Extension talk:Semantic Page Series
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Only works if SFI datepicker is used | 0 | 14:09, 13 April 2012 |
| Bug reports | 2 | 20:00, 20 February 2012 |
| Query simplification? | 5 | 21:10, 6 February 2012 |
| Page histories | 3 | 20:48, 6 February 2012 |
| Series page titles | 3 | 20:43, 6 February 2012 |
| Iterators | 1 | 20:24, 6 February 2012 |
| Serieslink | 1 | 20:23, 6 February 2012 |
Hi.
I'm running this on an english install of MW 1.17.3 with SMW 1.8alpha.
If I use the standard SMW date input:
{{{field|Start Date|input type=Date|mandatory}}}
Then the page create always fails with the error: "The start date is missing."
If I use the SFI date picker:
{{{field|Start Date|mandatory|input type=datepicker
|disable input field
|show reset button
|show week numbers
|week start=1
|highlight days of week=0
|date format=DD dd MM yy}}}
Then it works and the pages get created. I suspect this is down to some low level date format issue.
I wanted to switch to the simple date entry because there is a nasty problem with SFI. When you edit the page, the date is zapped back to the current date. Caught between a rock and a hard place!
Hello - I have filed a bug report at http://code.google.com/p/semanticpageseries/issues/detail?id=1&thanks=1&ts=1329252765 because MW Bugzilla doesn't have an entry for SPS - is this the right place (I'd prefer MW Bugzilla though).
Thanks for the report, I will fix the bug next week. For the time being you can either revert to SF 2.4 (release version) or replace all calls to SFFormUtils::hiddenFieldHTML by Html::hidden. Calling unhandledFieldsHTML can not work, the functionality is different from hiddenFieldHtml.
I also added contact information to the Extension Page.
I hear that this extension simplifies/improves SMW queries... could this be explained here? Thanks
No, it will not directly improve or simplify SMW queries, sorry. All this does is to create a series of pages in one go.
So you're saying that SPS honors the same queries forulated for SMW pages with #set_recurring_event and for SIO pages with #set_internal_recurring_event? If not, what are the changes? Thx
SPS honors no queries at all. It depends on your template what properties are set for the created pages and hence in what queries they show up.
What is the effect on page histories of edits to the 'master' page, each of the series' pages, and series' pages that are overwritten? Thanks
- master page: if you mean the pages, where the link is, no effect
- each of the series pages: they are created like any other page, the summary given when filling in the form will appear as the summary for every page
- pages that are overwritten: they will appear as any other edit in the history, so if you accidentally overwrote something, you can revert it as any other edit
Does each series page have a link back to its "master" page, like SIO does (and i suppose also like Subobjects have) - that's what I meant by master page. I guess one can delete such master page, leaving series' pages intact?
The concept of a master page in the sense of SIO does not apply here. Every event of the series gets its own page, so there is no need for a master page. So there is no need to delete the master page, because it will not even get created.
But yes, if you already have a 'master' page for the whole series, e.g. because you used SIO before, you can delete it afterwards. However, as I pointed out, the #serieslink parser function will not automatically create all the new pages if you just replace #set_recurring_event by #serieslink. You will have to insert all the data again.
How are the titles for the series' pages formulated? Thx
See the Extension:Semantic_Forms/Linking_to_forms#The_one-step_process of Semantic Forms. Basically, you can specify how it is created by giving a rule in the form definition's info tag.
The extension's page states: You can also remove the page name parameter of the info tag or - as there are no parameters left in this case - the whole info tag.
Yet I hear you talking about something else? And how would one incorporate the date into the title?
Other than date and numeric, what other iterators are in the hopper?
Where is this parser function used, in the same place (the template for the page referenced by the form) as #set_internal_recurring_event?
You could put it there, although it has a very different function than #set_internal_recurring_event. Where #set_internal_recurring_event specifies the recurring events, the #serieslink will take you to a form, where you can put in some data. The #serieslink is more similar in function to #formlink, so wherever you would put a #formlink, you could put a #serieslink.
