Forum Replies Created

Viewing 15 replies - 16 through 30 (of 210 total)
  • Thread Starter inge12

    (@inge12)

    Thanks for the reply.
    1. I can’t see any warnings for my site. Core files are all fine. PHP is the same version as on other sites that work perfectly.
    2. All plugins were deactivated, and it made no difference. So I re-activated them.
    3. The same problem appears in the admin interface on browsers around the world – from Texas to Florida, Australia and Malaysia. So, no, it’s not my browser.

    I have actually found the cause – the file that shows the Dashboard interface. It is missing almost all links to CSS files for styling. It’s kind of like showing up undressed in public. ??

    I need to know which file to edit to solve the problem. Since the core files are all the same as for working sites, I suspect it’s a database issue, but I don’t know the innards of WordPress well enough to find the correct file.

    Thread Starter inge12

    (@inge12)

    H’mm… that didn’t exactly work. The Dashboard appearance did not change, but no “default theme” went into effect. I just got a message that the theme directory (which I renamed) does not exist. No site content showed up at all.

    Is there a way to set up a “default theme”?

    (I undid the change, and the public side of the site loads fine. Just the Admin section doesn’t have any styling whatsoever.)

    • This reply was modified 1 year, 11 months ago by inge12.
    Thread Starter inge12

    (@inge12)

    Thanks.
    Yes, I already deactivated all plugins. It made no difference at all. So I re-activated the most important ones – especially spam protection!

    Had not thought of simply deactivating current theme. That’s not something I had tried. That’s probably not it, but it’s worth a try.

    Thanks.

    Thread Starter inge12

    (@inge12)

    This is what I see in the Admin interface : https://ssnet.org/dl/admin.jpg

    Thread Starter inge12

    (@inge12)

    I see a link for reporting a *topic* as spam. But how do we report *comment spam,* like the comment above?

    Thread Starter inge12

    (@inge12)

    Increasing WP memory made no difference. We now have more severe issues, with the Admin interface being nearly unusable, and I’m not sure I can install a new plugin.

    Thread Starter inge12

    (@inge12)

    Thanks, but it seems to me there should be a reason for this happening. I have neither installed new plugins recently nor changed any plugin configuration. WordPress just stopped publishing queued posts out of the blue, after working flawlessly for 10 years or so on the same site!

    I take it on faith that a plugin will fix the situation, but it shouldn’t have to depend on a plugin. …

    First, I’ll increase the memory limit. I’ll see if that makes a difference.

    Thread Starter inge12

    (@inge12)

    Thanks. The post views are viewable in CPanel and in Google Webmaster. So I thought the plugin might be able to pick up those stats too.

    • This reply was modified 2 years, 1 month ago by inge12.
    Thread Starter inge12

    (@inge12)

    LOL! I was trying to mark this as “Resolved.” Maybe this time it will “take.”

    Thread Starter inge12

    (@inge12)

    Thanks again

    Thread Starter inge12

    (@inge12)

    Thank you for this! It helps me to know how to move forward.

    Thread Starter inge12

    (@inge12)

    After submitting a comment on a post (with DEBUG set to “false”), I get this list of error messages, which have to be intimidating for our users!

    `Deprecated: Function wpdb::escape is deprecated since version 3.6.0! Use wpdb::prepare() or esc_sql() instead. in /home/ssnet/public_html/wp-includes/functions.php on line 5401

    Warning: Cannot modify header information – headers already sent by (output started at /home/ssnet/public_html/wp-includes/functions.php:5401) in /home/ssnet/public_html/wp-includes/comment.php on line 569

    Warning: Cannot modify header information – headers already sent by (output started at /home/ssnet/public_html/wp-includes/functions.php:5401) in /home/ssnet/public_html/wp-includes/comment.php on line 570

    Warning: Cannot modify header information – headers already sent by (output started at /home/ssnet/public_html/wp-includes/functions.php:5401) in /home/ssnet/public_html/wp-includes/comment.php on line 571

    Warning: Cannot modify header information – headers already sent by (output started at /home/ssnet/public_html/wp-includes/functions.php:5401) in /home/ssnet/public_html/wp-content/plugins/litespeed-cache/src/vary.cls.php on line 729

    Warning: Cannot modify header information – headers already sent by (output started at /home/ssnet/public_html/wp-includes/functions.php:5401) in /home/ssnet/public_html/wp-includes/pluggable.php on line 1421

    Warning: Cannot modify header information – headers already sent by (output started at /home/ssnet/public_html/wp-includes/functions.php:5401) in /home/ssnet/public_html/wp-includes/pluggable.php on line 1424`

    Thread Starter inge12

    (@inge12)

    Well, you were right about the DEBUG setting. Thank you!
    I now set it to “false” and the relevant portion of the file now reads

    define (‘WPLANG’, ”);
    define (‘WP_DEBUG’, ‘false’);
    // ** Multi-site settings ** //

    However, I’m still getting this error:<blockquotDeprecated: Function wpdb::escape is deprecated since version 3.6.0! Use wpdb::prepare() or esc_sql() instead. in /home/ssnet/public_html/wp-includes/functions.php on line 5401

    • This reply was modified 2 years, 2 months ago by inge12.
    Thread Starter inge12

    (@inge12)

    Thanks. Last I checked WP_DEBUG was set to false. But I will check again.

    It seems like the highest number of warning messages originate here:

    Deprecated: Function wpdb::escape is deprecated since version 3.6.0! Use wpdb::prepare() or esc_sql() instead. in /home/ssnet/public_html/wp-includes/functions.php on line 5401

    I have no idea what to do about that. Is it a WordPress issue, or could it be a theme issue?

    Thread Starter inge12

    (@inge12)

    The anti-spam plugin seems to be working fine now.

    CleanTalk was not the culprit that slowed down the Admin section. It was another plugin.

Viewing 15 replies - 16 through 30 (of 210 total)