wpautop

  • Resolved syncbox

    (@syncbox)


    14 years, 11 months ago

    OK, after a long struggle, I convinced a site owner to upgrade their site from 2.3.3 to the latest version 2.7x

    However, while the site is functioning after bringing in the data to the new dev. version of their site (we’re doing it there, modifying the data from the main domain to a subdomain in anticipation of a re-design)…

    I cannot get to the wp-admin portion of the site — I get the following error

    remove_filter(‘term_description’,’wpautop’);

    At first, it was saying that there was an issue with the pluggable.php file in the includes… I commented out those lines and now am left with just the above appearing rather than a login screen or anything else.

    Any ideas?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter syncbox

    (@syncbox)

    14 years, 11 months ago

    Wow, this is really messed up… I can see the entire site but cannot get to any admin functions… I get pluggable.php and functions.php errors out the ying-yang and don’t know what to do about them.

    Other than removing plugin files from that folder, i cannot disable the plugins because I cannot access the admin.

    I cannot take down or work on the original site (it has to stay up)

    Any ideas anyone?

    I am getting this:

    remove_filter(‘term_description’,’wpautop’);
    Warning: Cannot modify header information – headers already sent by (output started at /home/schobla8/public_html/dev/wp-content/themes/maggieb/functions.php:1) in /home/schobla8/public_html/dev/wp-includes/pluggable.php on line 850

    If I comment out that big in pluggables, I just get other similar errors or just the first line…

    stvwlf

    (@stvwlf)

    14 years, 11 months ago

    Yes, remove the comments you put in pluggable.php and fix the problem that was causing the legitimate error message it was trying to convey.

    The line that is displaying is a line of PHP code that is being displayed as text rather than executed, probably because the commenting you did modified its context within the file.

    You should never comment out code in a WordPress core file.

    Thread Starter syncbox

    (@syncbox)

    14 years, 11 months ago

    Nevermind. I figured it out myself. There was a functions.php file in the theme that I removed and now all is at least accessible.

    Thanks anyway.

    stvwlf

    (@stvwlf)

    14 years, 11 months ago

    the error messages about functions.php mean that you have white space (text, newline, space, whatever) before and/or after the opening and closing PHP tags at the top and bottom of your theme’s functions.php file. Remove it and the error message should go away. Since its on line one, its likely at the top.

    Shane

    (@shamess)

    14 years, 11 months ago

    Like Stvwlf said, it’s best not to mess around with core WordPress files.

    The original problem was probably caused by remove_filter('term_description','wpautop'); being echoed for some reason (maybe it was put outside of the scope of the <?php ?> tags). Just go through each of plugins (back them up) and delete them one by one till the site starts working. Put all the rest back until you’ve found out what the problem with the trouble causing plugin is.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘wpautop’ is closed to new replies.