Hey,
Can you tell me exactly what happened when the site broke? Did you get the white screen of death or were there issues with posts? The more descriptive you are, the quicker we might get this resolved.
wafwaf,
I just realized that the JS directory and JS file some how didn’t make it into the last update. I added them in a 1.2.1 version update. I don’t know if that might be the issue, but feel free to check and let me know if that fixes the problem. Also, if you want to use version 1.1, you can go here https://wordpress.org/plugins/jm-breaking-news/developers/ to download and reinstall that version.
Hi,
Jacobe
You asked to wafwaf that
“Can you tell me exactly what happened when the site broke?”
I can tell that as i installed your plugin via my admin panel and clicked on “Activate Plugin” link, I got the white screen of death.
Then i had to delete your plugin from cPanel.
I am using WordPress 4.2.3 running Hueman theme.
You should not claim compatibility if you have not tested your plugin.
Thanks
I’ve tested this with WordPress 4.2.2 and it did work on a number of test sites. My understanding is WordPress just released 4.2.3 and there are a number of plugins that broke. I never claimed it worked with 4.2.3.
Anyway, can you find an error log in the public_html directory or something similar to that? The description of the error you ran into should be at the bottom of that error log and will help us both to figure out what might of happened while I test the compatibility with the new version of WordPress.
Also, not sure why WordPress says it’s compatible with 4.2.3. The readme.txt hasn’t been updated. Very odd.
Thanks for the error log. Do you know about what time during the day (in UTC preferably) that you tried to install the plugin. There are a ton of database errors in there, none of which look related to this issue, and it makes almost impossible to find the actual error I’m looking for. Thanks.
Also, I updated all of my testing sites to WP v4.2.3 and have yet to run into an error.
I have tested all 3 versions, only first version does not break, and both other 1.2 and 1.2.1 go to the white screen of death.
Now you can download error_log file from the same link.
I cleared old log file and then tried to install your latest version, had to face same error.
Then i zipped new error_log file for you.
Please let me know when you have downloaded it.
I have tested all 3 versions, only first version does not break, and both other 1.2 and 1.2.1 go to the white screen of death.
Now you can download error_log file from the same link.
I cleared old log file and then tried to install your latest version, had to face same error.
Then i zipped new error_log file for you.
Please let me know when you have downloaded it.
So I took a peek at your error log and found this.
[24-Jul-2015 03:41:54 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 12681269 bytes) in /home/zemtvs/public_html/wp-includes/class-phpmailer.php on line 2171
The issue appears to be along the lines of too many big plugins that take up all of the available space on your server. I haven’t really dealt with this issue before with WP sites I run, but if you search that error on Google, there are a number of forum issues on that topic. This one, https://wordpress.org/support/topic/fatal-error-allowed-memory-size-of-67108864-bytes-exhausted-tried-to-allocate-1, might be a good starting point. Hope it helps. Not entirely sure why version 1.2 and above might be causing that error. I’ll see how I can size it down in future versions.
Right, you should see how you can size it down in future versions.
Because as i have said the oldest version of your plugin works fine on same site, but other tow versions do not.
So I just ran a few numbers and really, the plugin in it’s current state (1.2.1), is only using roughly 800KB of memory, which in the grand scheme of plugins isn’t that much. Now granted, it’s still up from the 70KB or so used by 1.1, but still, I’m not sure how to cut it by that difference.
Just out of curiosity, how many plugins do you have on your site? That will cause issues as well. I would get rid of any that you aren’t using, try 1.2.1 again and it’s still giving that error, let me know and I’ll see what I can do.
