WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#4831 closed defect (bug) (invalid)

Slugged by svn update; suspect wp-app.php version 5954

Reported by: jcwinnie Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: Cc:

Description

ugs'); add_action('edit_form_advanced', 'wp_remember_old_slug'); ?>) return wp_specialchars($matches[0]); return $matches[0]; } ?> '$term'"); } } ?>

appears at top of page

ugs'); add_action('edit_form_advanced', 'wp_remember_old_slug'); ?>) return wp_specialchars($matches[0]); return $matches[0]; } ?> '$term'"); } } ?>

appears after the Need Help content of Manage Posts

ugs'); add_action('edit_form_advanced', 'wp_remember_old_slug'); ?>) return wp_specialchars($matches[0]); return $matches[0]; } ?> '$term'"); } } ?>

appears under Latest Activity

switching from k2 to default fails to help

all plugins disabled; any plugin action gets error msg:

ugs'); add_action('edit_form_advanced', 'wp_remember_old_slug'); ?>) return wp_specialchars($matches[0]); return $matches[0]; } ?> '$term'"); } } ?>
Warning: Cannot modify header information - headers already sent by (output started at /home/jcwinnie/public_html/wordpress/wp-includes/default-filters.php:147) in /home/jcwinnie/public_html/wordpress/wp-includes/pluggable.php on line 412

Warning: Cannot modify header information - headers already sent by (output started at /home/jcwinnie/public_html/wordpress/wp-includes/default-filters.php:147) in /home/jcwinnie/public_html/wordpress/wp-includes/pluggable.php on line 412

Change History (5)

comment:1 DD327 years ago

output started at /home/jcwinnie/public_html/wordpress/wp-includes/default-filters.php:147

default-filters is only 145 lines long for me on the latest install, It sounds like you've got some extra code in there (I suspect an extra ?>
Maybe try deleteing that file and then doing another update.

comment:2 jcwinnie7 years ago

Removed filed, re-ran svn update

Hm, made a difference, but failed to remove garbage, which now reads:

) return wp_specialchars($matches[0]); return $matches[0]; } ?> '$term'"); } } ?>

comment:3 DD327 years ago

  • Milestone 2.3 deleted
  • Version 2.3 deleted

) return wp_specialchars($matches[0]); return $matches[0]; } ?>

is:

output started at /home/jcwinnie/public_html/wordpress/wp-includes/formatting.php:1219

'$term'"); } } ?>

Is coming from /wp-includes/taxonomy.php

Deleteing the file might not've been the best idea, For some reason other content has sliped into your install, it might just be a corruption, it might've been SVN couldnt update properly, or it might've been that someone has slipped something else into your install..

I'd suggest save taxonomy.php and formatting.php to your computer, delete them both from the server and run an update again.
You can send the files over to me at wordpress@…[dot]au if you want to know whats happened to them.

I'd personally Wipe the install(beside from the config file and wp-content) and put a fresh copy on just in case other files are affected if its not just SVN not managing to update correctly.

comment:4 DD327 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Looks like you've got it working now.
Closing as invalid(as it doesnt look to be WP's fault)

comment:5 westi7 years ago

Note svn does funky things when it cannot merge your local changes with the changes incoming due to the svn up - this will leave you with extra files (.orig for example) and probably busted php script until you fix it.

This is shown in the output of svn up I believe with a C in the output column (http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.update.html)

Note: See TracTickets for help on using tickets.