Elpie

Arras 1.5.0 had a number of issues. Its possible that the newest release does too. Have you asked on their forum? https://www.arrastheme.com/forums/forum11-guides-database.html

You don’t need a function, just add this to your theme’s functions.php

remove_action('wp_head', 'adjacent_posts_rel_link_wp_head', 10, 0 );

Note the change to adjacent_posts_rel_link_wp_head in 3.2.

It’s not working well for me on Firefox 4 or in the latest Opera either. There are too many errors for me to be able to offer a quick fix. If you correct these your site should work okay.
https://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.cleanairspace.com%2Fw20%2F

You should NEVER, EVER use the GUID in your site. It is a globally unique identifier for RSS readers. RSS feeds use the GUID to know which posts have been published, so they don’t republish the same content over and over. It’s not a permalink (even though it looks like one) and due to inconsistencies in behaviour over the years its not even necessarily unique, so trying to use it within WordPress itself will cause a whole lot of pain.

If you need to get an ID you need to use $post_id.

You need to use the post ID, not guid. The GUID might look like a permalink but its not, and cannot be used as one. Essentially, the GUID only exists for RSS feed readers, and its supposed to work like a globally unique identifier. It’s not a link.
If using it as a link is sending you to a different site that is because the URL of the old site is stored as part of the unique identifier. Don’t change this because it messes up RSS feeds. Just use the correct ID of the post instead.

Authentication failed messages usually mean that Twitter cannot identify the application that is calling it. Make sure you have the correct API keys and tokens from Twitter. You get them after signing up at: https://dev.twitter.com/apps/new

That’s happened to me on one of my sites. Sorry, I can’t help you fix it – I just rolled back to 2.8.6 and will wait until at least after 2.9.1 before I upgrade that site again.

PHP version 5.2.6
MySQL version 5.0.67

definitely a FTP password hack.

I think most people who were hacked had Adobe Reader 8.0 and using FileZilla

This is plain rubbish! I’ve also had sites hacked with both JavaScript injection and iframe. Not only is FTP not used, its not even enabled on the server. Interestingly, the attack vectors show that entry was gained from a core WordPress file.

I had just written a report for the WP core devs when I saw the announcement about the release of WordPress 2.8.1.
Everyone should upgrade as soon as possible.

More information on known vulnerabilities (some of which have been fixed in 2.8.1) is here: https://corelabs.coresecurity.com/index.php?module=FrontEndMod&action=view&type=advisory&name=WordPress_Privileges_Unchecked

I wouldn’t bother with patching anything – just download and install WP 2.8.1 RC. The latest is RC2 and it seems to be pretty stable.

Cheers – I’m actually filtering out all dynamic classes now as they accounted for an increase of 50% in file sizes on my themes.

@pariahdesign – if you are still getting errors on the loop in the wp_santize_redirect function (which uses _deep_replace() ) in 2.8.1 beta 2 perhaps you might want to reopen this ticket and report it. https://core.trac.www.ads-software.com/ticket/10226

I haven’t experienced this problem with beta 1 so the issue may be getting triggered by the environment.

Try 2.8.1 Beta 2 to see if this makes a difference. There was a change to this after beta 1.

This is a Firefox bug – if you use the last stable release of FF you shouldn’t have this problem. 3.5 has not been released yet and is still under development.

I’m not part of WordPress, just a 3rd party hacker, but even so I think a couple of points should be made…

1. WordPress Codex says, “deactivate plugins before upgrading” (https://codex.www.ads-software.com/Upgrading_WordPress) and people who don’t are really asking for trouble. Plugins are mini-applications that hook into WordPress and either change or build on WordPress core functionality. It is only logical that when the underlying core code changes then plugins can cause problems.

2. WordPress tells everyone to take backups before upgrading. These backups are important as many things can go wrong with an upgrade – even things that are outside of WordPress itself. Restoring from backup is relatively easy, as long as the backups exist.

3. WordPress, like all open source projects, relies on its community to test code. WP 2.8 had beta releases and a release candidate before it was finally released. Most of the issues that were raised during the testing phase were fixed before WordPress 2.8 was released but obviously everyone uses different server setups with different versions of PHP and MySQL so the few people who did test could not test on all platforms.

Which brings me to my final point – if everyone was prepared to test the beta’s and release candidates and provide feedback to the developers, a lot of these problems would not occur.

Even opening or adding to tickets on the tracker is helpful. https://core.trac.www.ads-software.com/

All open source depends on users to feed information back to the developers. I share the frustration of everyone in this thread (perhaps even more frustration since I spent time testing the betas and RC1, with no problems until I put this onto live blogs) but, really, venting in the forum doesn’t help. If we report the issues in the tracker and they don’t get fixed, THEN we really have grounds for complaint ??

It’s a bug & you were just lucky to have it ??