WordPress-instruktionen uppdaterad
[lang_en]A few persons have said that they are having problems validating their RSS feeds after following my instructions for integrating WordPress in RapidWeaver. Since I haven’t been able to get any further information about this and the fact that I haven’t been seeing this problem I haven’t been able to do anything about it. But yesterday I was able to identify the problem, thanks to a helpful user, and fix my instruction :)[/lang_en]
[lang_sv]Några personer har hört av sig och sagt att dom har haft problem att validera sina RSS-strömmar efter att ha följt min instruktion för att integrera WordPress in RapidWeaver. Eftersom jag inte har kunnat få någon mer information om det och själv inte haft det problemet så har jag inte kunnat göra någonting åt det. Men igår lyckades jag identifiera problemet, tack vare en hjälpsam användare, och rätta till min instruktion :)[/lang_sv]
[lang_en]The RSS-feed problem only affects those who are running the latest version of WordPress, any version in the 2.2 series. They made a small change in their code that leaves the surrounding app (in this case my code) in charge of terminating the script at the correct point. Since this wasn’t necessary before I didn’t add it to my instruction.
If you are having problems with your RSS-feed and is seeing the page content added at the end of the feed you should redo your integration accoring to my updated instruction.
I also took the time to make some other minor adjustments:
- Fixed the RSS-link because it wasn’t generated properly.
- Removed some code that is not needed.
[/lang_en]
[lang_sv]Problemet med RSS-strömmarna berör bara dom som använder den senaste versionen av WordPress, någon av 2.2 versionerna. Dom har nämligen gjort en liten ändring i sin kod som överlåter till den omgivande applicationen (i detta fall min kod) att avsluta skriptet vid rätt tillfälle. Eftersom det inte var nödvändigt tidigare så gjorde jag inte det i min instruktion.
Om du har problem med din RSS-ström och ser HTML-sidan i slutet av din ström så bör du göra om din integration efter min uppdaterade instruktion.
Jag passade också på att göra några fler små ändringar:
- Fixade RSS-länken eftersom den inte genererades riktigt rätt.
- Tog bort lite kod som inte behövs.
[/lang_sv]
Great! I wanted to ask for help with the RSS-problem, but then I went on holiday and now I’m back it’s fixed. Thanks!
The base href – why didn’t anybody think of that earlier?! 🙂 – works fine with the permalinks, but it needs a slash in the end (like you have in the code for this blog!) to show the correct link for the blog in the RW menu and breadcrumb trail.
Yes, the base href is a neat trick 🙂
It was not possible to add that in RW pre version 3.6 so that is mainly why I didn’t list it before. Since you anyway had to edit the exported page you could just as easily fix the links. I did so by running a small script everytime I had republished my blogpage.
I have added the missing slash in the tutorial now, thanks for pointing it out 🙂
I just finished debugging a minor issue caused by a mistake on my part but it might be worth telling others about this little gotcha.
In Step 2 of the tutorial: Add code to the “Page Prefix” it is VITAL that the
Fill in the rest and i’ll see about highlighting what you stumbled upon in my tutorial 🙂
Sorry!!! Don’t know how that happened!
As I was saying…
In Step 2 of the tutorial: Add code to the ”Page Prefix” it is VITAL that the part that starts with the files.
Hope that helps.
OK now this is annoying me…..
WordPress doesn’t check for the php open and close symbols in comments? Isn’t that a huge security issue?
The problem in step two is about leaving spaces or line breaks infront of the symbols to start the php when copying to Rapidweaver. IF this happens, it breaks the RSS export (and who knows what else) while most of the site appears to work.
Ahh, yes you should not put anything before the first php-tag. I will add a note about that in step 2. Thanks for the feedback.
The issue with the php tags in comments is just that WordPress strips certain things from the comment text so that you cannot inject bad stuff 🙂 Most of the times it’s good but there are cases where you would like it to behave differently. There is probably some plugin available that can fix that but I haven’t checked.