Hi @tonitrommer,
we do not know about this error. What version of our plugin are you using?
Unfortunately, the website you linked is behind a password, so I can’t access it. If you’d like us to help you debug the issue, please create a new user in WordPress with administrator rights, email [email protected] and username onOffice. You do not need to send us the password, we’ll reset it ourselves.
All the best,
Johannes
Thanks for the quick reply!
I installed the latest version from the WordPress Plugin Repository.
I have created an user account with that email address (you should have received an email from wordpress). The htaccess password protection is temporarily disabled, as well as the plugin as the error also affects the login page.
Also I changed to twentytwenty-Theme and disabled all other plugins, the error persists. So it’s not a conflict with the theme or other plugins.
Thanks for creating the user, I managed to log in. And thanks for testing it without theme and other plugins!
Can I activate the plugin and try out a few things? Or is there a critical error which I cannot recover from using the account I have?
Feel free to do whatever you need to do. If you’re logged in, you should be able to continue with your work.
As far as I can see, the error only shows on Frontend and wp-login.
Great, thanks! Last safety check: Do you have the onOffice enterprise API token and secret? If yes, then I could try reinstalling the plugin and trying another onOffice enterprise instance.
Yes, I have them. Both configured in the plugin settings.
-
This reply was modified 4 years, 7 months ago by
tonitrommer.
I’ve tried some things, but it seems that the plugin does not install correctly on your site. I managed to install it on another. So it is unclear to me where the bug is and I’ve contacted our developers.
Out of security, I urge you to regenerate the API secret and token, since they are visible publicly in your post above.
I’ll keep you posted on any updates on the issue.
Thank you for your support, I’ll wait for updates. Meanwhile, I will also check if there’s something wrong with my server setup or something (but anything else works fine, so no idea what that could be).
Hi @tonitrommer,
I talked to a developer and they suspect that this is a naming conflict. It is really difficult to debug, but it would be very helpful if you could try to produce a minimal reproducible example.
Since it seems that deactivating all plugins still leaves the error, do you have the option of reinstalling WordPress on your server? If you add only our plugin, does the error still appear?
All the best,
Johannes
I already created a simple sample WordPress installation yesterday with nothing but your plugin installed and it worked perfectly.
The issue is that there is already a vendor folder in the root directory of the installation with it’s own autoloader. So I think this is the problem, nothing with you plugin. Just an incompatibility with this special installation.
Thanks a lot for your support. I am already developing my own plugin using your API to avoid this issue, I think that is the easiest way atm.
Hi @tonitrommer,
glad to hear that you found a way forward. Thanks for letting us know!
All the best,
Johannes
