wp_die() problem

  • Resolved tvejacques

    (@tvejacques)


    6 months ago

    This is a multisite installation.
I'll explain what I did when the problem began.

1. After installing some plugins this didn't work:

* Appearance --> Editor (using Gutenberg)
* Appearance --> Theme --> Customize

After clicking, the process started leading to the target, but the screen remained blank.

Troubleshooting, by deactivating all plugins and activate them one by one, showed that the culprit is:

Conditional Logic for Woo Product Add-On

2. But after removing this Product Add-On plugin, and Activating plugins again, when activating the plugins one by one, the return window for each says I do not have access.

Yet the plugins did activate, so I continued working.

This is the message:

"Sorry, you are not allowed to access this page.

This message was triggered by WordPress Core.

"Call stack:

wp_die()

wp-admin/includes/menu.php:380

Query Monitor"

After installing another new plugin, there was another new conflict with WCFM Marketplace: Multi Vendor Plugin.

I deactivated the new culprit on the primary site, but its activation does not go away in the secondary site where it would be used.

Please advise
Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator bcworkz

    (@bcworkz)

    Hi tvejacques, sorry your’e still having difficulty. The not allowed access message generally means there’s an problem with your user’s role capabilities. But if plugins are causing errors it could be more of a symptom than a problem in of itself.

    In deactivating a plugin, you should deactivate it network-wide, which is not the same as deactivating in the primary site. When deactivating, be sure you’re in the network admin area and not that of any particular site.

    If you ever have difficulty accessing the right page to deactivate, you can deactivate via FTP or your hosting file manager by renaming the plugin’s folder within /wp-content/plugins/.

    Also be aware that caching can confuse your investigations. When testing, you should deactivate any caching plugins that you might have. If you’re still not getting expected results, also flush your browser’s cache.

    If you find that a number of otherwise reputable plugins are not working on your installation, it’s possible your core WP installation may have become corrupted. If you suspect this, you should perform a manual “update”, even if it’s to the same version. The point is to replace core files with those from a fresh download.

    Thread Starter tvejacques

    (@tvejacques)

    Thank bcworkz

    I indeed usually do the deactivation on the primary site when troubleshooting.
    Will do the manual “update” thing – thanks for that link.
    I am really disappointed with WordPress. The moment one does something more than a blog, brochureware or basic shop – something with a mix of more functionalities – plugin conflicts are severe and we waste an unbelievable amount of time.

    You have been a great help on several other problems we’ve experienced – thanks so much for that.
    _______
    PS

    We do a bit of development and everything works fine, then when trying to add another functionality provided by another plugin, problems start. On occasions we have tried 10+ alternative plugins for the same general purpose, and as they all give some or other problem (not always the same effect, though), we have to go back only to find the culprit is some other implemented plugin with a totally unrelated functionality.

    We then need to find a replacement for that plugin, thus redesigning what was already done and waste days on end. For example, we’d use a block plugin to build template parts, then do lots of other stuff, only to discover it is the bad boy, redo all those templates, and redo everything else that sits on top of that.

    We’ve had to chuck expensive themes, we tried various block builders, menu plugins, taxonomies, media management, conditionals, vendor management, and a very long list of others.

    Plugins for the same broad purposes offer different features. Clashes might occur because a particular feature of another plugin of a different “family” of purpose clashes with one from another “family”.
    Plugins should have the ability to have some of their features disabled – being object oriented that should not cause problems.

    WordPress should have stricter guidelines for plugin developers.

    I tell this long story because if we knew beforehand what we know now, we would have just rather have developed everything on a programming platform. I did mention somewhere that 20 years ago we developed a solution in PHP with more complexity than our present project. That went smoothly. We thought WP would be quicker.

    Moderator bcworkz

    (@bcworkz)

    I’m sorry you’ve had so much difficulty. Sadly, the more plugins you have, the more likely it is you’ll encounter conflicts. I know it’s frustrating to try out various plugins, only to find out they simply do not play well together. One thing you could do to help with this is to hire an expert programmer to either resolve the conflicts, or to develop a bespoke solution that’s a perfect match for your needs.

    Of course one of the criteria for success is their work cannot conflict with any of your existing configurations. Strive to find someone who is unlikely to disappear on you. Nothing worse than finding out down the line that their work is problematic and they are now no where to be found. Finding another programmer willing to repair someone else’s work can be a challenge. One resource where you can find competent programmers knowledgeable about WP is at https://jobs.wordpress.net

    Thread Starter tvejacques

    (@tvejacques)

    Thanks bcworkz

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.