Permalink Bug in Wordpress 2.6

[papagmp]

And I thought I was going fucking crazy

http://wordpress.org/support/topic/189058
http://wordpress.org/support/topic/188959
http://trac.wordpress.org/ticket/7306

Just installed the newest version and it's broke but the fuckers have the ticket closed - you have to do a hack of the index.php and I'm just not feeling that today.

[papagmp]

This may help: http://farm4.static.flickr.com/3228/...6c738559_o.png

[Lemmy]

Seems 2.6 is a little buggy still. I just upgraded one of my blogs, and while the permalinks are fine, the damn thing ate my categories.

[cd34]

http://trac.wordpress.org/browser/tr...s.php?rev=8213
http://trac.wordpress.org/browser/tr...e.php?rev=8213

At the bottom, click:

Download in other formats: Plain Text

save both

upload to your wp-includes directory over top of the originals and you should be set.

[ladydesigner]

Does anyone know what will happen to my blogs if I don't do the upgrade to wordpress 2.6? I keep hearing about all these bugs and am nervous about upgrading.

[Useless]

Originally Posted by ladydesigner

Does anyone know what will happen to my blogs if I don't do the upgrade to wordpress 2.6? I keep hearing about all these bugs and am nervous about upgrading.

HotWifeBlog (not mine) has an Alexa Ranking of 75k and runs on WP 1.5. Once you have a stable version, there is no reason to upgrade unless you REALLY must have the latest, coolest plugin that comes along. (and basic SEO will do more for you than all those funky plugins) I wonder if there is a repository for all the old versions of WP, you know, the ones that actually performed as expected?

[Lemmy]

Originally Posted by Useless Warrior

I wonder if there is a repository for all the old versions of WP, you know, the ones that actually performed as expected?

There is a release archive with all the previous versions. On one of my blogs I had to "downgrade" to restore functionality in a theme that the latest upgrade broke.

I researched my problem (missing categories) and it appears to be a bug in the upgrade script they've known about for weeks, yet it's still in the latest version I downloaded yesterday. If you have an older blog (2.1/2.2) do NOT go straight to 2.6 (you'll lose your cats), but do an "intermediate upgrade" to 2.3 first and you should be fine.

Or you could just not upgrade at all. If it ain't broke, is stable and does what you want it to, why bother (I keep asking myself )?

Oh yeah, if you do upgrade, make sure to back up your database. If you don't and something goes wrong you might end up just a little bit fucked.

[ladydesigner]

Thanks UW. That was exactly what I was hoping to hear. I have no desire to upgrade to an unstable version of WP.

[LD]

I usually stay 1 or 2 releases behind, and skipped a couple. I haven't even been blogging that long, and they've already released 6 or so. I'll bet people that have a gazillion blogs curse a lot when they see that little new version message in the admin panel...

I've noticed sometimes the upgrade will cause problems with a certain theme, and swapping the theme fixes the problem. Of course, most times that's not really a fix since you want to keep your theme.

Hopefully it's just a matter of time before they streamline the upgrade process, particularly for those with multiple blogs.

[walrus]

Personally I'm getting pretty tired of WP. Ever since they went to having a release every 6 weeks or what ever the reliability of the script has went to shit. They find a bug but rarely fix it in the current release, you have to wait till the next release for the fix but that often has just as many other problems.

It's almost like your in a constant state of beta test. Plus if you customize your theme, they have no problem depreciating tags which means you can spend hours fixing your theme or changing themes and spend hours customizing it the way you want. Both are not good for something your using to generate money with.

I really like how you can find a plug-in for anything you want to do but....

[cd34]

Regrettably, there are some security holes in xmlrpc.php through to 2.5.0. There is one in 2.5.1, but, noone has captured it, so, wordpress disabled remote publishing through xmlrpc for new installs in 2.6.

here's a hack that involves wordpress sites up through 2.5.1. View source on one of the resulting sites and search for kvantservice. While we've not been able to capture how this particular hack was done, I still believe there is a hole in 2.5.1 (and 2.6 since they made no changes to xmlrpc other than to turn off remote publishing for new installs, I don't believe 2.6 is secure if you use wordpress for the iphone or any of their desktop publishing widgets. I believe the kvantservice attack happened through a google scan to find wordpress sites, it then read the post from the front page (possibly even the google cache) to get the post id, then forced its update through xmlrpc. The reason we think they looked at the front page only is because almost every republished post breaks at the More... marker. which sort of proves they didn't read the entire post.

The site running 1.5 might be running WPMU -- its version numbers haven't kept up with the personal version and their current WPMU is 1.5.1

The problem that one particular client and I have been having with wordpress is that security updates are not kept separate from feature upgrades. And those feature upgrades almost always break functionality or remove features to make the product simpler. The permalink error is just one of many. Another irritating addon is revisions. Every time a post is kept, the revision is kept. Because they save that revision in the post table, and, that table is poorly indexed and the queries against it are poorly written, a blog with 10000 posts, each with a revision or two because you cleaned up typographic quotes, becomes a blog with 40000 posts. Their initial version of revisions kept the revisions in a separate table. Around the 4th prerelease of 2.6, it was put in the main wp_posts table.

If I were to settle on a version, I think I would settle on 2.5.1 because that xmlrpc bug doesn't seem to be well known and I've only seen it hit a few times. The bug on 2.3 is rather rampant and I have the xml payload that can exploit that. Wordpress has closed that vulnerability in 2.4. The exploit script is publicly available on many different hacker boards.

[digifan]

It is not too safe to upgrade to a new version imho.. it makes sense to wait a bit for like 2.6.1 or similar.

[cd34]

2.6 isn't bad as a fresh install. And due to poor documentation in prior versions, PapaGMP ran into the index.php/permalink issue because it was never expected by wordpress that someone would do that.

If you started a blog from scratch, and were relying on templates developed from the community, and you didn't want the performance hit from that awful tag cloud query, 2.6 is about your only choice. If you have an older version, I would upgrade to 2.5.1 and stick there. You still have the awful tag-cloud issue, but, you would give wordpress the time to release 2.6.1 which will probably fix a lot of the 2.x -> 2.6 migration issues.

[ronnie]

I just installed 2.6 fresh on a new domain, mainly to check it out. I really can't see anything that 2.5.1 doesn't already do, least on the surface. I read the whats new in 2.6 on the wordpress site and still don't really see any major advancements that would help me. Am I missing something?

Thinking I'll just stick with 2.5.1

[Beaver Bob]

Has anyone managed to use an RSS reader plugin successfully on 2.6? I can't find one

edit: post 420!!!!!!!

[cd34]

Feedwordpress works in 2.6

If I understood what you were looking for.

[Beaver Bob]

Originally Posted by cd34

Feedwordpress works in 2.6

If I understood what you were looking for.

yep! thanks