WordPress.org

Ready to get started?Download WordPress

Forums

Bug in newest wordpress version (9 posts)

  1. hanshans
    Member
    Posted 1 year ago #

    Hello guys, since the newest version, this bug is in it: click here

  2. Andrew
    Forum Moderator
    Posted 1 year ago #

    Please post the contents of your problem here. The other thread will be closed.

  3. adpawl
    Member
    Posted 1 year ago #

  4. hanshans
    Member
    Posted 1 year ago #

    I have this bug on every website, so it's something with the newest wordpress...

    My selfmade seo titles are not working anymore in google, I only see the name of the post or page as seo title (meta descriptions still working fine) Maybe it has to do with this issue.

    I get this warning: Warning: Cannot modify header information - headers already sent by (output started at /home/hans/public_html/symptomenoverspannen.com/wp-admin/includes/template.php:1642) in /home/hans/public_html/symptomenoverspannen.com/wp-includes/pluggable.php on line 876

    I can only find the template file on filezilla, not the pluggable.php file. But I have changed the pluggable.php file on my server.

    So it looks now like:

    $r .= "<tbody>\n$diff\n</tbody>\n";
    $r .= "</table>";

    return $r;
    }
    endif;
    ?>

    But Im not sure what is wrong with line 1642 in my template, what do I have to change exactly?:

    <html xmlns="http://www.w3.org/1999/xhtml" class="ie8 <?php echo $admin_html_class; ?>" <?php do_action('admin_xml_ns'); ?> <?php language_attributes(); ?>>

    I already did what you said adpawl, but thanks for your input.

    So again: I have this problem on every new wordpress website, so it is not only one website, something is wrong with the newest script

  5. catacaustic
    Member
    Posted 1 year ago #

    The error messages that you have posted are not the actual place that the error is occuring. I know that sounds strange, but the fault isn't in those files. From my experience, anything that causes an error like that in plugable.php means that you have a plugin that's causing the error, not the core WP files.

    If you deactivate ALL of your plugins I'll bet that the problem goes away. From there you just need to re-enable each plugin one at a time and see which one causes the error to show again.

  6. kmessinger
    Volunteer Moderator
    Posted 1 year ago #

    I have this bug on every website, so it's something with the newest wordpress...

    No, not really as many thousands of people do not have a problem.

    But I have changed the pluggable.php file on my server.

    Do not change any core wordpress files.

    Work your way thru this list. http://wordpress.org/support/topic/troubleshooting-wordpress-35-master-list?replies=4

  7. hanshans
    Member
    Posted 1 year ago #

    The error messages that you have posted are not the actual place that the error is occuring. I know that sounds strange, but the fault isn't in those files. From my experience, anything that causes an error like that in plugable.php means that you have a plugin that's causing the error, not the core WP files.

    If you deactivate ALL of your plugins I'll bet that the problem goes away. From there you just need to re-enable each plugin one at a time and see which one causes the error to show again.

    okay some other guys told me to look on the lines, but what you said is completely possible yes, because of this:

    No, not really as many thousands of people do not have a problem.

    next quote:

    Do not change any core wordpress files.

    Work your way thru this list. http://wordpress.org/support/topic/troubleshooting-wordpress-35-master-list?replies=4

    okay I read the list. The problem only shows everytime up when installing the wordpress seo plugin by yoast. And the only visible problem for me is: not working seo titles. I see only the page or post name in google. So I think that happens because of this plugin, message.

    So what is the next step for me now? Because I really like the SEO plugin from yoast, but I think a bug is in this plugin right? So what to do now?

  8. fonglh
    Member
    Posted 1 year ago #

    Let the plugin author know, but first check if there's a new version of the plugin which might already have fixed your issue.

  9. hanshans
    Member
    Posted 1 year ago #

    okay I posted it on his specific forum

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.