Thanks for posting yours. It validates with fewer complaints. On Dec 10, 2:12 pm, The Editor <[email protected]> wrote: > Here's what I have in my code.skin.rss... > > <?xml version="1.0" encoding="utf-8"?> > <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom";> > <channel> > <atom:link href="$$script$$p" rel="self" type="application/rss+xml" /> > [[MAIN]] > </channel> > </rss> > > Evidently the backup file was never upgraded. I think the best > solution is to just delete the backup. The skin can be simply cut and > pasted from the solution page (it's current now) and it's easy enough > to add a description data value using the data function. That's one > less thing to try and keep in sync. I've just touched up the solution > page. Thanks! > > Cheers, > Dan > > > > On Thu, Dec 10, 2009 at 2:32 AM, Markus <[email protected]> wrote: > > Alright, I installed 3.3.2 and after lots of tinkering with RSS I got > > it working. But not as it seems to be expected... > > > I don't understand the version of code.skin.rss in rss.backup: > > > <title>$$title</title> > > <link>$$rss</link> > > <description>$$description</description> > > ==[(rssfeed {p})]== > > > If you use this, you must remove the rssfeed function call from the > > actual page, right? But how would get the parameters in there? I tried > > to make a rss* page containing only parameters but it didn't work. It > > just returned every single page I can think of. > > > So I changed code.skin.rss to the following which makes much more > > sense to me (I thought the changes were all about capitalized sections > > anyway): > > > <?xml version="1.0"?> > > <rss version="2.0"> > > <channel> > > [[MAIN]] > > </channel> > > </rss> > > > Using the (simpler?) version of code.skin.rss, the rss* pages can look > > as they have been looking ever since: > > > [(rssfeed *parameters*)] > > > In this case I also see no need for action.description or for setting > > custom titles as you are already setting all the parameters in rss*. > > > All the best, > > Markus > > > On Dec 9, 11:52 pm, The Editor <[email protected]> wrote: > >> Actually, it is available in 3.3.1. I've noticed a few problems on my > >> server though with some file names being created that have capital > >> letters. Not good. So there is obviously a bug in there. > > >> I'm fixing to release a new version shortly, with several other bugs > >> fixed. I may try to track this one down first. I'll see if I can't get > >> that out tonight... > > >> Cheers, > >> Dan > > >> On Wed, Dec 9, 2009 at 4:47 PM, Markus <[email protected]> > >> wrote: > >> > On Dec 9, 9:50 pm, The Editor <[email protected]> wrote: > >> >> On Fri, Dec 4, 2009 at 6:18 AM, Markus <[email protected]> > >> >> wrote: > > >> >> > Another issue found. I just logged in to BoltWire.com and I got this > >> >> > message: > > >> >> > Form submitted. You have been successfully logged in as $1. > > >> >> Yes, this is because you have a local site.messages page. The $ signs > >> >> are no longer encoded so it needs to be updated. The easiest way to do > >> >> this is to simply delete the local site.message page. The server one > >> >> will kick in, recently corrected, and the problem will disappear. If > >> >> you have custom messages, simply open the page (site.messages) and > >> >> resave it. It will automatically convert the $ to an unencoded form > >> >> and your problems should go away. > > >> > Thanks for getting back to my posts. > > >> > It wasn't on my site, it was BoltWire.com. But obviously you have > >> > fixed this. > > >> > I agree with everything else you wrote (update check, action.changes > >> > etc.). Good things to come. > > >> > The RSS plugin is working for you only because you are using an > >> > unreleased BoltWire version that supports CAPITALIZED sections, right? > > >> > Best wishes, > >> > Markus > > >> >> 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 > >> > athttp://groups.google.com/group/boltwire?hl=en. > > > -- > > > 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 > > athttp://groups.google.com/group/boltwire?hl=en.
-- 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.
