Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter matt richards

    (@matt-richards)

    BINGO!!!!!!
    There were 2 spaces at the end of config file.
    I have disabled plugins and now can log in!!!!!

    Found 2 guilty plugins that I don’t use anyway.

    Thanks so much for you help and patience, I can start clearing the office for our Christmas holiday now!

    Thread Starter matt richards

    (@matt-richards)

    Thanks Esmi,

    I have tried this but I get the following when deactivating plugins on the login page;

    Warning: Cannot modify header information – headers already sent by (output started at /home/mattr752/public_html/wp-config.php:153) in /home/mattr752/public_html/wp-login.php on line 349

    Warning: Cannot modify header information – headers already sent by (output started at /home/mattr752/public_html/wp-config.php:153) in /home/mattr752/public_html/wp-login.php on line 361

    And then this after trying to log in

    Warning: Cannot modify header information – headers already sent by (output started at /home/mattr752/public_html/wp-config.php:153) in /home/mattr752/public_html/wp-login.php on line 349

    Warning: Cannot modify header information – headers already sent by (output started at /home/mattr752/public_html/wp-config.php:153) in /home/mattr752/public_html/wp-login.php on line 361

    Warning: Cannot modify header information – headers already sent by (output started at /home/mattr752/public_html/wp-config.php:153) in /home/mattr752/public_html/wp-includes/pluggable.php on line 669

    Warning: Cannot modify header information – headers already sent by (output started at /home/mattr752/public_html/wp-config.php:153) in /home/mattr752/public_html/wp-includes/pluggable.php on line 670

    Warning: Cannot modify header information – headers already sent by (output started at /home/mattr752/public_html/wp-config.php:153) in /home/mattr752/public_html/wp-includes/pluggable.php on line 671

    Warning: Cannot modify header information – headers already sent by (output started at /home/mattr752/public_html/wp-config.php:153) in /home/mattr752/public_html/wp-includes/pluggable.php on line 866

    I tried this first with plugins disabled. And then again with all themes except twenty eleven moved out of themes folder aswell.

    Thread Starter matt richards

    (@matt-richards)

    I worked through the “find and replace” process, creating a new database.

    Exactly same result. Blank screen.

    I have added the WP_DEBUG and get the following;

    Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    I am still running the new database, (with the corrected absolute paths).

    Thread Starter matt richards

    (@matt-richards)

    Ok I found a video tutorial to dump the database

    opening the .sql file in text edit, and doing a “find” for the old root path does bring up a lot of results.

    Could this be the fix? If so how do I run a “find & replace” in the database?

    Thread Starter matt richards

    (@matt-richards)

    Would you be able to give a step by step on that database dump?

    I did run a debug earlier but this is beyond my realms.

    This is the log it reported.

    [21-Dec-2011 19:09:41] PHP Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:41] PHP Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:46] PHP Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:46] PHP Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:53] PHP Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:53] PHP Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:54] PHP Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:54] PHP Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:58] PHP Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:09:58] PHP Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:10:00] PHP Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:10:00] PHP Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:10:04] PHP Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:10:04] PHP Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:10:20] PHP Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    [21-Dec-2011 19:10:20] PHP Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/mattr752/public_html/wp-includes/functions.php on line 3578

    Thread Starter matt richards

    (@matt-richards)

    I’ve subsequently moved other sites (add-on domains) without a problem so I doubt that it is the server causing this?

    Thread Starter matt richards

    (@matt-richards)

    Thanks but I was following that post’s instruction.

    The URLS remain the same so should of just been a simple change of the config. file.

    Thread Starter matt richards

    (@matt-richards)

    Thanks, for your help Amitash, unfortunately I tried including the backslash but now have a blank screen (as opposed to the live’s site links) when navigating to https://www.nameofsite.com/wptest/

    I agree with you about the .htaccess file, which is why I have included it in the original post. The code (above) is what is existing in the current .htaccess file, located in the root of the content managed site.

    Interestly by adding the backslash, a .htaccess file is now in the wptest folder.

    RewriteEngine On
    
    RewriteRule ^([a-zA-Z0-9\--]+)/$ index.php?p=$1 [L]
    RewriteRule ^([a-zA-Z0-9\--]+)$ index.php?p=$1 [L]
    
    RewriteRule ^([0-9]+)-(.*).html$ index.php?id=$1&page=$2&p=news [L]
    RewriteRule ^news-([0-9]+).html$ index.php?page=$1&p=news [L]
    
    ErrorDocument 404 /index.php
    Options -Indexes
    # 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

    By editing this .htaccess file, The live site no longer worked there I have had to restore the original .htaccess file. Potentially I need an alternative workaround?

Viewing 8 replies - 1 through 8 (of 8 total)