I suggest you start by asking in the Elementor support forum, I don’t have any way of checking this out. If they can point to something specific in Participants Database that’s causing a problem, let me know.
It’s not a conflict with Elementor alone, as the Ocean WP plugin as well as others also send the error message.
The line in question is in the “Top level menu override” region of admin-menu-manager.php. The error occurs when reloading the page after I’ve made modifications – this only applies to pages with tabbed menus in PD.
Additionally, on a site running the previous version of PD this is not an issue (I have the same plugins on the other site.)
Yes, well there is evidence that there is a conflict with the plugin, but without more information, i don’t have enough to go on. You’re seeing error in other plugin code…this is not something I can investigate. This is why I ask you to check with Elementor or the other plugins support.
In your original post, you don’t mention what the actual problem is, just a warning, which alone is not significant. So, what is the functional problem you are seeing?
The functional problem is that whenever I make any modifications on a backend page in your plugin with a tabbed menu (such as fields / field groups management), when I click save, I get a blank page with an error message (the message I quoted above) at the top.
I have to return to the previous page and click refresh to see that the changes have been made, and to do whatever my next step is.
OK, there is more going on that you are not seeing…the warning alone would not stop execution, so what you need to do is look at your php error log to get the whole story. If you don’t know how to set up the php error log, you should ask your web host.
The best way to use the error log is to first clear it, then perform the action that causes the problem, then look at the error log. Usually, this will show only the messages that pertain to that one operation and should be helpful in identifying what the problem is.
Again, if the message is from another plugin, I can’t look into it, you need to refer to support for the plugin that is showing the problem. It’s not that I don’t want to help, I just can’t debug someone else’s code.
Just to let you know, everything is working fine now… I’m still using all of the same plugins, but someone fixed something in one of the updates!
