Kajuna

Awesome, thanks for your help!

Surprisingly, the problem just disappeared yesterday on my production site. No idea if it was a change in the server or what. So it could also come back for no reason, who knows?

@tatsuya Thanks but I don’t use wp-flickr-rpess, I don’t see anything wrong in the console.

Thanks anyway

I do have pissed clients because of this.

Currently on 4.9.4, the problem with the media library not loading on grid and not being able to attach featured images to posts happens on any theme and with no plugins activated.

Strangely enough, it does not happen on another installation, on a different server, so the problem might also be dependent on server settings.

Completely at a loss.

Hi @lazykins,

Thanks for sharing your solution. That did not work for me. Can I ask why you went that route?

Thanks

Same problem here. And quite some more reports on the same issue on plugin forums, etc.

Same problem here. Changing the language or the user language to anything does not solve it for me

• This reply was modified 7 years ago by Kajuna.

Hi @tatsuya ,

Could you share what the problem was specifically? I don’t have wp-flickr-press installed but am experiencing the same problem with the media library, so maybe knowing what caused yours can help me debug the issue.

Much appreciated

My hosting provider solved it by disabling ModSecurity from cPanel

Thanks but no, I already went through all the related Google results. The problem is not on my browser or computer or Internet service. Do you not experience the same problem when commenting on the links I provided?

Tried with an older version of WordPress, 4.6 Still the same: https://ateneu.elteu.cat/test2/2017/02/21/hello-world/

And I’ve tried changing .htaccess to anything I could find online, related to comments.

I really am at a loss. Is there some php or apache setting that I should look into?

In fact, I just installed a clean WordPress instance on the same server and comments still don’t work: https://ateneu.elteu.cat/test/2017/02/21/hello-world/

Yes, And I have tried re-uploading the WordPress system (I was already on the latest version), disabled all plugins, changed the folder name to force-disable them…

I’m trying to reply here, but my posts keeps disappearing. I just wanted to say that logs or debugging do not show anything related

Thanks.

The server logs don’t show any error at the time the frontend crashes. I get these errors on any page, when I enable debugging, but they also happen in my server, so they don’t seem to be related to the problem:

Notice: The called constructor method for WP_Widget in stag_widget_contact is deprecated since version 4.3.0! Use
__construct()
instead. in /var/www/tailorandwayne.com/public_html/ateneuelteu/wp-includes/functions.php on line 3891

Notice: The called constructor method for WP_Widget in stag_widget_cta is deprecated since version 4.3.0! Use
__construct()
instead. in /var/www/tailorandwayne.com/public_html/ateneuelteu/wp-includes/functions.php on line 3891

Notice: The called constructor method for WP_Widget in stag_widget_hero is deprecated since version 4.3.0! Use
__construct()
instead. in /var/www/tailorandwayne.com/public_html/ateneuelteu/wp-includes/functions.php on line 3891

Notice: The called constructor method for WP_Widget in stag_widget_intro is deprecated since version 4.3.0! Use
__construct()
instead. in /var/www/tailorandwayne.com/public_html/ateneuelteu/wp-includes/functions.php on line 3891

Notice: The called constructor method for WP_Widget in stag_widget_recent_projects is deprecated since version 4.3.0! Use
__construct()
instead. in /var/www/tailorandwayne.com/public_html/ateneuelteu/wp-includes/functions.php on line 3891

Notice: The called constructor method for WP_Widget in stag_widget_static_content is deprecated since version 4.3.0! Use
__construct()
instead. in /var/www/tailorandwayne.com/public_html/ateneuelteu/wp-includes/functions.php on line 3891

• This reply was modified 8 years, 1 month ago by Kajuna.