Last modified: 2012-04-06 14:37:24 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 T37750, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35750 - Initial parsing ( != PST parsing) of a newly created page should be done after the page is there
Initial parsing ( != PST parsing) of a newly created page should be done afte...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.20.x
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-06 05:40 UTC by Liangent
Modified: 2012-04-06 14:37 UTC (History)
2 users (show)

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


Attachments

Description Liangent 2012-04-06 05:40:56 UTC
Test case:

Create a page [[Template:SelfA]] with the following content:

{{ {{PAGENAME}} | 0 }}

Create a page [[Template:TselfA]] with the following content:

{{ #if: {{{1|}}} | + | {{selfA}} }}

After saving of the second page, I see this on the page:

Template:TselfA

which is actually a selflink.

After purging I see:

+

which is expected on the first view.
Comment 1 Tim Starling 2012-04-06 06:06:09 UTC
Parsing needs to be done before save so that AbuseFilter and SpamBlacklist can reject the edit based on the parse results. It's possible to do parsing both before and after edit, and we do if you use {{REVISIONID:}}, but this doubles the save time and allows spam filtering to be bypassed.
Comment 2 Liangent 2012-04-06 09:41:38 UTC
(In reply to comment #1)
> Parsing needs to be done before save so that AbuseFilter and SpamBlacklist can
> reject the edit based on the parse results. It's possible to do parsing both
> before and after edit, and we do if you use {{REVISIONID:}}, but this doubles
> the save time and allows spam filtering to be bypassed.

Hmm from your comment I found another bug which is submitted as bug 35754.

A better solution can be to do initial parsing before saving but treat the page to parse as if it's there already in parsing progress.

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


Navigation
Links