v 2.0.0 issues

@arrasel403

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

Yeah policies are like that on WP.org.
No harm either way ??
Luckily I know what I want / don’t want te share publicly.

The team reached out by mail as it is something they need some additional information for. So in short they have asked for; wp rocket config, system health details and a staging enviroment.

I have provided them currently with;
– wp-rocket config export
– perfmatters config export
(but noting that the issue is present without them (disabling them)).
– system health export
– A staging enviroment is quite a challenge as it is a big website on which we are using NotificationX.

As per what I requested the team provided me with the rollback of the pro version.
So I rolled back to prior 2.0.0 on BOTH base and pro version. And the plugin is now working as it was before.

As Yui explained here, if we get to resolve the issue which seems to be in the base (free) plugin. I will update this ticket, as helping one can likely mean helping many.

Once again thanks to the NotificationX team for replying and helping out in quick fashion. Thanks to Yui for keeping things clear about WP.org rules.

I’m sure the team will get this resolved ??

FYI all has been resolved on my end now.
The team was informed about what to look for when it comes to WPRocket and Perfmatters.

In short;

in Perfmatters;
– REST API must be set to default, as NotificationX now uses it.
– wp-data must be disabled through Script Manager everywhere (it seems to do no harm)

in WPRocket;
– Load JavaScript deferred
– Delay Javascript Execution
Both need;
/wp-includes/js/dist/vendor/moment.min.js
/wp-includes/js/dist/date.min.js

Then NotificationX will work fine.
Also if you in the past added ‘notificationx’ in the mentioned WPRocket options please remove them to prevent any issues.

The team might be looking into getting this solved without the above. But for now this works just fine so I am calling this resolved.

Also I got to play a bit with how flexible NotificationX now is and I like it a lot ??
Keep up the great work guys!