[ad_1]
Hi, I am having issues with the plugin update as well. How were you able to put the old version of the plugin back on the website? Unfortunately I have plugin autoupdates activated so restoring backup doesn’t help.
- This reply was modified 3 hours, 17 minutes ago by .
Hi @katjanurmi,
You can download the sourcecode of the precedent version of the plugin here :
It comes from their official github repo.
I have just put the content of the archive in wp-content/plugins and deleted the new version of the plugin, and renamed the folder of the archive with the correct name (and then desactivated the autoupdate in backoffice).
It solved the problem for all my websites with this issue
I would recommend downloading previous versions from projectdmc.org here and because GitHub ships with a lot of extra files that are meant for development only, and not needed for final release.
You should hopefully be able to do that with most plugins on projectdmc.org here actually, just tack on /advanced/ to the URL or click “Advanced View” in the right sidebar.
Anyways, based on the error itself presented above, the issue is stemming from /wp-content/themes/nanosite-proefficace/functions/admin-register-menus.php which is going to be one of your theme’s files. However, I’m not familiar with this specific theme so it’s impossible for me to say what’s in that admin-register-menus.php file and why it may be contributing to headers being sent already.
Are you willing to share the contents of that specific file? I can provide instructions on how to share that part privately if you prefer.
@nicolastroadec please try out version 1.13.1 when you have a chance.
Yes I mentioned the idea that the theme was where things were originating from, but based on feedback and help from other forum members, I did find a place where we were sending content to the browser before intended. This would absolutely contribute to the type of error you’re seeing, so that’s on us and my apologies for causing some troubles for you.
If you’re still seeing similar errors after the 1.13.1 update, let us know and we can continue digging in.
It works perfectly now, thank you for the quick update !