Forum Replies Created

Viewing 15 replies - 16 through 30 (of 38 total)
  • Thread Starter awelsh

    (@awelsh)

    I found the solution to this problem. In expert mode, you need to tick “the_post:”

    Thread Starter awelsh

    (@awelsh)

    False alarm. I just realised it is not a conflict with wpml. I am using plugin organizer and had videojs turned off except for the page I was using it on. I had to enable it for the new translated page.

    Thread Starter awelsh

    (@awelsh)

    Thanks for all your help. After reading what you said, and then doing a search on “Comment paging links selector” I came across an answer you gave a year ago at:

    https://wordpress.org/support/topic/plugin-does-not-work-with-paginate_comments_links?replies=5

    After analysing the problem there, and how it was fixed, I managed to get my problem fixed.

    For all those using the Genesis framework, you need to change the “Comment paging links selector” to “#comments a” It’s that simple.

    Thanks again for your help, and for a great plugin. I’ll be leaving a good review,
    Adrian

    Thread Starter awelsh

    (@awelsh)

    Ok I did some testing and have some more information. I created a fresh site and got it all working. However when I activate the genesis framework, it stops working and I notice this line in the network logger appears when genesis is activated:

    “[WP-Ajaxify-Comments] Search comment paging links (selector: ‘#pagination a’)… Not found”

    Without the genesis framework, the same line above looks like this:

    “[WP-Ajaxify-Comments] Search comment paging links (selector: ‘#comments [class^=’nav-‘] a’)… Found: ” Object { 0: , 1: , length: 2, prevObject: Object, context: HTMLDocument → test, selector: “#comments [class^=’nav-‘] a” }

    So there is obviously an issue with the genesis framework. Is that something that can be fixed?

    Now with my development site, there must be more issues, because when I first noticed the problem, I deactivated Genesis and all plugins and it did not fix the issue. I’ve just tried again and it still does not work. It still has the Search comment paging links error. However, if I can get it to work with genesis on a fresh site, I can then start looking into what else might be causing the issue.

    Adrian

    Thread Starter awelsh

    (@awelsh)

    Hi Janjonas,

    When I click on the “Older Comments” button, the following appears at the bottom of the network logger in the console:

    “[WP-Ajaxify-Comments] Scroll to anchor element ” Object { 0: <div#comments.entry-comments>, length: 1, context: HTMLDocument → comment-page-1, selector: “#comments” } ” (scroll speed: 500 ms)…”

    Not sure where the URL is in the line. When the page is loaded for the first time, the follow also appears in the network logger:

    “[WP-Ajaxify-Comments] Initializing version 0.25.0” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Found jQuery 1.11.1” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Found jQuery blockUI 2.6” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Found jQuery Idle Timer plugin” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Attach form…” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search comment form (selector: ‘#commentform’)… Found: ” Object { 0: <form#commentform.comment-form>, length: 1, context: HTMLDocument → 1-at-the-table, selector: “#commentform” } wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search comments container (selector: ‘#comments’)… Found: ” Object { 0: <div#comments.entry-comments>, length: 1, context: HTMLDocument → 1-at-the-table, selector: “#comments” } wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search respond container (selector: ‘#respond’)… Found: ” Object { 0: <div#respond.comment-respond>, length: 1, context: HTMLDocument → 1-at-the-table, selector: “#respond” } wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search comment paging links (selector: ‘#pagination a’)… Not found” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search comment links (selector: ‘#comments a[href*=”/comment-page-“]’)… Found: ” Object { 0: <a.comment-time-link>, 1: <a.comment-time-link>, 2: , length: 3, prevObject: Object, context: HTMLDocument → 1-at-the-table, selector: “#comments a[href*=”/comment-page-“]” } wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Initialization completed”

    Adrian

    Thread Starter awelsh

    (@awelsh)

    Hi John,

    Thanks for your reply. The “Return to Top” link is not able to fix this issue. The issue I’m having is once you have read to the end of the first accordion which may be several screen lengths in size, and click the next one you are not taken to the beginning but have to scroll up to the beginning of the accordion.

    The diagram below tries to illustrate what is happening once you have clicked accordion 2 title:

    accordion 1 title
    accordion 2 title
    | |
    —————– top of screen
    | |
    | |
    | accordion 2 |
    | contents |
    |———– |
    —————– bottom of screen

    What needs to happen is the following:

    accordion 1 title
    —————– top of screen
    accordion 2 title
    | |
    | |
    | accordion 2 |
    | contents |
    |———– |
    —————– bottom of screen

    It needs the ability to automatically scroll to the arconix-faq-accordion-title once it is opened.

    Thanks again for your help,
    Adrian

    Have you figured out a way to do shortcodes yet? I’m wanting to wrap my content in an accordion but without being able to use shortcodes, it makes it impossible.

    Thanks

    Thread Starter awelsh

    (@awelsh)

    Hi Janjonas,

    Here is the information from the console when I first load the page that I have comments on:

    An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing 1-at-the-table:3204
    “[WP-Ajaxify-Comments] Initializing version 0.25.0” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Found jQuery 1.11.1” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Found jQuery blockUI 2.6” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Found jQuery Idle Timer plugin” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Attach form…” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search comment form (selector: ‘#commentform’)… Found: ” Object { 0: <form#commentform.comment-form>, length: 1, context: HTMLDocument → 1-at-the-table, selector: “#commentform” } wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search comments container (selector: ‘#comments’)… Found: ” Object { 0: <div#comments.entry-comments>, length: 1, context: HTMLDocument → 1-at-the-table, selector: “#comments” } wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search respond container (selector: ‘#respond’)… Found: ” Object { 0: <div#respond.comment-respond>, length: 1, context: HTMLDocument → 1-at-the-table, selector: “#respond” } wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search comment paging links (selector: ‘#pagination a’)… Not found” wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Search comment links (selector: ‘#comments a[href*=”/comment-page-“]’)… Found: ” Object { 0: <a.comment-time-link>, 1: <a.comment-time-link>, 2: , length: 3, prevObject: Object, context: HTMLDocument → 1-at-the-table, selector: “#comments a[href*=”/comment-page-“]” } wp-ajaxify-comments.js:87
    “[WP-Ajaxify-Comments] Initialization completed”

    When I click on the “Older Comments” button, the following appears in the console:

    “[WP-Ajaxify-Comments] Scroll to anchor element ” Object { 0: <div#comments.entry-comments>, length: 1, context: HTMLDocument → comment-page-1, selector: “#comments” } ” (scroll speed: 500 ms)…”

    I hope this helps,

    Adrian

    Thread Starter awelsh

    (@awelsh)

    It was set to “in the widget area” I don’t recall setting it to that. So I changed it to at the end of the post and it now works. Thank you for your help and thank you for a great plugin.

    Thread Starter awelsh

    (@awelsh)

    I’m sorry but I can’t provide you a link because i’m currently only working on a local developement site.

    Thread Starter awelsh

    (@awelsh)

    Thank you so much! Your plugin is so useful and has made my life a lot easier. From what I can see, it is missing just one feature, which I know others have requested, and that is showing all posts with pagination. At the momement I’m using W4 Post Lists to achieve this, but if your plugin had pagination (especailly with ajax) that would be the only plugin I would need to manage my posts. I understand however you are proving this plugin for free, and I’m sure it must take up quite a bit of your time, so there is no pressure to add this feature.

    Regards,
    Adrian

    Thread Starter awelsh

    (@awelsh)

    Is it possible to use the exclude=”this” with just the following code?

    [content type=”post” id=”1376″ field=”image-link” image_class=”image-shadow” size=”full” exclude=”this” ]

    It is not being called from a [loop][/loop] anymore. I changed the way products are organized in my custom post type, and can’t use the loop I was using before. I’m wanting to display the image of indiviual posts (hence the id number) but exclude them when on their own page.

    Thread Starter awelsh

    (@awelsh)

    Ok I managed to fix the problem by using size=”full” The docs says this is the default and it wasn’t necessary to specifiy the size until now. So it looks like the default size is being overridden by a smaller size.

    Thread Starter awelsh

    (@awelsh)

    Thanks for the fix. Works great now. I’m using the code in my sidebar so it doesn’t originate in the post, but ends up there when wordpress does its thing. The post is a custom post type which I’ve named book.

    Thread Starter awelsh

    (@awelsh)

    Thanks for fixing the image_class bug. However there is now a much worse problem which I can’t get around since the 1.3.1 update. All my images are being displayed at a tiny size of 150×150. The plugin use to default to showing the full sized image, and I would use css to size them down. But now, the images are being cut off so no amount of resizing in css can get the image back.

Viewing 15 replies - 16 through 30 (of 38 total)