Last modified: 2013-12-03 22:58:40 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 T53238, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 51238 - Value of {{PAGENAME}} gets cached and it shouldn't
Value of {{PAGENAME}} gets cached and it shouldn't
Status: RESOLVED FIXED
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: High normal
: ---
Assigned To: Gabriel Wicke
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-07-12 13:48 UTC by Inez Korczyński
Modified: 2013-12-03 22:58 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Inez Korczyński 2013-07-12 13:48:29 UTC 
* create two articles (Pagename1 and Pagename2) with wikitext: 'Pagename: {{PAGENAME}}'
* parse those articles with Parsoid in order (for instance, requerst http://192.168.142.128:8000/localhost/Pagename1 and then http://192.168.142.128:8000/localhost/Pagename2)
* Output for both requests would be 'Pagename: Pagename1' <- WRONG
Comment 1 Inez Korczyński 2013-07-12 14:07:35 UTC 
If I make cacheKey in line 136 of ext.core.TemplateHandler.js unique (by adding some random string) this issue disappears. Obviously it is not a solution, but should help with finding where is the problem.
Comment 2 Gabriel Wicke 2013-07-12 15:30:08 UTC 
Are you using the PHP preprocessor?
Comment 3 Inez Korczyński 2013-07-12 15:30:52 UTC 
Yes. I'm using PHP preprocessor.
Comment 4 Gabriel Wicke 2013-07-12 15:35:25 UTC 
Ok, I successfully reproduced this locally. Will investigate.
Comment 5 Inez Korczyński 2013-07-12 15:36:41 UTC 
In order to reproduce it it seems that it have to be the same "fork" handling request, if it's different fork then it works correct. That's probably why it is less likely to happen on production.
Comment 6 Gabriel Wicke 2013-12-03 22:58:40 UTC 
I can't reproduce this any more. Closing as fixed.

Inez, please reopen if this is still an issue.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links