• Resolved Mai

    (@maicrosoft)


    Hi,

    I think the new Divi 4.10 update broke the plugin. Now all sections are shown, no matter if you have set visibility rules for it or not.

    Here is an example of one of my sites using the plugin https://i.imgur.com/u12AWgZ.png Each row has a rule based on logged in state and user role, but as you can see all of them are shown now.

    Hope this will ever get fixed, or even be seen by the developer.

Viewing 15 replies - 1 through 15 (of 21 total)
  • Same thing happened with me. Luckily, you can roll-back the Divi version and mine started working again.

    I’d consider disabling auto-updates too.

    Thread Starter Mai

    (@maicrosoft)

    Yeah, that’s what I did in the end but it’s not a solution for the long run. My question here is whether there will be a more permanent solution for this or not, hoping the dev will reply. Leaving a plugin/theme/wp core on an old version is not an ideal situation at all.

    Same here. Sadly I didn’t notice for two days. I’ve become quite dependant on this plugin – I can’t find any obvious alternative.

    Here’s hoping that the fix is simple and that it happens pretty soon.

    Plugin Author Jonathan Horowitz

    (@jhorowitz)

    Hi @maicrosoft, @tomfadial and @chaostica!

    Thank you for reporting this to us!

    On our test site with Divi 4.10.3 and Content Visibility for Divi Builder v3.16, the plugin works as expected for hiding/showing content via boolean expressions.

    We did notice an issue with the documentation page in the admin not showing available modules, and will look to address that in a coming update, but the way that page loads has no impact to the core functionality of the plugin.

    Therefore, we believe there is something deeper at play here. Could you all please share the list of plugins installed and active on the sites displaying the issue? You can either post here or email [email protected]; hopefully there will be a common plugin between the three of you that may help narrow this down.

    Also, are any of you using the advanced filters/actions prefixed with content_visibility_for_divi_builder_ that the plugin provides?

    Thank you for your patience and help diagnosing this issue promptly!

    P.S. If any of you would be willing to go the extra mile and disable all plugins except CVDB (and the builder plugin if not using the Divi theme) and then, if it works, re-enabling plugins one by one to find the offending plugin (if that is indeed the issue), we would really appreciate it! But if not, no worries ??

    I have two modules, one that shows with “is_user_logged_in()” TRUE, and the other that shows with !is_user_logged_in() TRUE (meaning not logged in). Both now show with 4.10.3. I tried deactivating and reactivating, didn’t help.

    Plugins that are installed (all active) are:

    Akismet Anti-Spam 4.1.10

    Child Theme Configurator 2.5.8

    Content Visibility for Divi Builder 3.16

    Final Tiles Grid 3.5.1

    GoDaddy Email Marketing 1.4.3

    Import and export users and customers 1.17.9

    ProfileGrid 4.5.4

    ProfileGrid Login Logout Menu 1.2

    Profilegrid Woocommerce 2.0

    Search Engine Visibility 0.5

    Smart Slider 3 3.5.0.10

    Sucuri 1.8.28

    User Menus 1.2.7

    WooCommerce 5.6.0

    WooCommerce for Logged-in Users 1.2.2

    WooCommerce Square 2.5.3

    Woo Donations 1.8

    WP101 Video Tutorials 0.3

    Wufoo Shortcode Plugin 1.43

    Zapier for WordPress 1.0.2

    • This reply was modified 3 years, 7 months ago by sthaney.
    • This reply was modified 3 years, 7 months ago by sthaney.
    • This reply was modified 3 years, 7 months ago by sthaney.
    • This reply was modified 3 years, 7 months ago by sthaney.
    Plugin Author Jonathan Horowitz

    (@jhorowitz)

    Also, quick question: does the option to set visibility expressions still show up in the builder?

    Hi Jonathan,

    I’m having same issue with last upgrade of Divi 4.10.3, I tried to clean cache, disable/enable Content Visibility, but nothing worked.

    I was doing some test and I can see that the attribute “cvdb_content_visibility_check” is not comming for all modules in content_visibility_for_divi_builder_prevent_texturize_shortcodes, in the “eval” “if” block, only rows were being processed.

    I have two text modules with Content Visibility option, then I’ve duplicated the row and moved each text module to one row to hide one for logged-in and other for logged-out users. (temporal fix)

    Thanks.
    Juan

    • This reply was modified 3 years, 7 months ago by jgarces.

    Hi Jonathan,

    I created a staging site from a site that uses CVDB a lot. CVDB worked until I updated Divi and then it failed. I then disabled all plugins except for CVDB and it still failed. I tried activating Divi itself rather than the child theme and I tried running troubleshooting. In each case CVDB would still fail.

    There are two things I’m doing with CVDB. One is showing sections based on categories and the other is displaying buttons and some text based on location. For location I’m using Geolocation IP Detection.

    The host is running a Litespeed server. I doubt that’s relevant but you never know.

    Since I’ve got this set up as a staging site I could give you access if that would help. Let me know.

    For the moment and for what it’s worth here are my plugins:

    Admin Menu Editor
    Advanced Custom Fields
    Advanced Editor Tools
    Akismet Anti-Spam
    Asset CleanUp Pro
    Auto Featured Image
    Auto Featured Image premium (Premium)
    Classic Editor
    Classic Widgets
    Content Visibility for Divi Builder
    Display Posts
    Easy WP SMTP
    Embed Plus for YouTube
    Far Future Expiration Plugin
    Geolocation IP Detection
    Health Check & Troubleshooting
    Imsanity
    LiteSpeed Cache
    Maintenance
    MainWP Child
    MainWP Child Reports
    Pages with category and tag
    PDF Embedder
    Perfect Images
    Rank Math SEO
    Rank Math SEO PRO
    Relevanssi
    Show IDs
    Wordfence Security
    WordPress Importer
    WordPress Popular Posts
    WP to Buffer Pro
    Yoast Duplicate Post
    Yoast SEO Premium`

    Admin Menu Editor
    Advanced Custom Fields
    Advanced Editor Tools
    Akismet Anti-Spam
    Asset CleanUp Pro
    Auto Featured Image
    Auto Featured Image premium (Premium)
    Classic Editor
    Classic Widgets
    Content Visibility for Divi Builder
    Display Posts
    Easy WP SMTP
    Embed Plus for YouTube
    Far Future Expiration Plugin
    Geolocation IP Detection
    Health Check & Troubleshooting
    Imsanity
    LiteSpeed Cache
    Maintenance
    MainWP Child
    MainWP Child Reports
    Pages with category and tag
    PDF Embedder
    Perfect Images
    Rank Math SEO
    Rank Math SEO PRO
    Relevanssi
    Show IDs
    Wordfence Security
    WordPress Importer
    WordPress Popular Posts
    WP to Buffer Pro
    Yoast Duplicate Post
    Yoast SEO Premium

    Cheers,

    Daniel

    Hi Jonathan,

    I’ve looked a bit further. Most of the place I’ve used CVDB were at the module level. It occurred to me to try it on a row. It’s working when applied to a row or a section. It’s not working when applied to a module. I haven’t done enough testing to find out if that is consistant everywhere, but every row and section I’ve applied it to it seemed to work and every module it seems to fail.

    Daniel

    Plugin Author Jonathan Horowitz

    (@jhorowitz)

    Hello @chaostica, @jgarces, @sthaney, @maicrosoft and @tomfadial. (Whew!)

    Wanted to reach out to you all to let you know that we have identified and fixed the issue in v3.17 of Content Visibility for Divi Builder. Thank you all so much for the additional information provided here, it really helped!

    Please let us know how the update goes and if it resolves your issues ??

    Thanks again!

    Jon

    Still having problems!! Here are my plugins

    Advanced Custom Fields PRO
    Akismet Anti-Spam
    Select Bloom
    Bloom
    Classic Editor
    Content Visibility for Divi Builder
    Custom Post Type UI
    Default featured image
    Divi Booster
    Select Divi-Modules – Table Maker
    Divi-Modules – Table Maker
    Google Analytics for WordPress by MonsterInsights
    Jetpack
    MalCare – Pro
    Monarch Plugin
    Rearrange Woocommerce Products
    Scheduled Post Trigger
    ShopMagic Abandoned Carts
    ShopMagic Advanced Filters
    ShopMagic Delayed Actions
    ShopMagic for WooCommerce
    ShopMagic Manual Actions
    WooCommerce
    WooCommerce – ShipStation Integration
    WooCommerce Authorize.Net AIM Gateway
    WooCommerce Cart Add-Ons
    WooCommerce Email Customizer with Drag and Drop Email Builder
    WooCommerce Shipping & Tax
    Woocommerce Table Rate Shipping Pro
    WooCommerce Zapier
    Yoast SEO`

    Fatal error: Cannot declare class ET_Builder_Module_CTA, because the name is already in use in /home/customer/www/simplehealthnh.com/public_html/wp-content/themes/Divi/includes/builder/module/Cta.php on line 0

    Plugin Author Jonathan Horowitz

    (@jhorowitz)

    Hi @mangomichelle,

    That’s an odd error, since CVDB doesn’t load any modules directly. Can you try disabling all the plugins except CVDB and using Divi theme directly? Then re-enable them individually to see which causes the issue?

    The 3.17 version worked for me. Thanks for the quick response, and good luck to others that are still having problems.

    I’d like to add that it’s working when using the code within a text module but if it’s on the module itself (like an image) or Flipbox or something like that, it is not working. ??

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘Plugin stopped working with new Divi 4.10+ update’ is closed to new replies.