on 1.5.5 update, admin error no admin_init

I’m having the same error, it runs along the top of the backend in wordpress. Thankfully it doesn’t appear to have affected the frontend at all.

Same here, just updated this plugin (which is wonderfull btw) and got the error message. No show on frontend pages and the plugin does work on frontend pages.

It appears this error is affecting my ability to add new pages/posts or edit anything on the site, when I try I just get a load of errors thrown at me in the backend regarding line 429.

Well, I don’t have that problem. I have the error message and I can still publish any posts or pages. With and without the usage of the plugin.

Odd.

I’ve disabled the plugin for now and I can update my site once again just fine.

Hopefully this can be resolved soon so I can restart the plugin. ??

same error message here, too. If it’s affecting other things, I think I’ll rollback till the fix is released.

(love this plugin by the way – keep up the good work.)

Hmm the error of collapse-o-matic causes some problems with other plugins in the backend.
For example: I use for my personal website a plugin for a bucket-list. The backend shows me normaly a list with categories and goals. With Collapse-o-matic and its error, the bucket list plugin does not show that list. It simply will not load it. The frontend shows the list fine tho.

I deactivated this plugin as well. Altho it’s a wonderful plugin, Im gonna search for another option to use a similar function on my website. Till the problem is fixed, I will not enable this plugin.

So lets hope there will be an update soon which fixes this error.

CRAP! sorry about that. Update 1.5.6 is available and fixes this issue. We really need to fire the drunken pirate monkey that tests our code. Turns out it was not such a good idea.

Works like a charm, Thanks very much!

Thanks for the quick fix. Enabled the plugin again and it works perfectly now.
Keep up the good work!

amazing turnaround, Baden – thanks ??

*sigh of relief*
if you don’t mind, please vote for pedro.

yup 1.5.6 works and fixes that bug. thanks for the quick response!