Question
I defined a preference variable in a specific topic to override the value defined in the
WebPreferences topic for that web. Everything works as expected.
However, when using the
PublishWebPlugin, the variable in the topic is either not processed or processed in a different order since the value is equal to the one defined in the
WebPreferences.
Additional information: It works ok when editing/saving an individual topic. It fails when doing all topics in a web. I suspect that it is taking the preferences variables from the topic which called the Publishweb "all" command.
Environment
--
RichardBeaver - 26 Mar 2008
Answer
If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.
Yes, you analyzed it properly. Workaround for now: Use
TWikiForms instead of preferences settings to set page specific settings.
For example, all pages in the publish web of the
TWIKI.NET's website
have a form. This is the form content of blog entry
http://www.twiki.net/blog_2008-03-25.html
:
| WebForm |
| PageId |
blog |
| PageSection |
blog |
| PageTitle |
Scalability of TWiki |
| PageDescription |
TWIKI.NET blog voice: How to scale TWiki sites |
| Author |
Peter Thoeny |
| Category |
Best Practices |
Those form field values are used by the publish skin, for example to highlight the proper link in the top link bar.
--
PeterThoeny - 26 Mar 2008
Thank you for the quick response.
I have switched to
TWikiForms and the effect is still the same. My skin uses a preference variable to set the page title. A normal display (a TWiki page) works fine and an individual edit/save works also. However, I have another topic (call it TopicA) which generates the static pages for all topics in the web. This one fails the same way. The preference set in the individual topic is ignored. It is either taking the preference setting from
WebPreferences or TopicA, which really doesn't even have one set.
--
RichardBeaver - 27 Mar 2008
Your scenario is currently not supported. Change setting the page title from a preference variable to a form field. That will work.
--
PeterThoeny - 30 Mar 2008