Extension talk:Semantic Page Series

Previous page history was archived for backup purposes at Extension talk:Semantic Page Series/LQT Archive 1 on 2015-07-10.

Where can i found a functionally example to how works this extension?

i can not make to work, when i clic on the next link, it does not work

{{#serieslink:
form=EventSeries
|link text=Create event series
|link type=button

|iterator=date
|target form=Event
|target field=Event[Date]

|start=Event[Start]
|end=Event[End]
|unit=Event[Unit]
|period=Event[Period]
}}

before to click on the above link, sends me a page with this url:

Especial:SeriesEdit/EventSeries?iterator=date&target_form=Event&target_field=Event%5BDate%5D&start=Event%5BStart%5D&end=Event%5BEnd%5D&unit=Event%5BUnit%5D&period=Event%5BPeriod%5D&origin=9782

an this tag:

<seriesedit>

First of all, make sure that you have Extension:SemanticForms and Extension:SemanticMediawiki installed and that you created the necessary forms and the template.

As you can see from the release date, this extension is quite old and it may well be, that it does not work with newer versions of Mediawiki or Semantic Mediawiki. The link looks generally alright. The only thing is, that I don't know where the origin parameter comes from.

What versions of Mediawiki, SemanticMediawiki, SemanticForms and Semantic Page Series are you using?

I have it working on MW 1.19.18 and SMW 1.9.

I notice you are specifying two different forms EventSeries and Event. Do you both a SF form and a template? Do you have Date, Start, End, Unit and Period set up as SMW properties?

I have this on my site:

{{#serieslink:form=Activity Form |link text=Add a Multiple event |link type=button |iterator=date |target form=Activity Form |target field=Activity Template[Start Date] |start=Activity Template[Start Date] |end=Activity Template[End Date] |unit=Activity Template[Unit] |period=Activity Template[Period] |keep parameters }}

and it works.

Hi Mitchelln:

may you tell me, what have into your template "Activity Template"? also, what type has the "unit" and "period" properties?

I spcifying two forms because sow that in the usage documentation... but maybe i misunderstood something

Hi F.trott: i´m using MW 1.22.3, SMW Versión 1.9.1, SF Versión 2.7, SPS Versión 0.1 alpha, these extensions works ok! and yes i created the forms and template exactly than the example in to the usage section of the extension page. Maybe i missing something... i created three elements:

1. Form:Event
2. Form:EventSeries
3. Template:Event

if you want, i can get you temporary user... with a e-mail

Great idea with this extension. I have decided to test it out. I copied and pasted the example templates & forms provided on the Extension page. However, when I hit the link to create the page series, Special:SeriesEdit only shows <seriesedit> in the page title and nothing else. Is there version incompatibility with either MW or SMW & SMW-related extensions?

I noticed this with a bare minimum extension base (or at least as bare minimum as I can think):

• MediaWiki 1.19.0
• PHP 5.3.10
• MySQL 5.5.21
• Semantic Forms 2.4.2
• Semantic Forms Inputs 0.5
• Semantic MediaWiki 1.7.1
• Semantic Page Series 0.1a
• Validator 0.4.14

PS, I tested against SPS release version and SPS dev version with same results. SMW extensions were from Semantic Bundle 20120430r189.

Sorry, no clue. Could you turn PHP errors on to see if something comes up? See Debugging#PHP_errors

Oh, and this wiki is not public by any chance, is it?

Cheers,

unfortunately, no. i am running this on a local dev vm. i did have debugging on, and did not see any outputs.

should SPS be compatible with those SMW extension versions?

From what I was able to deduce, EventSeries form requires the info tag (lines 123-128 of includes/SPSSpecialSeriesEdit.php seems to be looking for this or else it complains). I don't believe the EventSeries example on the extension page has that.

Once I changed that, I was able to see the EventSeries form as expected from the Special:SeriesEdit page.

However, the series of pages will not be created. It returns the fatal error:

Call to a member function getContext() on a non-object in $IP/includes/api/ApiBase.php on line 77

Thanks.

Sorry, this took a while. I fixed the first problem, the info tag is not required anymore. I do not get the second error. If you are still interested, could you try the latest dev version?

Cheers.

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!

This should now finally be fixed in the SPS development version.

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.

Ok, just checked the fix in. There was also a bug in SF that is fixed now. If you update both extensions to the latest dev version, it should work.

Cheers,

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.

Let me reword this. Is there any difference in the construction of queries of dates associated with a page via #set_recurring_event vs dates associated with a page via #serieslink ?

Probably not,

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?

As it says on the extension's page, there are two form definitions involved, one for the pages of the series and one for the series as a whole. The series as a whole does not require the page name parameter. The form definition for the pages however does.

Other than date and numeric, what other iterators are in the hopper?

None right now. Though I am open for suggestions. Or you could implement one yourself, it's straightforward.

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.