• Resolved 99uavvw

    (@99uavvw)


    Hi,

    We are using your plugin on our website and have just updated to the latest version but when we did the formatting (font sizes, layouts etc) of all out FAQs was changed. We have reverted back to the old version now but is there a reason for this?

    Thanks

Viewing 8 replies - 16 through 23 (of 23 total)
  • Thread Starter 99uavvw

    (@99uavvw)

    Hi Jay,

    Hopefully I’ve done what you want this time.

    I updated the FAQ plugin to V2.0.9.

    I made a new FAQ using the Elementor editor (https://imgur.com/CV2mZrz)

    This is how the FAQ looked like on the website with the concertina menu (https://imgur.com/EhjEiPM) and this is the source code for that (https://www.dropbox.com/s/bl1gy9wcklox9xr/Source%20Code%20for%202.txt?dl=0)

    This is also how the same FAQ looks like on its individual post / page (https://imgur.com/ifQANtR) and this is the source code for that (https://www.dropbox.com/s/rse0djecs9hczjl/Source%20Code%20for%203.txt?dl=0)

    I then updated the same FAQ with the WP editor (https://imgur.com/VH9Gxsf) (https://imgur.com/T9XvWGK)

    and this is how the FAQ looked like on the website with the concertina menu (https://imgur.com/OQmA9kf) and this is the source code for that (https://www.dropbox.com/s/zoke4nm3xex5ggx/Source%20Code%20for%206.txt?dl=0)

    This is also how the same FAQ looks like on its individual post / page (https://imgur.com/ZRlb88d) and this is the source code for that (https://www.dropbox.com/s/l0m95fsbtuf9wti/Source%20Code%20for%207.txt?dl=0)

    Cheers

    Plugin Support jaysupport

    (@jaysupport)

    Hi 99,

    I’m sorry if I have not been able to explain what I mean clearly. I’m not sure how else to explain it. When you open the edit screen for an FAQ that has been built with Elementor, click the “Back to WordPress Editor” button.

    This will load all the content you created with the Elementor builder, but in the the regular Gutenberg editor. I wanted to know if there was perhaps any broken code that showed there that might indicate what is going on.

    I can build FAQs with Elementor completely without issue using the newest version of our plugin. And we’ve had no other reports of trouble with this. There does not seem to be any inherent or global issue with this. There must be something specific to your site/setup that is contributing to this. The only thing that doesn’t make sense is how it only happens with 2.x.x. The conflict that is specific to your admin is further only specific to 2.x.x of our plugin. At this point, you may have to try some standard troubleshooting steps like deactivating other plugins and temporarily switching to a different theme.

    Thread Starter 99uavvw

    (@99uavvw)

    Hi Jay,

    I’m sorry for not getting it right, hopefully this time I’ve done it.

    I opened the editing screen for an FAQ made with Elementor and then went back to the WP editor (https://imgur.com/eCs8zlg) and this is the source code for this (https://www.dropbox.com/s/lj0g7bvmcgz3wfl/1.txt?dl=0)

    I also opened the same FAQ with the Elementor editor (https://imgur.com/KDMObTU) and this is the source code for this (https://www.dropbox.com/s/3mmn6lzu6zgt7ra/2.txt?dl=0)

    Hopefully this is what you want.

    Cheers

    Plugin Support jaysupport

    (@jaysupport)

    That’s what I was looking for. Unfortunately, there are no clues there. It just does what it should and removes the Elementor elements, leaving the content.

    Just to make sure, are you using the newest version (2.0.11)? We did have to add in a workaround a few versions back to compensate for the way SiteOrigin Page Builder applies content filtering. It should have nothing to do with Elementor, but, maybe, by some chance, something in there, or one of the newer updates, might have done some magic for your issue.

    If you are on the latest update and it makes no difference, then, at this point, I really don’t know what your issue is. If only someone else could chime in with perhaps a similar issue, but with an extra puzzle piece, maybe we could get a clue or a turn in the right direction. I am able to use Elementor without issue on our test sites. And we’ve had no one else even mention Elementor in any support requests since the release of 2.0.0.

    Thread Starter 99uavvw

    (@99uavvw)

    Hi Jay,

    We’re using version 2.0.11 of your plugin.

    I’m glad I finally managed to get you what you needed. Is there anything you can suggest for us to do to resolve the issue? Could the issue be cause by Elementor Pro?

    Cheers

    Thread Starter 99uavvw

    (@99uavvw)

    Hi Jay,

    I’ve tried deactivating all plugins except FAQs and Elementor and we’re still having the issue. I’ve tried a different theme and the issue is the same and I’ve tried deleting and re-installing the Elementor plugin but still nothing.

    Is there anything else you can think of that would be causing this issue?

    Cheers

    Plugin Support jaysupport

    (@jaysupport)

    Hi 99,

    We’ve been doing some more testing over the past two days and have found that the issue is happening because Elementor does not save their page content in the standard post_content variable. We made the FAQ page more efficient by using WP_Query to retrieve the FAQs. However, Elementor has a filter added to “the_content”, which checks the global $post object to then overwrite the content of a post with its custom structure. However, when they’re looking for a global $post object, since the FAQs are displayed with a single WP_Query, without the loop, the one they find is the main FAQ page and not the $post for the individual FAQ. This is far from ideal, since it means that Elementor would never work correctly with any post displayed using WP_Query instead of a WordPress loop.

    Nevertheless, we’ve modified our code to update the global $post object each time an FAQ is displayed, so Elementor’s filter that they added to “the_content” gets applied to each FAQ instead of the overall page. It would be much better if they just saved their content to the standard post_content, so WP_Query could be used without needing this hack. But I doubt they’ll update that any time soon, so, with this workaround, it’ll now get their filter to apply to each FAQ.

    We’ll be releasing an update shortly that includes this workaround.

    Thread Starter 99uavvw

    (@99uavvw)

    Hi Jay,

    The latest update has resolved the issues.

    Thank you for all your help, we really appreciate it.

    Cheers

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Issues with new update’ is closed to new replies.