As I have just figured out after some of the upgrades the external link in the title hack was, indeed, broken. In fact, I am somewhat puzzled, as it worked on some of my installations and didn’t work on others.
It turns out that the method of obtaining the permalink for the post is returning the canonical URI no matter what permalink system has been set up (I use custom on this blog). For example, even if you have something SEO-friendly, the code
$perm = $post_id->guid;
would still return http://www.istudioweb.com/?p=427 as a link to this post. The right way of doing it now (before WP 2.7 arrives) is change the above line to:
$perm = get_permalink($post_id);
That’s it. Should work.
P.S. Updated the downloadable txt file. Click here to view.
At least once a week I get an e-mail about the WP theme hack I posted in January. Most of the people ask how to make the hack work in WP 2.5 and 2.6.
Here’s the simple answer – if you didn’t touch your theme (I didn’t) and if you have just upgraded the WordPress installation itself – then the hack should still work. The original post with instructions is here.
The proof is this post – look at the title and take note that link in the title leads to the main blog page, not to the post itself.
If something actually did went wrong, check the following:
- Your theme’s functions.php file or whatever the name of the file with theme’s functions is. It should still contain the code from the original post.
- Your theme’s index.php file or whatever the main index template file name is. It should have the original hack as outlined in the original post.
- Custom field – the new URL must be in the value field, whereas the custom field name should be url1 or whatever you made it to be.
Let me know if the damn thing is acting up again.
Looks like there is another vulnerability discovered in WordPress, that’s why I have to upload all 3.1MB of files again to all the accounts I have WP installed. After backing up the account and downloading backup.
Maybe I am being too quirky, but I would just post files that need to be updated – just like other PHP projects do – Joomla, Invision Power Board and so on.
On the other hand – maybe (just maybe) it’s time to move to SVN way of managing the multiple installations…