You might want to wait till the morning Linly as I've noticed some other problems, that kept the blog from working as it should.
I'll post my findings soon. I think I about have it working again. Was a bit tricky... Cheers, Dan 2009/3/27 Linly <[email protected]>: > > OK, I'll try Martin's suggest first.If failed, then go to the php code > as Dan said. > Wish me luck. :) But I've to go to bed now. Good night guys. > > Cheers, linly > > > On 3月28日, 上午12時26分, The Editor <[email protected]> wrote: >> On Fri, Mar 27, 2009 at 11:15 AM, Linly <[email protected]> wrote: >> >> > Partly worked. I can make the rss page use the rss skin. But it can >> > not pass the validation fromhttp://validator.w3.org/feed/. >> >> > line 5, column 38: XML parsing error: <unknown>:5:38: not well- >> > formed (invalid token) [help] >> >> > <link>http://txtray.net/?p=rss&action=rss</link> >> >> ^ >> >> The problem here is that the & should be escaped to & To fix >> this, open the rss.php plugin and try changing line 12 to this: >> >> $BOLTvar['$rss'] = "$scriptURL$pageLink&action=rss"; >> >> > In addition, interoperability with the widest range of feed readers >> > could be improved by implementing the following recommendation. >> >> > * >> >> > Feeds should not be served with the "text/html" media type >> > [help] >> >> This seems to mean the server is supplying the wrong content type in >> the server headers that come with the html page. It will take a bit >> more to fix. But you can try this: >> >> First, change the last line at the end of the BOLTmakepage function in >> engine.php, around line 1440 to >> >> if (is_array($BOLTserverHeaders)) { >> foreach($BOLTserverHeaders as $h) header($h); >> } >> return $out; >> >> Second, add $BOLTserverHeaders, to one of the two lines containing all >> the global declarations at the top of that function. >> >> Finally, change the rss.php function to change the first line of >> BOLTFrssfeed to: >> >> global $scriptURL, $pageLink, $BOLTserverHeaders; >> $BOLTserverHeaders[] = "Content-Type: application/xml; >> charset=utf-8"; >> >> Basically this tells BOLTwire to set the content-type header to xml >> rather than text/html. Not 100% sure the charset line is needed, but >> guess it won't hurt. >> >> I'll add the lines to the core and give it a test run when I get some >> time, but feel free to tinker with these changes yourself and see what >> happens. >> >> Cheers, >> Dan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
