• Resolved brandonchicago

    (@brandonchicago)


    I upgraded this morning and now my visual and text editors are blank boxes with no content. Disabled all plugins and changed the theme to Twenty Eleven, still no love. Tried in FF 17 and latest version of Chrome.

Viewing 15 replies - 31 through 45 (of 61 total)
  • Great cooperation guys πŸ™‚

    Thanks Otto for providing the helpful insight and AITpro for the extremely fast involvement!

    Thread Starter brandonchicago

    (@brandonchicago)

    Thanks AITpro & Otto! Really appreciate the help in getting that great plugin to play nice with WP again.

    Thanks guys but I tried this (had BulletProof a long time ago) and it still isn’t working. My HTACCESS looks like this:

    # BULLETPROOF PRO 5.D DEFAULT .HTACCESS

    # If you edit the line of code above you will see error messages on the BPS Security Status page
    # WARNING!!! THE default.htaccess FILE DOES NOT PROTECT YOUR WEBSITE AGAINST HACKERS
    # This is a standard generic htaccess file that does NOT provide any website security
    # The DEFAULT .HTACCESS file should be used for testing and troubleshooting purposes only

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    Thanks!

    Okay so I figured it out.
    Not only do you have to do DEFAULT BPS Mode. You have to (more importantly?) activate Default mode for your wp-admin htaccess file taht BPS creates.

    Uninstalling this plugin now.. πŸ™

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    Reinharts (and anyone else who isn’t using BPS) – Please make your own topic πŸ™‚

    When a topic is resolved, we generally don’t come back to look to help people. It’s totally okay (encouraged!) to make your own topics πŸ˜€

    BPS .47.7 has been released. All Square Brackets characters are no longer filtered in either the Root .htaccess file or the wp-admin .htaccess file. The upgrade to .47.7 will automatically preg_replace the “bad” filters with new filters. Should have been done a long time ago – it would saved me a fortune in unneeded bottles of Aspirin. πŸ˜‰

    This fix from X111zen worked for me

    Just add this to your wp-config file : define(‘SCRIPT_DEBUG’, true);

    Thank you all above! Resolved!

    I deactivated “CKEditor for WordPress” plugin and it solved the problem

    It was indeed BPS that was causing problems, all good now

    This worked for me!!! THANK YOU πŸ™‚

    Mark

    (@mark-bremmer)

    @aitpro:
    There is a Pro fix coming soon? I tried the #RewriteCond %{QUERY_STRING} ^.*(\[|\]|\(|\)|<|>).* [NC,OR] solution and did not have success.

    @mark Bremmer – BPS Pro 5.3.3 was released yesterday that also automatically fixes this issue. If you are not seeing the upgrade notification in your WP Dashboard:

    1. Click on the “Updates” Link under your WordPress Dashboard panel (topmost left link is the Dashboard panel).

    2. Click on the Check Again button.

    3. Refresh your Browser.

    You should now see an upgrade notification displayed in your WordPress Dashboard for BPS Pro.

    If you still do not see an update/upgrade check notification in your WordPress Dashboard then go to the WordPress Plugins page and Refresh your Browser.

    If you still do not see a BulletProof Security Pro update/upgrade check notification in your WordPress Dashboard then deactivate any other security plugins you have installed on your website and go to the WordPress Plugins page and refresh your Browser.

    If you still do not see a BulletProof Security Pro update/upgrade check notification in your WordPress Dashboard then deactivate all plugins and go to the WordPress Plugins page and refresh your Browser.

    Mark

    (@mark-bremmer)

    Perfect. All is working correctly again. Thank you!

Viewing 15 replies - 31 through 45 (of 61 total)
  • The topic ‘Post Editor missing in WP 3.5 after upgrade’ is closed to new replies.