Archive
Switching from Blinksale to Zoho Invoice
I Think Google Chrome Killed My WordPress Blog
Still Trying to Troubleshoot FeedWordPress Issues
AT&T Comes Out with Their U-Verse iPhone App
Why I Really Like WordPress 2.8
Blog, From the Network, WordPress, WordPress 2.8, WordPress Plug-ins, WordPress Plugins, WordPress Themes
iPhone 3GS – I Got MY New Baby
iPhone Firmware 3.0 Installed and I’m Liking It
- iPhone 3GS – I Got MY New Baby
- New Blogging Tool – Evernote on My iPhone
- Fail: iPhone 3.0 Activation Servers Down :-(
App Store, Blog, Camera, Copy, Firmware 3.0, From the Network, Paste, Spotlight, Voice Memo, Voice Notes, iPhone
Fail: iPhone 3.0 Activation Servers Down :-(
I was super excited to see that the iPhone 3.0 software was out so I ran home to update my phone. The download happened nice and fast which was cool but when I actually tried to install the update this is what I got:
Bum deal.
I guess this is the message that a lot of people were seeing with the 2.0 update except for the fact that when it happened back then that it bricked the phone. I guess I am fortunate enough that 2.0 did not brick mine.
I want my iPhone 3.0!
Related posts:
FeedWordPress – One Step Closer to Fixing My Problem
So I posted the issue that I am having about the automatic update not pulling in the meta data for each post over on the official FeedWordPress site. I haven’t received a reply yet but in all fairness it is a free plugin so I would not necessarily expect to get an answer.
With that I setup another site really quick with a fresh install of WordPress 2.8 and the 2009.0613 version of FeedWordPress. I then setup my Twitter RSS feed to populate it and low and behold the automatic update pulled in all of the necessary meta data and linked back to the original source. This means that there must be something screwy with my install of the plugin but I am not quite sure what it is.
My options at this point are:
- Uninstall the plugin and hopefully it will delete itself completely from my WordPress db and then reinstall it.
- Kill the whole WordPress DB , delete the plugin, reinstall WordPress and the Plugin, re-import all my posts, and reconfigure FeedWordPress.
I am really hoping that option 1 will work. I guess I will find out in the next day or so. I will update when I find out what it took to fix it.
Related posts:
Aggregation, Blog, FeedWordPress, From the Network, Syndication, WordPress Plug-ins
FeedWordPress Problems – It’s Got to Be Me, Not You
Aggregation, Blog, FeedWordPress, From the Network, Syndication, WordPress Plug-ins
WordPress 2.8 Release – Looking Good
New Website Under Construction
Fixing FeedWordPress PermaLinks to the Original Website
With the recent upgrade of the syndication plug-in FeedWordPress that I use on my network.idano.net syndication site the links on the articles were no longer linking back to the original website. A few people had noted this issue on the comments thread but no one provided any solutions. Because the network.idano.net website was linking back to itself I was not getting the SEO and cross linking advantage that was intended. In fact there was a possibility that I could be penalized because of duplicate content.
To fix the issue I deactivated and deleted the plug-in on my network.idano.net website and then re-uploaded the plug-in. This included the MagpieRSS-upgrade rss.php and rss-functions.php files that needed to be uploaded to the wp-includes folder as well. Once that was done I cleared the cache in my browser and re-activated the plug-in.
From there I did a test post and manually had the FeedWordPress plugin check for a new post from that site. The plugin found the post and when I checked the Permalink it linked back to the original website like it was supposed to. Unfortunately it did not update the previous posts.
To correct the rest of the posts I went into my syndicated site and deleted the posts that had the incorrect linking. From there I went in and had the plug-in update from all of the syndicated sites. It found all of the posts that I had deleted, added them, and properly linked them back to the original sites.
Problem fixed. Case closed
.
