it’s also always 262144 bytes that’s being tried to allocate
Plugin Author
Brecht
(@brechtvds)
It might be related to the domain change, yes. I’d try using a plugin like https://ww.wp.xz.cn/plugins/better-search-replace/ to search for the old domain and replace it with the name one.
I did do that with the wordpress cli tool and just checked with the tool you linked, but those are all fine. All pages without this plugin do work as expected and now after disabling it, the error doesn’t occur anymore. So I doubt it’s something on that end.
Do you need loopback to work? I do have a warning in the website health section that it’s not working for me (running in docker, seems to be a little tricky). But it ran in docker before I migrated so shouldn’t be a problem.
I’ll try and check if this error occured before I migrated to a new url.
okay, I just restored my backup on another host and there is no problem on that instance. So I guess the problem is either on my migrated setup or caused by the change of url. I’ll keep this open for now in case others encounter the same issue someday. For now I don’t think it’s something on your part, but maybe you can improve error handling once we know what’s wrong. Would be nice if this would’nt break the whole page by eating up all available php memory.
I’ll keep you updated
I did fix the problem with loopbacks, but the plugin is still broken for me. So not related to that. Kinda running out of ideas now. Any guess in what case this plugin could eat up all php memory?
Plugin Author
Brecht
(@brechtvds)
I’m not sure. Did you test Easy Image Collage without any other plugins active and when using a default theme?
do you store any data in database? I couldn’t find any tables
Plugin Author
Brecht
(@brechtvds)
Collages are saved as a custom post type with post meta to save the data. So that would be the wp_posts and wp_postmeta database tables.
Thank you. I looked into those and compared the database entries of my live instance with my backup and I can’t really see any difference besides the guid (the string search and replace tool I used did change those aswell). But changing those back did not fix anything. Or would I have to change more than the guid column of wp_posts to revert that?
Besides that, I did find out that I can still create new collages that do not break anything. I can even recreate one of my old ones, that still break the whole post, without any issues. I can also directly access my images with those links stored inside the tables you referred to, so they are definitely there and correctly served by my webserver. That indicates to me, that something must be wrong with those migrated collages inside of the database, even though I just copied the whole database and changed all occurrences of the old url. But when I compare the datasets of the old collage and the recreated one in database (wp_posts and wp_postmeta) I can’t really see a difference either. Just different dates and ids in wp_posts and some minor sizing differences and “s:88:”/”s:89:” instead of “s:84:”/”s:85:” as key in front of the image url in wp_postmeta.
I’m about to give up and delete/recreate all my collages by hand. That will take a ton of time, but I don’t have any more ideas where I could search for an error. Assumed you don’t have a new idea where to look at and/or can’t reproduce the issue.
Plugin Author
Brecht
(@brechtvds)
Could you send a quick email to [email protected] and attach some example eic_grid_data meta?
sure, I did just send it. Thank you for helping me out!
I eventually solved this by reverting to my backup state and changing all urls again by using the ‘wp search-replace’ tool provided in wp-cli. I did skip the guid column as described in the provided examples. I don’t know what exactly broke or what I did differently this time, but it does work now. Thank you for helping me out with this one.
