Make WordPress Core

Opened 17 years ago

Closed 17 years ago

#5097 closed defect (bug) (invalid)

Tag-related issues with wp_rewrite in 2.3

Reported by: kaeru's profile kaeru Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.3
Component: General Keywords:
Focuses: Cc:

Description

I'm having trouble getting tagging to work in 2.3. I've upgraded my blog without trouble. I have converted all my categories to tags, which went fine as well. The issue is when I try to update my permalinks for tags or display tags on my blog.

In the permalinks panel, it throws the following error after I try to specify a tag base.

Fatal error: Call to undefined method WP_Rewrite::set_tag_base() in /home/.pug/karsalfrink/leapfrog.nl/blog/wp-admin/options-permalink.php on line 81

On the blog, it throws the following error for the template tag

<p><?php the_tags(); ?></p>

Fatal error: Call to undefined method WP_Rewrite::get_tag_permastruct() in /home/.pug/karsalfrink/leapfrog.nl/blog/wp-includes/category-template.php on line 423

And this error on the archive page where I try to display a default tag cloud using

<?php wp_tag_cloud(''); ?>

Fatal error: Call to undefined method WP_Rewrite::get_tag_permastruct() in /home/.pug/karsalfrink/leapfrog.nl/blog/wp-includes/category-template.php on line 423

I've done some digging and found this page:

http://codex.wordpress.org/Function_Reference/WP_Rewrite

Where it says:

It's defined in wp-includes/wp-classes.php and a global singleton, $wp_rewrite, is initialised in wp-settings.php.

I can find the initialisation in wp-settings.php, but there is no wp-classes.php in my wp-includes directory. Furthermore, I cannot find the file in the WordPress distribution I downloaded on the morning of sep 28.

Finally, I have verified this is not a theme issue by testing one of the prepackaged themes. The default theme throws exactly the same errors as my own.

Any help would be greatly appreciated.

Change History (4)

#1 @kaeru
17 years ago

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

#2 @kaeru
17 years ago

A clean install of WordPress resolved this issue.

#3 @Nazgul
17 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

#4 @Nazgul
17 years ago

  • Milestone 2.5 deleted
  • Resolution set to invalid
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.