Last modified: 2014-01-28 15:47:59 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62533, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60533 - jobs from "Generate pages" sit in the job table and are not executed.
jobs from "Generate pages" sit in the job table and are not executed.
Status: RESOLVED DUPLICATE of bug 58719
Product: MediaWiki extensions
Classification: Unclassified
PageSchemas (Other open bugs)
REL1_22-branch
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-28 15:42 UTC by Greg Rundlett
Modified: 2014-01-28 15:47 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Greg Rundlett 2014-01-28 15:42:10 UTC
There are actually two problems here:
a) jobs are not run automatically, you have to manually invoke runJobs.php to clear out the job table.
b) some jobs will silently fail - and persist in the job table

I defined a schema [1] using PageSchemas and when I try to "Generate pages" the jobs are sent to the job table, but are not actually completed.  When I've used maintenance/runJobs.php to manually clear the job queue, some jobs are executed (namely the properties and templates), but others are not recognized as needing execution.  showJobs.php reports 0 jobs.

For jobs that just refuse to execute, I guess I could try to de-serialize the 'params' content from the database to create the form.

Example content from the 'params' field of a form creation job that did not execute:

a:2:{s:7:"user_id";i:2;s:9:"page_text";s:1107:"<noinclude>\nThis is the "Person" form.\nTo create a page with this form, enter the page name below;\nif a page with that name already exists, you will be sent to a form to edit that page.\n\n\n{{#forminput:form=Person|autocomplete on category=Person}}\n\n</noinclude><includeonly>\n{{{info|create title=Create a new Person|edit title=Edit Person}}}\n<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>\n{{{for template|Person}}}\n{| class="formtable"\n! First Name:\n| {{{field|First Name|input type=text}}}\n|-\n! Last Name:\n| {{{field|Last Name|input type=text}}}\n|-\n! Department:\n| {{{field|Department|input type=checkbox}}}\n|-\n! Manager:\n| {{{field|Manager|input type=text with autocomplete}}}\n|-\n! Email Address:\n| {{{field|Email Address}}}\n|}\n{{{end template}}}\n\n'''Free text:'''\n\n{{{standard input|free text|rows=10}}}\n\n\n{{{standard input|summary}}}\n\n{{{standard input|minor edit}}} {{{standard input|watch}}}\n\n{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}\n</includeonly>\n";}

What I found out is that any form that has a field of type "email" would fail to execute.  Changing the schema so that the "Email Address" field was of type "text" worked to allow runJobs.php to execute the job and create the corresponding form.

[1] http://pastebin.com/1FNGaHsW
Comment 1 Yaron Koren 2014-01-28 15:47:59 UTC

*** This bug has been marked as a duplicate of bug 58719 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links