Extension talk:Page Schemas/Archive 2013 to 2015

[Download link does not work]

Hi there,

I would love to download the extension Page Schemas, but have unfortunately not been able to. I went onto the Extesion:PageShemas, under “Code and download” area where it says: “You can download the Page Schemas code, in .tgz format, here.”

The download link “here” was as follows: https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/PageSchemas.git;a=snapshot;h=4dd93fe74c8c39b6438b92f4927cfa71ca3b901a;sf=tgz

Once I am clicking on the above link I am getting the following error message: “Unable to download gitweb from gerrit.wikimedia.org. Unable to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.”

Would anybody please be able to help?

Many thanks

Pan

The link works for me. Could you try again? Gerrit may have been unavailable for a short time. Instead of clicking, you could also try "right-click / save as". Cavila ^{MW 1.19.2, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.1} 11:21, 15 February 2013 (UTC)

Hello Cavilla, I've just tried again and got the same error message.

However, completely by chance I found the following link http://www.mediawiki.org/wiki/Special:ExtensionDistributor/Autoincrement and by selecting the extension I wanted it did allow me to download the PageSchemas files.

Thanks for your reply. Pan

Issue with side infobox

Hi, I am having an odd error. The infobox came out as expected when I was using the other way to use a form (manually create property, create template, create form). When I deleted the template/form and tried to re-make the exact same thing in page schemas, i get a jumpled mess peppered with red links that say "Template:!" where the infobox should be.

Thanks so much for any help,

Matt

You should create the page at "Template:!", with just a single character as the contents: "|". I think the latest version of Semantic Forms takes care of creating that page automatically. Yaron Koren (talk) 19:23, 30 July 2013 (UTC)

Perfect, thank you. I did download the semantic bundle maybe 2 days ago which had semantic forms. Wondering if that doesnt have the latest version and perhaps I should go update it....Matt

Two minor questions on page schemas (image upload, edit function)

Question 1: I am having trouble creating a form input field in a side infobox template of form created in page schemas - what I want is to have the user hit an upload button, they upload an image from their desktop, and then the picture shows (not the filename eg xyz.png). I did read in "Working with Mediawiki" by Yaron Koren about uploading files - where he says "This is done simply by adding the parameter "uploadable" to that field's declaration in the form definition (although this was for the shows filename xyz.png example) and I was unsure where exactly I put "uploadable" - any guidance here would be much appreciated.

Question 2: In Page Schemas if you select the output to be "sections" - when the user is reading the page each section has an "edit" hyperlink above it. unfortunately this takes you to editing the source code, not the form. Is it possible to either change this to point to the form, or remove it entirely? Thanks for any advice - I believe these answers will help the average person use page schemas more! --Matt

Hi - (1) you should add it in the form input's "parameter names and their values..." field. (2) you should add __NOEDITSECTION__ to the template. That's really a bug in the software - that tag should get added to the template directly. Yaron Koren (talk) 16:21, 31 July 2013 (UTC)

Yaron, in response to (1), within the edit schema function, I added __NOEDITSECTION__ to the "additional XML field" of each field in the template that uses sections. I also tried to manually add it to the code by hitting edit on the category page rather than edit schema, in many different places.....the latest one I pasted below just to see if you can let me know if I am doing something wrong:

</Template>

 <Template name="Golf Course Introduction" format="sections">

  <Field name="Course Overview">

NOEDITSECTION (I took out the __ __ on this posting)

     <Label>Course Overview</Label>

All my tries yielded nothing. I can't help but wonder if perhaps I have a setting either wrong, or not in, localsettings.php. especially since it looks like the __NOEDITSECTION__ worked on this page....

As for item (2) about uploading docs, In the "Enter parameter names and their values as key=value pairs, separated by commas (if a value contains a comma, replace it with "\,"). For example: size=20, mandatory" field of "Form Input" in the Edit Schema section, I added "uploadable" (without " ") - when I refresh and go to my page, oddly it displays the following in my field on the Read tab of the page using the schema: "File:Mail-envelope.png" - I did not type or put that in. The code from the edit tab of the Category page for this, as created by edit schema, looks like this (BTW, i tried not to but maybe i killed the edit tabs in this page....can delete after.

    </Field>
    <Field name="Score Card">
      <Label>Score Card</Label>
      <semanticmediawiki_Property name="Has Score Card">
        <Type>Text</Type>
      </semanticmediawiki_Property>
      <semanticforms_FormInput>
        <InputType>text</InputType>
        <Parameter name="uploadable"/>
      </semanticforms_FormInput>
    </Field>

Thanks again for the time you have spent on this subject, and all others, Matt

For (2) (which you called (1)), I don't think there's way to add it via Page Schemas at all - which is unfortunate. For (1) - that's very strange; I can't replicate that strange behavior. What version of MediaWiki are you using? Yaron Koren (talk) 13:48, 1 August 2013 (UTC)

Version MediaWiki 1.21.1

PHP 5.3.24 (cgi-fcgi)

MySQL 5.0.96-log

Page Schemas (Version 0.3.1)

http://coursecaddy.org/index.php?title=Special:Version

Just to summarize since I screwed up the numbering (2 threads next time) - no way to ad NOEDITPAGES on a massive scale through page schemas, you have to do it page by page manually. for "uploadable," the way I have it should work, but something odd is going on - I re-did it this morning and instead of insterting envelope.png, its just a blank box I can type in, you can see that here: http://coursecaddy.org/index.php?title=Rustic_Canyon - Matt

It looks like "uploadable=", instead of "uploadable", is being added to the form, which causes the problem. This may have been fixed in the most recent SF version; I'm not sure. Yaron Koren (talk) 15:38, 1 August 2013 (UTC)

Thanks! That was an easy fix.....and easy to implement on a mass scale but simply upating the form: after generating pages. Folow up question, once you upload a file through semantic forms, it loads the file into the file namespace and images directory, which is great. How would you (if its possible) have it automatically display the image on the page in which you uploaded, after you upload it through semantic forms? Again, trying to make this user friendly so they dont have to then type the [{FILE:...) to display. thx as always, matt

The string "File:" needs to be added to the template, right before the variable that holds the file name, like "File:{{{filename|}}}". Again, that's a bug in Semantic Forms - it might have been fixed in the most recent version, but I'm less sure about this one. Yaron Koren (talk) 14:51, 2 August 2013 (UTC)

Worked perfectly, thanks. BTW I did update page schemas and semantic forms, both were a rev behind. The uploadable bug is still there, and this one. - Matt

Yaron, I'm having a similar problem and my code looks exactly the same as generated from Schemas. I can edit out the "uploadable=" problem, but the file still does not show. Where are you specifying what the file name is? The field is formatted as text. I see no variable that holds the filename because none is specified. Do I need to set that as a parameter? - David

I don't understand the question - is this a Semantic Forms question? Are you asking about the "default filename" parameter? Yaron Koren (talk) 22:09, 23 January 2015 (UTC)

I figured it out, thanks, Yaron. David

Output Format:Sections

I wonder if its a bug or I am doing something wrong. In using the Output Format:Sections functionality of page schemas, an odd thing happens with the template output. A " | " is added to the beginning of each section in the actual page that executes the templates through forms. I tinkered around with removing | from various parts of the template, with no luck. Any idea? example of output below:

Course Overview

| Rustic Canyon is a tribute to the....

No idea. Can you link to the template? Yaron Koren (talk) 12:49, 5 August 2013 (UTC)

Sure, check out how the page looks here (see the " | " at the beginning of each section?) http://coursecaddy.org/index.php?title=Rustic_Canyon. The template is here: http://coursecaddy.org/index.php?title=Template:Course_Body & http://coursecaddy.org/index.php?title=Template:Yardage_Book.

I am also having some trouble with the field descriptions & display labels in the Yardage Book section of the form itself, and I don't know if perhaps it's related to the above. Once we get root cause on the above i'll decide if i should start another thread....Thanks, Matt

Those extra pipes are coming from the "Course Body" template. Yaron Koren (talk) 15:58, 6 August 2013 (UTC)

I saw that too. When i change the output format in Page schemas to plain text and remove them from the template manually (i'm still wondering why Page Schemas adds them?) it looks great. Perhaps I will just revert back to plain text. When I try to remove them when the page schemas output is "sections" - it goes haywire.

Sorry, I didn't understand. Yaron Koren (talk) 11:35, 7 August 2013 (UTC)

Create Schema page - Does not initialize

After successfully installing this plugin, I get the expected "Create Schema" on my category pages; however, these pages fail to initialize, and I am not able to get back any debug info. Any ideas? Oh, and this is not skin related. ~z929669 Talk 20:29, 29 September 2013 (UTC)

Do you mean that you're seeing blank pages? And if so, could this help to diagnose the issue? Yaron Koren (talk) 17:56, 30 September 2013 (UTC)

Here is what PHP is reporting:

           Fatal error: Call to a member function getObject() on a non-object in 
           /home/stepproj/sites/wiki/docroot/extensions/SemanticForms/includes/SF_PageSchemas.php on line 270

... and the code snippet (270 is last line):

	public static function getSchemaEditingHTML( $pageSchemaObj ) {
		$form_array = array();
		$hasExistingValues = false;
		if ( !is_null( $pageSchemaObj ) ) {
			$form_array = $pageSchemaObj->getObject( 'semanticforms_Form' );
			if ( !is_null( $form_array ) ) {
				$hasExistingValues = true;
			}
		}

		// Get all the values from the page schema.
		$formName = PageSchemas::getValueFromObject( $form_array, 'name' );
		$pageNameFormula = PageSchemas::getValueFromObject( $form_array, 'PageNameFormula' );
		$createTitle = PageSchemas::getValueFromObject( $form_array, 'CreateTitle' );
		$editTitle = PageSchemas::getValueFromObject( $form_array, 'EditTitle' );

		//Inputs
		$standardInputs = $pageSchemaObj->getObject( 'standardInputs' );

~z929669 Talk 05:27, 1 October 2013 (UTC)

What versions of Semantic Forms and Page Schemas are you using? Yaron Koren (talk) 12:12, 1 October 2013 (UTC)

I am using 2.5.3 and 0.4-alpha, respectively. ~z929669 Talk 14:58, 1 October 2013 (UTC)

Ah, okay. It looks like this issue has already been fixed in the version of SF on Git - I guess it was fixed recently. You can either update your code via Git, if you have that, or just wait until the next version of SF is released, which I think will be this week or next. Yaron Koren (talk) 19:54, 1 October 2013 (UTC)

Wonderful, thanks! ~z929669 Talk 21:46, 1 October 2013 (UTC)

I have same problem - Strict standards: Non-static method SMWPageSchemas::createPropertyText() should not be called statically in ....\extensions\SemanticMediaWiki\includes\SMW_PageSchemas.php on line 294. MediaWiki 1.23.7, PHP 5.5.12 (apache2handler), MySQL 5.6.17, Semantic Forms 3.2, Semantic MediaWiki 2.1.1 Chvlad74 (talk)

That's a totally different problem. That issue is actually in the Semantic MediaWiki extension - I just submitted a patch to fix the bug. Thanks for letting me know about it. You can just ignore that warning or now, though. Yaron Koren (talk) 14:26, 19 March 2015 (UTC)

May be it related, but I can't generate a form with several templates. Generates only first template in the form, created by Page Schemas Chvlad74 (talk)

Try calling runJobs.php. Yaron Koren (talk) 21:06, 19 March 2015 (UTC)

Yes, it works. Thanks. Where I can find the full user documentation for Page Schemas? Chvlad74 (talk)

It's all on the main page. I see now that the page barely mentions jobs; I just added in a note about that. Yaron Koren (talk) 12:14, 20 March 2015 (UTC)

Thanks. When do you plan to publish an update with bug fix on line 294? Chvlad74 (talk)

You'll have to ask the Semantic MediaWiki developers that - it's a bug in SMW. Yaron Koren (talk) 13:56, 20 March 2015 (UTC)

Do you know this bug is in SMW buglist? Chvlad74 (talk) 14:30, 20 March 2015 (UTC)

I don't know. On the other hand, it was fixed yesterday. Yaron Koren (talk) 14:50, 20 March 2015 (UTC)

But we have to wait new release of SMW (Sorry for the stupid questions)? Chvlad74 (talk) 15:06, 20 March 2015 (UTC)

It depends on how you're getting the code. If you're getting the code via Git, you can just re-fetch the code. Otherwise, you can also just apply this change directly. Yaron Koren (talk) 15:21, 20 March 2015 (UTC)

Thanks! Chvlad74 (talk) 15:26, 20 March 2015 (UTC)

Form to PageSchema conversion

see http://stackoverflow.com/questions/19186528/page-schema-addition-for-converting-forms-to-schema

That's great! I just added that URL to the list of PS importing tools. Yaron Koren (talk) 12:32, 7 October 2013 (UTC)

Thanks Please add your PS importing tools link as an answer to the stackoverflow question. This cross-linking might be helpful. Also you are kindly invited for personal communication via my webpage (see my user's profile on Stackoverflow). Unfortunately I can not come to Berlin next week since the event is sold out.

Unfortunately, I don't have a Stack Overflow account. Yeah, it's crazy how much interest there was in this SMWCon - hopefully we'll get to meet at a future event. Yaron Koren (talk) 02:54, 17 October 2013 (UTC)

Link is broken, target is a page not found on stack overflow

Indeed, I will remove the link from the docu. I wonder where it ended up. --[[kgh]] (talk) 14:58, 23 November 2016 (UTC)

Generate pages doesn't work

MW 1.22.2
PHP 5.3.28
SMW 1.9.1
Page Schemas 0.4.1 7d4e35e 7 Feb 2014

I've designed a schema, but the Generate Pages does nothing.

• I've read everything available on the extension and talk pages.
• I've watched the tutorial video
• I've executed runJobs.php manually and via cron.
• I've queried the 'job' table (empty).
• I've played with the $wgPhpCli setting.

The apache error log contains the following when I edit the schema:

[Tue Feb 11 03:34:46 2014] [error] [client 127.0.0.1] PHP Notice:  Undefined variable: fieldDelimiterSet in
/usr/local/devmediawiki-1.22.2/w/extensions/PageSchemas/specials/PS_EditSchema.php on line 260, referer: <masked>

I'm out of ideas. Thanks.

Hi - I'm familiar with that error message (it'll be fixed), but I'm pretty sure that's not the cause. How many pages are you trying to generate? And what happens if (using the checkboxes) you try to only generate one or two of them at a time? Yaron Koren (talk) 13:21, 11 February 2014 (UTC)

Hello, I am having the exact same issue, I can create the schema with no issues, but page generation will not work. Also tried generating pages one at a time and still a no go...

Did you try running runJobs.php? Yaron Koren (talk) 01:10, 19 March 2014 (UTC)

That worked, I'm assuming then that it is a permissions issue? Also, i have to do a null edit with forms to get the updated changes to work, is this normal?

Hi - no, it's not a permissions issue; if you're using MW 1.22 (which I'm guessing you are), it's a bug in that version of MediaWiki - see the "Common problems" section. I didn't understand the second question, though. Yaron Koren (talk) 02:43, 20 March 2014 (UTC)

Uploadable issue, partial handling of list of value in a field issue, and some suggestions

Hi there,

After using MW 1.22.5 + SMW 1.9.2 + SF 2.7 + PageSchema 0.4.2 for a week, I have noticed some issues, and some enhancements to perform to get a fully usable extension without need to manually custom templates or forms generated.

• Issue 1 : Whereas I work with all most recent extension versions, the issue of “uploadable=” in the form generated through PageSchema is still present. So the equal sign still needs to be manually removed, and the bad thing is that you will to need to do it each time you want make evolution on the form.

• Enhancement 1 : To go further with uploadable feature, when a field is set to be uploadable, would it be possible to automatically add to the generated template the file name property. For example, if I want a field to import a picture, “Picture” will be the label of the field. By using current feature and adding file namespace to my field, I can get in my template :

! Display label
| File:{{{Picture|}}}

But in order to embed the picture in the generated page I would need to have this :

! Display label
| [[File::File:{{{Picture|}}}]]

• Issue 2 : I got another trouble by using multiple values for the same field. So I created through Page Schema a template using a field that can hold a list of values. On the model I ticked “Can hold a list of values” option. On the property, I wrote the allowed values. At generating form, all is ok, list option is appended to the field in the form. At generating model, the parser function #arraymap is not used for the field. That means that even if I can choose on the form multiple values for the field, field in the page generated through the form doesn’t support multiple values in it. Again, I have then to manually modify my template by using #arraymap. So I think when, on a particular field for a template, we choose “Can hold a list of values”, the template generated should use #arraymap. Moreover this is the behavior of the special page CreateTemplate.

• Enhancement 2 : Finally, I have a suggestion for next version of page schema: can you add an optional category field for the template , as it is done on the special page CreateTemplate : “Category defined by template (optional) “?

Issues #1 and #2 both sound like bugs - I'll have to look into those. (I'm especially surprised by issue #2.) I'm also surprised by enhancement #1 - if you add a property for that field, it should show up in the template - not in the syntax you have it, but with a #set call, which should have the same effect. Does the #set call not show up for you? And for enhancement #2, I felt that that was not necessary because the category where the page schema is defined is already being added to the template. Do you need to add a 2nd category? Yaron Koren (talk) 13:44, 28 April 2014 (UTC)

generate pages doesn't work

M.W. 1.22.5 smw 1.8.0.5

Schemas looks like a great extension.

I get this message when i try to generate: Fatal error: Call to a member function getNsText() on a non-object in /home/yidtrave/public_html/mw/extensions/PageSchemas/PageSchemas.classes.php on line 66

That's strange... what version of Page Schemas are you using? Yaron Koren (talk) 21:07, 28 April 2014 (UTC)

Version 0.4.1

Alright. My guess is that it's something specific to this schema, in some way. Is this a public wiki? If not, could you put the schema XML somewhere, like pastebin, or email it to me? Yaron Koren (talk) 11:54, 29 April 2014 (UTC)

Thanks for emailing it to me. I couldn't reproduce the problem; but I just realized that you're using an older version of Page Schemas - 0.4.1 instead of 0.4.2. Could you try upgrading, and see if that fixes the problem? Yaron Koren (talk) 20:48, 30 April 2014 (UTC)

This was resolved - the issue was something I should have thought about right at the beginning, which was the MW 1.22 jobs bug. Yaron Koren (talk) 12:51, 6 May 2014 (UTC)

MW 1.23

If you are using MediaWiki 1.22, there is a good chance that trying to generate pages automatically will not work, because of a bug in MW 1.22 in which jobs that modify pages simply do not get run. If that is happening for you, it is recommended to add this call in LocalSettings.php, which should restore the correct behavior:

I have same problem with MW 1.23.1 and SMW 1.9.2, but $wgPhpCli = false; don't solve the problem.

It's not surprising that that fix would not help. If you call runJobs.php, do the pages get created? Yaron Koren (talk) 23:40, 29 June 2014 (UTC)

Yes, this is the solution I use now. Baxi69 (talk) 16:22, 3 July 2014 (UTC)

Alright - this problem came up for the Replace Text extension as well, which similarly makes page edits via jobs, and there some people were able to get around the problem in MW 1.23 by adding this to LocalSettings.php:

$wgRunJobsAsync = false;

That might work here. Yaron Koren (talk) 16:42, 3 July 2014 (UTC)

Now i installed an identical configuration on a new server, i just took the current versions via composer and git. I copied the Page schema from the older wiki (installed about 1 month ago) to the new server. The schema is diplayed corret on the catogory page, but gererating pages don't even create jobs... (i checked this in phpmyadmin...)

Baxi69 (talk) 12:32, 28 July 2014 (UTC)

That's strange; what's the difference between the two setups? Yaron Koren (talk) 12:47, 28 July 2014 (UTC)

Nothing, that's the real strange point. I made a setup protocol for the first, and made the second in same setup. All error scripts are empty. Baxi69 (talk) 13:41, 28 July 2014 (UTC)

I updated now a second wiki on another server with MW 1.23.2 and SMW 2.0, and i have the same effect. Even with adding

$wgRunJobsAsync = false;

No jobs get created at all.Baxi69 (talk) 16:38, 19 August 2014 (UTC)

Is the issue that the jobs are not being created, or that they're not being run? You can check the "job" DB table to see. Yaron Koren (talk) 18:42, 19 August 2014 (UTC)

Not being created. I checked in the job table. Baxi69 (talk) 09:41, 21 August 2014 (UTC)

Blanks at end of parameters

When defining a menuselect forminput for a field the structure parameter needs a blank at the end:

   <Field name="Thema">
      <semanticforms_FormInput>
        <InputType>menuselect</InputType>
        <Parameter name="size">150</Parameter>
        <Parameter name="structure">{{#ask: ... }} </Parameter>
      </semanticforms_FormInput>
      <semanticmediawiki_Property name="LearnItem_LearningGoal">
        <Type>Seite</Type>
      </semanticmediawiki_Property>
    </Field>

so that the form field is generated as:

'''Thema:''' {{{field|Thema|input type=menuselect|size=150|structure={{#ask: ... }} }}}

because:

'''Thema:''' {{{field|Thema|input type=menuselect|size=150|structure={{#ask: ... }}}}}

does not work. Currently the blank is removed when using the schema editor. Manually adding it works. I think this is a bug.

Thanks for letting me know about that. For now, I think you could work around it by switching the order of the parameters. Yaron Koren (talk) 13:44, 14 October 2014 (UTC)

Adding additional information to generated templates

Hi

I am using Semantic Titles to set the Title of my pages to a Semantic Property contained on a page. I then use DEFAULTSORT on the page to tell the category page to sort on the Semantic Title by adding the following to the page:

{{ DEFAULTSORT: {{ #semantic-title: {{PAGENAME}} }} }}

I am using Page Schemas to create Semantic Forms and would like the templates it generates to include this statement after the [[Category:CategoryName]] statement it inserts. Is there a way to get Page Schemas to include additional statements such as this when it generates templates?

Many thanks

Duncan

I don't think so, but I'm not sure. Yaron Koren (talk) 22:53, 7 November 2014 (UTC)

JSMW_Pageschema

To be better able to handle PageSchemas I have created the following GitHub project:

• https://github.com/WolfgangFahl/JSMW_PageSchema

I am willing to show applications for it at SMWCON 2015 - what do I need to do to get a slot there? Also I'd like to be able to change the way the Template are generated. Where would I have to start to do so or is there some kind of callback I could use? --Seppl2013 (talk) 17:53, 13 January 2015 (UTC)

You just need to sign up for SMWCon. If you mean changing the template wikitext that's generated automatically, at the moment you'd have to either change the relevant Semantic Forms code or write your own template-creation code. Yaron Koren (talk) 19:05, 13 January 2015 (UTC)

Uncaught Error: Unknown dependency: jquery (load.php:167) with MW 1.24.1

I can't seem to get PageSchemas working properly on my wiki with MediaWiki 1.24.1. The extension seems to have been loaded properly and I can get to the Create Schema page, but the Add template and Add section buttons don't work. The Javascript console says: Uncaught Error: Unknown dependency: jquery (load.php:167).

Same problem in Chrome & Firefox (latest versions).

I've tried:

1. Upgrading to the latest SemanticForms (instead of the version included with SemanticBundle)
2. Adding $wgIncludejQueryMigrate = true; to my LocalSettings.php
3. Removing SemanticBundle and installing the latest version of SemanticMediaWiki (with Composer) and all extensions manually
4. Clearing out my database & mediawiki directory and setting up brand new a new MW 1.24.1 installation from scratch, then manually reinstalling SemanticMediaWiki + extensions (latest versions)

I read that SemanticMediaWiki 2.0 is officially compatible with MW 1.24.1, which is why I decided to switch to the latest version. I also read about jquery issues with MW 1.24.1 which are supposedly addressed with $wgIncludejQueryMigrate = true;... Could this be the root cause?

Is there anything else I should be tweaking?

Am really at a loss for what to do next, and would appreciate any advice!

You should add "?debug=true" (or "&debug=true") to the URL, so you can see a more helpful JS error message. Yaron Koren (talk) 22:25, 15 January 2015 (UTC)

Ah, now I think I know the issue. This was a JS bug that was fixed way back in September; I assume you're using Page Schemas code from before then. I just released a new version of Page Schemas, that was well overdue; if you get the latest code, the problem will hopefully go away. Yaron Koren (talk) 14:54, 16 January 2015 (UTC)

--- Fixed! Thanks!

I have a similar problem, trying to use SemanticForms extension, &debug=true leads to Uncaught Error: Unknown dependency: jquery, java script fails at line 11268 (jQuery v1.11.3)

if ( !hasOwn.call( registry, module ) ) {
  throw new Error( 'Unknown dependency: ' + module );
}

Special:EditSchema is empty, using PageSchemas 0.4.6, MediaWiki 1.25.1 --Escalator~enwikibooks (talk) 13:19, 27 June 2016 (UTC)

What version of Semantic Forms are you using? Yaron Koren (talk) 14:45, 27 June 2016 (UTC)

Here a list of semantic related extensions. I probably have to update everything first? Thanks. --Escalator~enwikibooks (talk) 11:19, 28 June 2016 (UTC)

• Semantic Forms 2.7
• Semantic MediaWiki 1.9.2
• Semantic Bundle 1.9.2
• Semantic Compound Queries 0.3.4
• Semantic Drilldown 1.4
• Semantic Forms Inputs 0.7
• Semantic Result Formats 1.9.1

Maybe just Semantic Forms, and Semantic Forms Inputs. (Though after the upgrade, you might not need SFI any more.) Yaron Koren (talk) 15:08, 28 June 2016 (UTC)

Sorry for late response, my installation was based on Semantic Bundle which is totally outdated, installing a newer SMW 2.4.x solved everything, thanks for your effort! --Escalator~enwikibooks (talk) 14:52, 17 January 2017 (UTC)

ArrayMaps in Schemas?

How does one format fields for arraymapping? It doesn't appear to be a part of any default selection - therefore, does one edit the xml?

You just need to specify that a field can hold a list of values - I think that's one of the options, no? Yaron Koren (talk) 15:35, 19 January 2015 (UTC)

Thanks Yaron. I'm sorry I asked the wrong question. I'm new to all this and I really like schemas. I watched the YouTube video - which was a great primer. And I'm reading your eBook. My question really is, what about multidimentional data - compound data. How is that handled in schemas? I assume if Internal Objects is part of SB, there has to be a hook into schemas. Thanks for your help.

Yes - I think you just have to click the "Allow multiple instances of this template" checkbox. Yaron Koren (talk) 13:58, 20 January 2015 (UTC)

Ok, I got it. Thanks!

Problem with displaying links in property fields

Hi Guys, Thanks again for all your good work with SMW SB and the bundled extensions. I'm running into a problem that I've tried to resolve independently, so excuses if I am remiss.

I am trying to display an external link in a field of type "text" in the format [http:link Foo]. The display in the side infobox in the field is in the syntax [[propertyname::Foo]] with "Foo" as a link with an icon next to it.

The template code is as follows: [[hasAssociatedFinding::{{{hasAssociatedFinding|}}}]]

The form field code is as follows: {{{field|hasAssociatedFinding|input type=text}}}

The schema text for the template (does not define category) is as follows:

  </Field>
   <Field name="hasAssociatedFinding">
     <Label>Associated Finding</Label>
     <semanticforms_FormInput>
       <InputType>text</InputType>
     </semanticforms_FormInput>
     <semanticmediawiki_Property name="">
       <Type>Text</Type>
     </semanticmediawiki_Property>
   </Field>

I assume this is somehow a bug, but I don't know how to resolve it. Any suggestions?

Dmlddsoms (talk)

Hi - I'm not sure I understand the problem, but could this be the issue? Yaron Koren (talk) 04:31, 9 February 2015 (UTC)

Hi Yaron - see this link Example; this is an external link. It works on your Referata site. --Dmlddsoms (talk)

Did you try changing that setting? Yaron Koren (talk) 14:34, 9 February 2015 (UTC)

Yep, I did it. That did the trick. Thanks! --Dmlddsoms (talk)

Field display settings problem...

Hi again - back with another hitch. This time, if setting the field display to anything other than "Display field always" results in an error in the form display. Here is the schema code:

   <Field name="isSubClassOf" display="nonempty">
     <Label>Sub-Class</Label>
     <semanticforms_FormInput>
       <InputType>textarea with autocomplete</InputType>
       <Parameter name="Restricted"/>
       <Parameter name="size">10</Parameter>
     </semanticforms_FormInput>
     <semanticdrilldown_Filter/>
     <semanticmediawiki_Property name="">
       <Type>Text</Type>
     </semanticmediawiki_Property>
   </Field>

Here is the template code:

{{#if:{{{hasAssociatedFinding|}}}|}}
{{!}}-
! Associated Finding
{{!}} [[hasAssociatedFinding::{{{hasAssociatedFinding|}}}]]}} 

Here is the form code:

! Sub-Class:
| {{{field|isSubClassOf|input type=textarea with autocomplete|restricted|size=10}}}
|-

Here is an example of the display

I cannot find any documentation on this field setting. Comments appreciated...Dmlddsoms (talk)

You need to have the ParserFunctions extension installed. That should probably be better documented, yes. Yaron Koren (talk) 15:44, 10 February 2015 (UTC)

Aha...I see said the blind man. I thought I had that installed. I'll check. BTW, can you explain how the ! Category hack works? Thanks again! Dmlddsoms (talk)

It displays like a pipe, but it isn't a pipe. :) Yaron Koren (talk) 17:50, 10 February 2015 (UTC)

I had the extension installed, just hadn't included in in LocalSettings. Thanks again! Works like a dream now. Dmlddsoms (talk)

How to put "values from category"?

Hi! Using "Change/Create scheme" it is impossible to put the field attribute "values from category". If I check the "filter" and "Get... from category" - it not change the form field. The goal to create form record {{{field|Place|values from category=Places|input type=dropdown}}}. Chvlad74 (talk) 08:34, 6 April 2015 (UTC)

Just add "values from category=Places" in the "parameter names" input for that form field. Yaron Koren (talk) 12:58, 6 April 2015 (UTC)

Thank's, it works! But, for which purposes entered "filter" unit? -- Chvlad74 (talk) 18:18, 6 April 2015 (UTC)

"Filter" is for the Semantic Drilldown extension, if that's what you're asking. Yaron Koren (talk) 18:55, 6 April 2015 (UTC)

Thank's! If it will be wrote on the form, it helps for lames. I cant find any documentation or detail video. -- Chvlad74 (talk) 19:09, 6 April 2015 (UTC)

Great! Sorry, I didn't understand any of that. Yaron Koren (talk) 19:28, 6 April 2015 (UTC)

Installation Problem: Special:Create Schema link does not appear.

I am running MediaWiki 1.25.1

I installed PS with the Semantic Bundle v1.9.2

Page Schema shows v0.4.3 in Special:Version (Now upgraded to v0.4.5)

I have not yet used any of the SMW tools. So there should be no schemas present. SpecialPages displays "Edit Schemas", but it takes me to a blank page.

I tried running Update.php from the web (using /mw-config/) but it fails showing the following error:

Warning: include_once(/languages/SD_LanguageEn.php) [function.include-once]: failed to open stream: No such file or directory in /home/sanders4/public_html/wiki/extensions/SemanticDrilldown/SemanticDrilldown.php on line 186

Any suggestions? WmBliss (talk) 17:44, 8 October 2015 (UTC)

Follow these instructions to see an error message instead of a blank page. You don't need to run update.php for Page Schemas, though to get rid of that Semantic Drilldown message, you should upgrade SD as well. Actually, I wouldn't be surprised if that same error is what's causing the blank page. Yaron Koren (talk) 14:26, 11 October 2015 (UTC)

Using Schema Page, the Cargo Table was not created automatically

Hello, happy to join MediaWiki. I used the Cargo for few days creating tables with no issue, and then installed the Schema, and all was created by Schema except the Cargo table. I see the Cargo table when saving the Page Schema, but no Cargo table was found. Best, Gershi

I think that was a Semantic Forms issue that I just fixed yesterday. If you can, please upgrade to the latest SF code and try generating the pages again. Yaron Koren (talk) 13:10, 26 October 2015 (UTC)

I downloaded from: https://git.wikimedia.org/zip/?r=mediawiki/extensions/SemanticForms&h=e0f15961c5479413d99b5bbc50609a3a9ef7da8f&format=zip

no change in creating the table.

You need to create the Cargo table from the template page, by going to the "Recreate table" tab - could that be the issue? Yaron Koren (talk) 14:28, 26 October 2015 (UTC)

I used the Page Schema to set up all. I defined the Cargo table in the Schema Edit page, and saved. Then go to "genarate pages" on the page menu, and it works - shows all relevant pages to create but does not show a Cargo table in the list. I click on the Generate Pages anyway, but then after few minutes, i search for a Cargo table but there is none. Also the Template code do not show lines related to Cargo at all. no declare and no store commands.

Ah, okay. If you don't mind - what versions are you using of MW, SF, PS and Cargo? Yaron Koren (talk) 14:39, 26 October 2015 (UTC)

SF Ver 3.4 ; SMW_VERSION', '2.2.2' ; Cargo 0.1 (?) PAGE_SCHEMAS_VERSION', '0.4.5' . cant find the MW versio (I just downloaded it last week). Use SoDaddy shared hosting server

Ah, that's it. I believe Page Schemas doesn't do any Cargo stuff if SMW is installed. It's definitely not ideal, but it was the easiest way to avoid having to deal with SMW and Cargo data at the same time. Yaron Koren (talk) 17:11, 26 October 2015 (UTC)

thanks for your support. this does bring up the Cargo. but the NAME of the field is now missing from the PAGE SCHEMA (they used to be in earlier before i deleted the SMW extension), and in the template code in EDIT mode there are no fields attached to DECLARE, but do attached to the STORE function:

...{{#cargo_declare:_table=City}}
</noinclude><includeonly>{{#cargo_store:_table=City|EstablishmentDate={{{EstablishmentDate|}}}|Population={{{Population|}}}|Popularity={{{Popularity|}}} }}..

the results- the FORM note that a certain(first) field is not there. and when VIEW the table it shows no records.( i dont know how to check if there are fields at all).

Yes, okay - this is the bug I mentioned at the beginning. The zip file you got is the latest "stable" release, from a month ago, but what you should use instead is this one. Yaron Koren (talk) 06:47, 27 October 2015 (UTC)

it is working! thx!

That's great! Yaron Koren (talk) 15:26, 27 October 2015 (UTC)

Am I right that also Page Schema 0.4.6 does no Cargo (1.2) stuff if SMW (2.4.4) is installed? Is there a way to disable SMW temporary (e.g. by commenting out enableSemantics('#') in LocalSettings.php)? If so, does this make sense?

Yes, that is still the case. And yes, temporarily disabling SMW makes sense as a workaround. Commenting out enableSemantics() may do the trick, I'm not sure. Yaron Koren (talk) 15:23, 17 January 2017 (UTC)

Internal Server Error, after "Generate Pages"

Whenever I click on "Generate Pages" I get an "Internal Server Error".

Error message continues:

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

PS: 0.4.5

Cargo: 0.10

SF: 3.4

WmBliss (talk) 21:28, 28 October 2015 (UTC)

Does this happen no matter which subset of pages you generate? Yaron Koren (talk) 07:09, 29 October 2015 (UTC)

Yes! Both Templates &/or Forms, when selected cause this. WmBliss (talk) 17:09, 30 October 2015 (UTC)

Alright. Two more questions: what version of MediaWiki are you running? And could you try temporarily disabling Cargo, and see if the problem still happens? Yaron Koren (talk) 22:14, 1 November 2015 (UTC)

Fatal error: Call to a member function children() on a non-object in /home/...

I received this massage after editing manually a line in a schema page in URL ../index.php?title=Category:City&action=edit. and i can no longer access this file in edit mode neither in Schema mode. is there a way to find this file? Thanks.

Are you saying that going to "&action=edit" displays an error message? If so, that's very bad - sorry about that problem. If that's the case, the best option is probably to temporarily disable Page Schemas, then revert your edit. Yaron Koren (talk) 12:01, 2 November 2015 (UTC)

It did help finding the file. but than this Error line ...extensions/PageSchemas/PageSchemas.classes.php on line 328

is still there when the Page Schema is enabled again. Should i delete all directory /pageschema, or is it holding my new forms/template/tables structures inside this directory? BTW are 130 fields to heavy for this system? Cargo/Schema/ are limiting number of fields?

No, you shouldn't delete it. No, it doesn't hold any of the data structure. No, the number of fields isn't the issue. Did you revert your change? If so, the problem should go away... Yaron Koren (talk) 14:10, 2 November 2015 (UTC)

I did fix the Error issue as you recommended. it is strange, when i delete the first half of the fields, or if i delete the second half of the fields, it works fine. but when i keep all 120 fields - the Page Schema in "edit" mode work fine, including generating template and form, but in "Edit Schema" mode it let me edit, but not lett me save changes

Experience the same problem, absolutely. I have a terrible number of fields, too. I guess it happens just because of this. Symptoms: error 500 opening, editing the page and so on. I also made changes manually (copy/paste is easier, remember the number of fields!). Okay, I'm going to re-enable Page Schemas, then we shall take a look. Ядерный Трамвай (talk) 06:01, 26 January 2016 (UTC)

• BTW, since I've had this problem, I created a category with the same name. In "Recent changes" they look identical, but the first link returns 500, and the second — the category I just created. After disabling PS, text from both of them is merged in one page. Magic! …well, I followed the instructions. Editing the page from SpecialPages/Edit Schema returns error 500. And there is no button Edit Schema on the page immediately. But the category displayed without errors now. Ядерный Трамвай (talk) 06:22, 26 January 2016 (UTC)

Are you using the latest version of the Page Schemas code? I made a change in December that I thought fixed this problem. Yaron Koren (talk) 14:57, 26 January 2016 (UTC)

The version is 0.4.5 — seems like it's the latest one. Ядерный Трамвай (talk) 14:03, 30 January 2016 (UTC)

Look at this view http://jantanoo.info/w/index.php?title=%D0%9A%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D1%8F:%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD%D1%8B_c%D1%85%D0%B5%D0%BC_%D0%B3%D0%BE%D0%B4%D0%BE%D1%81%D0%BE%D0%B2&action=editschema Ядерный Трамвай (talk) 14:14, 30 January 2016 (UTC)

Could you add these two lines to LocalSettings.php? That may help do to diagnose the issue. Yaron Koren (talk) 14:25, 1 February 2016 (UTC)

Done. That's it:

Warning: simplexml_load_string(): Entity: line 1393: parser error : expected '>' in /home/admin/web/jantanoo.info/public_html/w/extensions/PageSchemas/PageSchemas.classes.php on line 323

Warning: simplexml_load_string(): Entity: line 1393: parser error : Opening and ending tag mismatch: Label line 1393 and L in /home/admin/web/jantanoo.info/public_html/w/extensions/PageSchemas/PageSchemas.classes.php on line 323

Warning: simplexml_load_string(): Entity: line 1393: parser error : Premature end of data in tag Field line 1392 in /home/admin/web/jantanoo.info/public_html/w/extensions/PageSchemas/PageSchemas.classes.php on line 323

Warning: simplexml_load_string(): Entity: line 1393: parser error : Premature end of data in tag Template line 7 in /home/admin/web/jantanoo.info/public_html/w/extensions/PageSchemas/PageSchemas.classes.php on line 323

Warning: simplexml_load_string(): Entity: line 1393: parser error : Premature end of data in tag PageSchema line 1 in /home/admin/web/jantanoo.info/public_html/w/extensions/PageSchemas/PageSchemas.classes.php on line 323

Fatal error: Call to a member function children() on boolean in /home/admin/web/jantanoo.info/public_html/w/extensions/PageSchemas/PageSchemas.classes.php on line 328 Seems like it's my misspelling, isn't it?Ядерный Трамвай (talk) 17:13, 2 February 2016 (UTC)

Yes, there's probably an error in the XML - although that still shouldn't cause all the problems you're seeing. My guess is that you're not using the very latest version of Page Schemas; there have been a lot of changes since 0.4.5 was released. I need to release a new version. Are you using Git? Yaron Koren (talk) 17:49, 2 February 2016 (UTC)

Not yet. And there's OK with my code, I've checked. Ядерный Трамвай (talk) 18:38, 4 February 2016 (UTC)

Alright. Well, i just released version 0.4.6 yesterday - please try upgrading to that, if you haven't already. Yaron Koren (talk) 20:18, 4 February 2016 (UTC)

Field display if not empty doesn't work

If I select 'display if not empty' under a field in page schemas I get messed up HTML. I'm using cargo. This example is with datepicker, but happens on just normal text too.

Here's the form xml it creates:

  <Template name="Project Dates" multiple="multiple" format="standard">
    <semanticforms_TemplateDetails>
      <Label>Project Dates</Label>
    </semanticforms_TemplateDetails>
    <cargo_TemplateDetails>
      <Table>Project_Dates</Table>
    </cargo_TemplateDetails>
    <Field name="Milestone">
      <Label>Milestone</Label>
      <semanticforms_FormInput>
        <InputType>text with autocomplete</InputType>
      </semanticforms_FormInput>
      <cargo_Field>
        <Type>Text</Type>
      </cargo_Field>
    </Field>
    <Field name="Planned_Date" display="nonempty">
      <Label>Planned Date</Label>
      <semanticforms_FormInput>
        <InputType>datepicker</InputType>
      </semanticforms_FormInput>
      <cargo_Field>
        <Type>Date</Type>
      </cargo_Field>
    </Field>
    <Field name="Expected_Date" display="nonempty">
      <Label>Expected Date</Label>
      <semanticforms_FormInput>
        <InputType>datepicker</InputType>
      </semanticforms_FormInput>
      <cargo_Field>
        <Type>Date</Type>
      </cargo_Field>
    </Field>
    <Field name="Actual_Date" display="nonempty">
      <Label>Actual Date</Label>
      <semanticforms_FormInput>
        <InputType>datepicker</InputType>
      </semanticforms_FormInput>
      <cargo_Field>
        <Type>Date</Type>
      </cargo_Field>
    </Field>
  </Template>

This is in the generated template page:

{{#cargo_declare:_table=Project_Dates|Milestone=Text|Planned_Date=Date|Expected_Date=Date|Actual_Date=Date}}
</noinclude><includeonly>{{#cargo_store:_table=Project_Dates|Milestone={{{Milestone|}}}|Planned_Date={{{Planned_Date|}}}|Expected_Date={{{Expected_Date|}}}|Actual_Date={{{Actual_Date|}}} }}{| class="wikitable"
! Milestone
| {{{Milestone|}}}
{{#if:{{{Planned_Date|}}}|
{{!}}-
! Planned Date
{{!}} {{{Planned_Date|}}}
 }}{{#if:{{{Expected_Date|}}}|
{{!}}-
! Expected Date
{{!}} {{{Expected_Date|}}}
 }}{{#if:{{{Actual_Date|}}}|
{{!}}-
! Actual Date
{{!}} {{{Actual_Date|}}}
 }}|}

And this is my eventual HTML output:

Milestone	{{#if:|
Planned Date	}}{{#if:|
Expected Date	}}{{#if:|
Actual Date	}}|}

--Kc5vcx (talk) 15:51, 2 November 2015 (UTC)

It looks like the issue is just that you don't have the ParserFunctions extension installed. That looks like a bug; that option should not be there if PF is not installed. Yaron Koren (talk) 17:15, 2 November 2015 (UTC)

Thanks again. I didn't realize I needed the extension, but still have some formatting issues after enabling it. As I cleaned it up to make it more readable it started to work better. Definately the last |} closing the table needs to be on a new line, but there is still some more separation needed with the ifs. For example:

<includeonly>{{#cargo_store:_table=Project_Dates|Milestone={{{Milestone|}}}|Planned_Date={{{Planned_Date|}}}|Expected_Date={{{Expected_Date|}}}|Actual_Date={{{Actual_Date|}}} }}{| class="wikitable"

! Milestone | {{{Milestone|}}}
{{#if:{{{Planned_Date|}}}|
{{!}}-
! Planned Date
{{!}} {{{Planned_Date|}}}
 }}
{{#if:{{{Expected_Date|}}}|
{{!}}-
! Expected Date
{{!}} {{{Expected_Date|}}}
 }}
{{#if:{{{Actual_Date|}}}|
{{!}}-
! Actual Date
{{!}} {{{Actual_Date|}}}
 }}

|}
</includeonly>

I believe I found another small bug if you define a field to always have values in a namespace such as User, the User: gets prepended to the User| variable in the if statement.--Kc5vcx (talk) 19:30, 2 November 2015 (UTC)

Thanks for letting me know about the formmatting issue. For the 2nd issue - the software prepends "User:" on purpose, so that it doesn't need to be typed in to the field. Is there a problem with it? Yaron Koren (talk) 21:03, 2 November 2015 (UTC)

I agree/understand that it prepends the User: namespace which makes sense on the text/link, but I'm not sure it should also be applied to the if condition. Is it supposed to check if the page exists? Otherwise if you prepend to the variable in an if, now there's always text there, which I believe is making it always true.--Kc5vcx (talk) 22:10, 2 November 2015 (UTC)

Oh, I get it. Yes, that's bad. Yaron Koren (talk) 00:38, 3 November 2015 (UTC)

That 2nd issue turned out to be a bug in Semantic Forms; I think I just fixed it in the SF code. Yaron Koren (talk) 16:29, 3 November 2015 (UTC)

Cargo table not created from Schema

Hello, I continue last discussion. A Schema with 120 fields was not saved, then the cargo table with 120 fields was not created from template created by Schema. I tried to split the size and it helped saving the Schema, but the table still not created. How can I control this? maybe some characters are no acceptable by Cargo and it is not a size issue? BTW is there a limit to the field name size?

This is really a Cargo question, but - yes, there is an issue specifically with having too many "Text" and/or "Wikitext" fields in a table; I discovered this a few weeks ago. I need to fix this in Cargo itself, by having the code default to using the TEXT type for these fields instead of VARCHAR, like it does now. But until then, there's a hack you can do that will (hopefully) get it all working: make sure you have the latest version of Cargo, and then, in "Edit schema", add "size=2000" as a parameter to each field of type "Text" or "Wikitext". Hopefully that will work... Yaron Koren (talk) 17:23, 4 November 2015 (UTC)

is it possible that certain field names are not acceptable by Cargo? i found out of the 120 fields 2 field names that i changed and the Cargo was created fine. a possible logic reason - the Cargo "Chop" the field name and may result in recurrence of same names?. another phenomena - if too many fields, maybe a time out occur?

Ah, that's great. There are various field names that can cause problems - "Update" is one, as noted on the Cargo talk page. What were the names of the two problem fields you had? Yaron Koren (talk) 14:17, 6 November 2015 (UTC)

words-sent by,by,desc - do not allow Template to create a Cargo table.

I tried text=2000 as suggested (in the Form section -

      <semanticforms_FormInput>
       <InputType>text</InputType>
       <Parameter name="size">2000</Parameter>
     </semanticforms_FormInput>

but no help, and no Cargo table was created. the field names i add are acceptable for Cargo as i checked it separately in a Schema i created for the test. Could it be a TIME OUT of the system due to a too many fields per table?

BTW when -add "size=2000" as a parameter to each field of type "Text" - is this goes to template or only the form definitions?

IT IS working! I added the text(size=2000) parameter in the template in declare function.

Cool. By the way, a few days ago I changed the code in Cargo, adding a new "String" type which represents what "Text" used to be; "Text" now is always represented as a "TEXT" DB field. So if you get the latest Cargo code, you shouldn't need the "size" parameters any more. And thanks for letting me know about those field names - "BY" and "DESC" are both used in SQL, so it's not too surprising. Yaron Koren (talk) 20:23, 8 November 2015 (UTC)

how to query inline?

I'm not sure if this is currently possible, but would like to check my understanding and features available...

I'm trying to associate a set of 'contacts' with a particular 'project'. These (internal) contacts are all also wiki users (authenticated and info available through ldap). I don't want to duplicate the contact info and would like it to be dynamic, or rather only updated in the common ldap database. So, I'd like to give or search for a user and store just their user name in the table, but then show their full contact info on the actual project page (via an inline query). So far I have created a multiple item template where I can specify user name in the User: name space as a page, and then the resulting template output will be a link to their user page (where they currently hard code contact details, and I'd like to eventually use LDAP external data). My question is really how/where can I specify an inline query to put this info on the same page rather than link. Since I'm using Page Schemas to automate I'm trying to start as far back, closer to the source as possible to avoid redoing multiple edits if I later regenerate pages. I thought maybe I could put text for the query in a section, but can't seem to preload text, if that would even work. I thought maybe if I output data as plain text rather than a table I could specify pre/post text to embed it in my query string, but that doesn't look possible either. Any other ideas on putting this in Page Schemas? If I added text directly in the SemanticForm, can it handle it, or would I need to edit the output template directly to do what I want?

One more thing. Unfortunately our usernames are more cryptic and I use the RealNames extension to make it easier. It would be even better if I could also some how use the autocompletion search on external data to search for a name in LDAP and return their username. From reading, I think I could pull extra text as a description (i.e. full name as I search for user), but I'd like to do the opposite, or essentially store the description in second column and discard the first.

Thanks. --Kc5vcx (talk) 16:09, 28 November 2015 (UTC)

For the first question - I think you'll have to add it in directly to the template, unfortunately. For the second - I'm not sure I understand, but that sounds like a Semantic Forms question. Yaron Koren (talk) 15:55, 30 November 2015 (UTC)

oops, can't view,edit, or access history of category page w/ page schema

Hm, I was manually editing the page schema code for category page. Somehow I must have added an extra carrot or wrong syntax and can no longer view or edit. I can't even view the history to revert. Here's the error I'm getting.

Warning: simplexml_load_string(): Entity: line 1: parser error : Start tag expected, '<' not found in /home/xxx/mediawiki-1.26.0/extensions/PageSchemas/PageSchemas.classes.php on line 323 Warning: simplexml_load_string(): Redefinition of element PageSchema in /home/xxx/mediawiki-1.26.0/extensions/PageSchemas/PageSchemas.classes.php on line 323 Warning: simplexml_load_string(): ^ in /home/xxx/mediawiki-1.26.0/extensions/PageSchemas/PageSchemas.classes.php on line 323 Fatal error: Call to a member function children() on a non-object in /home/xxx/mediawiki-1.26.0/extensions/PageSchemas/PageSchemas.classes.php on line 328

Ever seen this? Any way to get it back? Is there some sort of error checking that can be done to avoid it? Thanks. --Kc5vcx (talk) 20:42, 30 November 2015 (UTC)

That's not good! Obviously, that's a bug that should be fixed, but for now, you can uninstall PS, fix the XML, then reinstall it. Yaron Koren (talk) 22:09, 30 November 2015 (UTC)

I noticed the post above and did as you said commenting out the extension, and was able to revert to earlier version. Not sure exactly how I got there, but at least it's not dead. Thanks. --Kc5vcx (talk) 22:12, 30 November 2015 (UTC)

By the way, I think I just fixed this problem - if you get the latest Page Schemas code, bad XML (or whatever it is) will hopefully not lead to a crash. Yaron Koren (talk) 14:51, 3 December 2015 (UTC)

lingo extension causes duplicates in generate pages

I just installed lingo, and for some reason now the generate pages of a category is showing duplicates for all my templates and form. I can make it go away by commenting out the require_once in my LocalSettings. I'm not sure if it's harmful or might cause problems regenerating at the same time, but it is annoying. Any thoughts, is it because of shared code w/ semantic glossary? I'm using lingo instead of semantic glossary because I'm using the cargo backend and didn't see that it'd work.

No idea. What do you mean by "duplicates"? Yaron Koren (talk) 13:11, 4 December 2015 (UTC)

Like this, all the links are listed twice...

Generate the following pages, based on this category's schema:

All  None

 Template:DDP Identification
 Template:DDP Details
 Template:DDP Dates
 Template:DDP Status
 Template:DDP Docs
 Form:DigitalDesignProjects
 Template:DDP Identification
 Template:DDP Details
 Template:DDP Dates
 Template:DDP Status
 Template:DDP Docs
 Form:DigitalDesignProjects

--Kc5vcx (talk) 13:25, 4 December 2015 (UTC)

Oh, interesting. Is that definitely the only part of the process where you're seeing duplication? Yaron Koren (talk) 14:14, 4 December 2015 (UTC)

That's the most obvious I've encountered being visible, but can't say for sure. I don't think it's related to my other issue on cargo w/ duplicates. --Kc5vcx (talk) 14:44, 4 December 2015 (UTC)

Alright. I just tried installing Lingo, but couldn't replicate this bug. What versions are you running of MediaWiki, Page Schemas, Semantic Forms and Lingo?

MediaWiki 1.26.0

Page Schemas 0.4.5 (10abb6d) 20:29, November 19, 2015

Semantic Forms 3.4.1 (acd23c8) 15:03, November 26, 2015

Lingo 1.2.1-dev (da185f4) 03:20, October 12, 2015

--Kc5vcx (talk) 22:06, 4 December 2015 (UTC)

I am actually seeing duplicates for the form and cargo table name elements of the 'edit schema' page with Lingo enabled, and again goes away disabling it. I also have another page schema for a category that does the same thing, so it's not just the one. --Kc5vcx (talk) 06:12, 6 December 2015 (UTC)

That's strange - that's almost the exact same set of versions I was using. Could it be that you're including one of these extensions more than once in LocalSettings.php? Yaron Koren (talk) 00:54, 7 December 2015 (UTC)

I don't see any duplicate includes in my LocalSettings. --Kc5vcx (talk) 02:10, 7 December 2015 (UTC)

Is this still an issue? And if so, could you include detailed steps to reproduce this? (I never used PageSchemas.) --F.trott (talk) 20:22, 8 October 2016 (UTC)

--Pitchke (talk) 09:51, 2 May 2017 (UTC) Just installed a new MW + SMW, have the same issue (MW 1.28.2, SMW 2.5.1). Versions are

• Page Schemas 0.4.6 (79aafee) 02:03, 25 October 2016
• Lingo 2.0.1 (same problem with 2.0.2-dev (ad924ae) tested on 2017-05-03)

Property fields are duplicated when Editing Schema, for both SMW Properties and Cargo. Confirmed working well when Lingo is disabled. And I only have one call to enableSemantics(); in LocalSettings.php (if I remove this I get no property definition at all, and when defined I get duplicates).

--Pitchke (talk) 13:47, 3 May 2017 (UTC) Confirms that the problem does not appear with Extension:Semantic_Glossary (2.1.0).

Can't save page under edit schema

I'm at a point where I can't seem to save any additional fields when I use 'edit schema'. I thought it may have had to do something with +/- in the display before field of the previous field or something weird like a field named URL, but just tried again with a TEST field at the end and it won't let me save. It returns the same edit schema page without the addition, and if I click save again (now without the addition) it works. If I make minor changes to the existing schema like a description or type it lets me save it. I have 74 fields and there's now over 800 lines in the edit source, just to give you an idea of the size/complexity. This sounds similar to a topic above "Fatal error: Call to a member function children() on a non-object in /home/..." where he seemed to think he was at a max number of fields based on behavior. (same versions as I posted above for lingo, but have it temporarily disabled doing me schema edits to be safe). I have the debug console enabled, but don't see any error messages. --Kc5vcx (talk) 06:01, 6 December 2015 (UTC)

That's a lot of fields! My guess is that you just need to increase the value of max_input_vars. Yaron Koren (talk) 00:57, 7 December 2015 (UTC)

That was it, thanks. I looked for a mediawiki setting but forgot about php. --Kc5vcx (talk) 02:11, 7 December 2015 (UTC)

weird things happening with section titles and free text

I've been fighting weird things happening towards the end of the form when it reopens the form for editing. I end up with section headings duplicated and free text moving up into previous text areas. I can understand it's tricky parsing the text back in to populate the form, especially in regards to multiple instances and in particular when no instances exist. Along the way I thought I could add either a dummy template or make sure I had a real data field at the end, but that doesn't seem to be enough to segregate the data. I think maybe I need to define at least one instance in each of my multiple instance templates. I know there's a parameter for the template in forms, but is there syntax in the edit schema page or the xml to do this?

Page schemas has been my crutch for getting this setup, because I really like the automation. Was the intention only ever to help kickstart a first pass at setup and am I trying too hard to stick with it? If I dig in and start editing pieces separately, I'm afraid of accidentally overwriting something is I were to use page schemas again, maybe I should disable it after setup and on my own. --Kc5vcx (talk) 19:20, 6 December 2015 (UTC)

What exactly is the syntax you want to set in the form and/or template? Also, if you're running into a bug in SF, it would of course be good to report that in one of the relevant channels. Yaron Koren (talk) 00:59, 7 December 2015 (UTC)

I think this is the issue I'm facing. Multiple_Instance_templates_directly_after_section I'm not sure it was ever resolved and the temporary workaround was to put section text in a template. I guess I'm understanding a bit better now and could include these templates in page schemas, but is there any better way? Also, I'd like to be able to define the miniumum instances in {{{for template|Template|multiple|minimum instances=1|label=Label}}} as that was originally what seemed to help the issue for me. --Kc5vcx (talk) 01:23, 7 December 2015 (UTC)

Right, there's no way to set the minimum/maximum instances from within Page Schemas - it would be good if there were a way to do it. Yaron Koren (talk) 01:51, 7 December 2015 (UTC)