That’s very strange. Can you share with me the URL? How did you change the URL? Any errors in your PHP logs?
Thread Starter
Thibaut
(@aiacciu87)
Hi Jordy π
Here is the URL : http://www.mikii.fr/
Simply moving file and change WP_HOME and WP_SITEURL in wp_config.php
I guess your WordPress is also updated? If you turn debug on, what is in the logs?
Thread Starter
Thibaut
(@aiacciu87)
Yes latest version of WP. Logs says:
2015-03-17 23:27:46: * HTML REWRITE FOR PICTUREFILL
2015-03-17 23:27:51: * HTML REWRITE FOR PICTUREFILL
2015-03-17 23:28:08: * HTML REWRITE FOR PICTUREFILL
2015-03-17 23:28:45: * HTML REWRITE FOR PICTUREFILL
2015-03-17 23:28:57: * HTML REWRITE FOR PICTUREFILL
Something weird happens now and completely stop the plugin code to execute. Can you check your PHP error logs?
Thread Starter
Thibaut
(@aiacciu87)
Will check this in detail. But atm I notice that :
[Wed Mar 18 10:03:34 2015] [warn] [client 85.169.116.176] mod_fcgid: stderr: Retina: This status is not recognized: , referer: http://www.mikii.fr/wp-admin/upload.php?page=wp-retina-2x&s=&view=issues
Thread Starter
Thibaut
(@aiacciu87)
Ok I guess it’s just errors related to the generation of the retina images in the admin…
The error.log file contains only this.
I am short of ideas…
Thread Starter
Thibaut
(@aiacciu87)
Now it seems to work (not very well) with the “Retina-Images” method only…
Don’t understand why. Before, everything was fine. Just changed URL without changing anything else in the settings (plugins etc.) β Everything seems to be OK except this plugin. Really strange.
I don’t think it’s the fact you changed URL. Actually I talked to somebody with the same issue. The theme had a line that cancelled the plugin’s process. It can be another plugin as well.
In your theme code (or other plugin) look for one of them that is using something called ob_start. Sometimes the theme is doing this to remove advertising or mention added by plugins… but it’s very hacky.
Thread Starter
Thibaut
(@aiacciu87)
Yes. In fact, the “somebody” guy was me. π
Indeed, ob_start was the problem.
Thanks Jordy.
Haha, it’s what I thought ^^
I probably need to add this ob_start issue in the FAQ.