WordPress.org

Forums

Multiple Themes
[resolved] Updates: conflict between NGG & Jonradion Multiple Themes (22 posts)

  1. fran330
    Member
    Posted 1 year ago #

    CC: NextGen Gallery plugin

    My site is a multisite. I have just updated WP and plugins that needed updates.
    After that, the frontend showed a blanck page with the error message:

    Fatal error: Call to undefined method stdClass::add_query_var() in /homez.744/vivartan/www/wp-includes/taxonomy.php on line 356

    I then tested desactivating/reactivating each plugin. This showed me that the problem occurs only when NGG and Jonradio are both activated. When only one of them is activated, all works well.

    Note: The problem occured already after I updated NGG, but before I updated Jonradio. So I guess the cause is more on NGG side.
    Once Jonradio updated as well, problem still occurs.

    The problem occurs also when using WP default theme.

    Thanks in advance

    https://wordpress.org/plugins/jonradio-multiple-themes/

  2. jonradio
    Member
    Posted 1 year ago #

    I will be back at my desk and test systems in 90 minutes, and try and recreate the problem then.

  3. fran330
    Member
    Posted 1 year ago #

    Thank you very much :)

  4. jonradio
    Member
    Posted 1 year ago #

    I haven't been able to recreate this error on my test system.

    Maybe I missed something, but I could not see a lot of useful information in the support forums or elsewhere on the Internet on this particular error message.

    But there was one common thread to 80% of the reports: it started happening right after a WordPress upgrade, i.e. - new version of WordPress. A couple of them appeared to be Memory issues. Tie that together with the fact that new versions of WordPress require more memory, and that says the most likely cause of your problem is either:

    1. WordPress update to new version that did not work properly
    2. Not enough PHP memory to run the current version of WordPress, your Theme(s) and all your activated plugins

    I really don't think this problem is a conflict between NGG and my plugin. To put it another way, there are a lot more likely answers. Among other reasons, because my plugin does not do anything with Taxonomies. Nor does NGG, I suspect.

    A logical next step is to deactivate all your other plugins and leave NGG and my plugin running. And see if the error still occurs.

  5. fran330
    Member
    Posted 1 year ago #

    Thank you for your reply.

    About the logical next step you advise at the en of your post: I just rechecked. I first activated WP default theme, in case there was something wrong with my theme. Then
    - All plugins desactivated: website OK
    - Only Jonradio activated: website OK
    - Only Nextgen activated: website OK
    - Only Jonradio and Nextgen activated: Error message.

    About memory, this site is being built and is very small right now. It contains just a few simple pages and a couple of small pictures.
    When I check my website data on my host website (OVH.com), only a tiny part of the allocated space is used by my website.
    My website runs with php 5.5

  6. jonradio
    Member
    Posted 1 year ago #

    Sorry for the confusion, I was speaking about computer memory, also known as RAM, or PHP MEMORY in this particular case. Not disk space.

    After I wrote my last post, I noticed that your site was using a Caching plugin. They can use a lot of memory, so I am very glad that you tested without it.

    I'll respond again once I've done a little more research, thinking and testing. I haven't run into anything like this before.

  7. jonradio
    Member
    Posted 1 year ago #

    Oops, I overlooked one important test that will either tell a lot of new information, or nothing. In your wp-config.php, look for define('WP_DEBUG',

    At the same time as you activate NGG and my plugin, make sure it reads define('WP_DEBUG', true); (be sure to save the wp-config.php after you make the change).

    A lot of plugins may generate warning messages, so you may want to keep the time short that you leave WP_DEBUG set to true, so feel free to set it back to false as soon as you cut and paste any new messages that you get.

    Please report back any warnings, notices, errors, etc. that you get before the Fatal Error you quoted in the first post.

  8. fran330
    Member
    Posted 1 year ago #

    Thank you for your time :)
    I just tried with WP-DEBUG set to true (with all plugins activated). This is what I get:

    Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /homez.744/vivartan/www/wp-includes/functions.php on line 2908

    Deprecated: Assigning the return value of new by reference is deprecated in /homez.744/vivartan/www/wp-content/plugins/dp-widgets-plus/dp-widget-plus.php on line 431

    Fatal error: Call to undefined method stdClass::add_query_var() in /homez.744/vivartan/www/wp-includes/taxonomy.php on line 356

  9. jonradio
    Member
    Posted 1 year ago #

    I'm afraid that doesn't provide any relevant information. I'm going to compose a support thread of my own in the general Troubleshooting area of the forums to try and make sure that this isn't a failure in the WordPress upgrade to a new version. I'll include a link below, and suggest that you subscribe to it.

    As I said, stdClass::add_query_var errors are something I need to know more about.

  10. fran330
    Member
    Posted 1 year ago #

    OK
    For your info,
    1) This site is under construction. It's not public yet. So no worry if it takes a little time. I am already very happy you're looking for a solution.

    2) Maybe this wasn't a useful test but in case, I just downgraded NextGen Gallery to an earler version (2.0.11 because it is the one I had on my hard disk). The problem is the same. So I am updating it again to last version now.

  11. jonradio
    Member
    Posted 1 year ago #

    Under these circumstances (under construction), because of so many of the reports of this error being connected to WordPress upgrades, it probably makes more sense for you to do a Restore of your site as it was before anything was upgraded, and to repeat the WordPress upgrade with all plugins deactivated first.

    But, I will still post on the support forum, and see if the suggestion to restore comes from there, before suggesting you actually do that Restore.

    However, because time is of the essence in backups -- most hosts only keep them a short time -- I would ask you to do this much right now: find a backup that you are happy with from before either WordPress or any plugins/themes were updated. And keep it in a safe place. A WordPress backup is all the WordPress files plus the WordPress database.

    By "happy with", I mean a backup that includes all the things you want not to have to "re-do".

  12. jonradio
    Member
    Posted 1 year ago #

  13. fran330
    Member
    Posted 1 year ago #

    Aaaaah! I found a solution. It's not the way it should work ideally but it works.

    As said in my 1st post, it is a multisite (containing just one site at the moment). I just tried and realised this: If I activate either Nextgen G or Jonradio (not both) on the network admin panel, I just have to activate the other one on the site admin panel. That way everything works fine.

    Of course, we shouldn't have to activate plugins on the individual site admin panels when we need them on all sites. So there is something that should be fixed somewhere anyway. Nevertheless I am quite happy with this solution.

    If you ever find a better solution some day, of course I'll be happy to know it. Otherwise, I thank you very much anyway for your time, Mr Jonradio :)

  14. jonradio
    Member
    Posted 1 year ago #

    Admittedly, my tests were based on activated on individual Sites in a WordPress Network (Multisite), but even now when I Network Activate both plugins, I do not get the error you were seeing.

    Nonetheless, I will continue looking at this, and report anything of interest here.

    Thank you for your patience. As I say, very weird problem.

  15. fran330
    Member
    Posted 1 year ago #

    If looking closer at my website would help, I'll be happy to make you a temporary admin and give you acces codes, etc. If it would help, ask me.
    I would then also need a way to send the info to you.

  16. jonradio
    Member
    Posted 1 year ago #

    For now, I'll wait to see what I hear from the other thread.

    Please send me your e-mail address via http://jonradio.com/contact-us/ That will ensure that I don't lose contact with you.

  17. fran330
    Member
    Posted 1 year ago #

    OK

  18. photocrati
    Member
    Posted 1 year ago #

    @jonradio - Thanks for all of your investigation into this matter. If anything does come back as being NextGEN Gallery related please let us know what you find so we can review/address those details.

    Just drop us a note or send me a direct response (@Cais) so I can follow-up with our developers.

    - Cais.

  19. jonradio
    Member
    Posted 1 year ago #

    I am now getting this error on one of my test systems! When I know more, I'll post here.

  20. jonradio
    Member
    Posted 1 year ago #

    Version 4.8 has been released to deal with this issue.

  21. fran330
    Member
    Posted 1 year ago #

    WOWWW! Awsome, Mr Jonradio! It even fixes other minor symptoms, like getting a blank page after activating a plugin.

    It's really pleasant to see an plugin author so quick to respond and so dedicated. Thank you very much! :-)))))

  22. photocrati
    Member
    Posted 1 year ago #

    @jonradio - Thanks for the new release dealing with this issue!

    - Cais.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Multiple Themes
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic