Title: Elpie's Replies | WordPress.org

---

# Elpie

  [  ](https://wordpress.org/support/users/elpie/)

 *   [Profile](https://wordpress.org/support/users/elpie/)
 *   [Topics Started](https://wordpress.org/support/users/elpie/topics/)
 *   [Replies Created](https://wordpress.org/support/users/elpie/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/elpie/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/elpie/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/elpie/engagements/)
 *   [Favorites](https://wordpress.org/support/users/elpie/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 52 total)

1 [2](https://wordpress.org/support/users/elpie/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/elpie/replies/page/3/?output_format=md) 
[4](https://wordpress.org/support/users/elpie/replies/page/4/?output_format=md) 
[→](https://wordpress.org/support/users/elpie/replies/page/2/?output_format=md)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Not able update publish post in WP theme Arras.1.5.1 with wordpress 3.2](https://wordpress.org/support/topic/not-able-update-publish-post-in-wp-theme-arras151-with-wordpress-32/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/not-able-update-publish-post-in-wp-theme-arras151-with-wordpress-32/#post-2188847)
 * Arras 1.5.0 had a number of issues. Its possible that the newest release does
   too. Have you asked on their forum? [http://www.arrastheme.com/forums/forum11-guides-database.html](http://www.arrastheme.com/forums/forum11-guides-database.html)
 *   Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/)
   
   In reply to: [Remove adjacent_posts_rel_link links under WP3.2](https://wordpress.org/support/topic/remove-adjacent_posts_rel_link-links-under-wp32/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/remove-adjacent_posts_rel_link-links-under-wp32/#post-2187766)
 * 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.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Absolute Positioning not working on IE!](https://wordpress.org/support/topic/absolute-positioning-not-working-on-ie/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [15 years ago](https://wordpress.org/support/topic/absolute-positioning-not-working-on-ie/#post-2067200)
 * 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.
    [http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.cleanairspace.com%2Fw20%2F](http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.cleanairspace.com%2Fw20%2F)
 *   Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/)
   
   In reply to: [All GUIDs are the same since upgrading](https://wordpress.org/support/topic/all-guids-are-the-same-since-upgrading/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [15 years ago](https://wordpress.org/support/topic/all-guids-are-the-same-since-upgrading/#post-1626667)
 * 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.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Recent posts linking to another site?](https://wordpress.org/support/topic/recent-posts-linking-to-another-site/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [15 years ago](https://wordpress.org/support/topic/recent-posts-linking-to-another-site/#post-1905409)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Tools for Twitter] [Plugin: Twitter Tools] Authentication Failed](https://wordpress.org/support/topic/plugin-twitter-tools-authentication-failed/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-twitter-tools-authentication-failed/#post-1646745)
 * 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: [http://dev.twitter.com/apps/new](http://dev.twitter.com/apps/new)
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Cannot edit Posts or Insert graphics after Upgrading to 2.9](https://wordpress.org/support/topic/cannot-edit-posts-or-insert-graphics-after-upgrading-to-29/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 4 months ago](https://wordpress.org/support/topic/cannot-edit-posts-or-insert-graphics-after-upgrading-to-29/#post-1316260)
 * 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
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Someone put a iframe on index.php file](https://wordpress.org/support/topic/someone-put-a-iframe-on-indexphp-file/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/someone-put-a-iframe-on-indexphp-file/#post-1097961)
 * >  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: [http://corelabs.coresecurity.com/index.php?module=FrontEndMod&action=view&type=advisory&name=WordPress_Privileges_Unchecked](http://corelabs.coresecurity.com/index.php?module=FrontEndMod&action=view&type=advisory&name=WordPress_Privileges_Unchecked)
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Error when upgrading to WP2.8](https://wordpress.org/support/topic/error-when-upgrading-to-wp28/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/error-when-upgrading-to-wp28/page/2/#post-1101953)
 * 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.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Filter out categories and tags from post_class](https://wordpress.org/support/topic/filter-out-categories-and-tags-from-post_class/)
 *  Thread Starter [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/filter-out-categories-and-tags-from-post_class/#post-1003034)
 * Cheers – I’m actually filtering out all dynamic classes now as they accounted
   for an increase of 50% in file sizes on my themes.
 *   Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/)
   
   In reply to: [2.8 is evil](https://wordpress.org/support/topic/28-is-evil/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/28-is-evil/page/5/#post-1104927)
 * [@pariahdesign](https://wordpress.org/support/users/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. [http://core.trac.wordpress.org/ticket/10226](http://core.trac.wordpress.org/ticket/10226)
 * I haven’t experienced this problem with beta 1 so the issue may be getting triggered
   by the environment.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Fatal error with pluggable.php](https://wordpress.org/support/topic/fatal-error-with-pluggablephp/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-with-pluggablephp/#post-1118634)
 * Try 2.8.1 Beta 2 to see if this makes a difference. There was a change to this
   after beta 1.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Mysterious”display: none;” inserted in <img> and AdSense ads](https://wordpress.org/support/topic/mysteriousdisplay-none-inserted-in-ltimggt-and-adsense-ads/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/mysteriousdisplay-none-inserted-in-ltimggt-and-adsense-ads/#post-1124094)
 * 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.
 *   Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/)
   
   In reply to: [2.8 is evil](https://wordpress.org/support/topic/28-is-evil/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 11 months ago](https://wordpress.org/support/topic/28-is-evil/page/3/#post-1104773)
 * 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” ([http://codex.wordpress.org/Upgrading_WordPress](http://codex.wordpress.org/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.** [http://core.trac.wordpress.org/ ](http://core.trac.wordpress.org/)
 * 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 😉
 *   Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/)
   
   In reply to: [Permission changed with upgrade](https://wordpress.org/support/topic/permission-changed-with-upgrade/)
 *  [Elpie](https://wordpress.org/support/users/elpie/)
 * (@elpie)
 * [16 years, 11 months ago](https://wordpress.org/support/topic/permission-changed-with-upgrade/#post-1109357)
 * It’s a bug & you were just lucky to have it 😉

Viewing 15 replies - 1 through 15 (of 52 total)

1 [2](https://wordpress.org/support/users/elpie/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/elpie/replies/page/3/?output_format=md) 
[4](https://wordpress.org/support/users/elpie/replies/page/4/?output_format=md) 
[→](https://wordpress.org/support/users/elpie/replies/page/2/?output_format=md)