Last modified: 2012-11-30 08:25:02 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 T25189, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23189 - Redirect issue
Redirect issue
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Markus Krötzsch
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-14 06:15 UTC by Patrick
Modified: 2012-11-30 08:25 UTC (History)
1 user (show)

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


Attachments

Description Patrick 2010-04-14 06:15:45 UTC
Consider the following scenario:
There is a property "Property:Customer" and a page "Xyz AG". On a page "Project 123" we have "[[Customer::Xyz AG]]". The query {{#show: Project 123 |?Customer}} returns "Xyz AG".

Now someone moves "Xyz AG" to "Abc AG". A redirect from page "Xyz AG" to "Abc AG" gets automatically created. {{#show: Project 123 |?Customer}} now returns "Abc AG" - everything as expected. Now someone decides that the move was wrong, and moves "Abc AG" back to "Xyz AG". A redirect from "Abc AG" to "Xyz AG" gets created, which now contains the actual content again. But when you run the query {{#show: Project 123 |?Customer}}, there is no result at all anymore - it should
return "Xyz AG".

---

I figured out that the 'smw_iw' column in the 'smw_ids' table needs to be emptied (remove ':smw-redi') for those rows where the column 'smw_title' equals the page name of the ex-redirect in order to fix the problem.
Comment 1 Markus Krötzsch 2010-04-14 15:57:29 UTC
Thanks, I will try to debug his. Is the problem happening on SMW 1.5.0 or on some other version?
Comment 2 Patrick 2010-04-14 18:05:49 UTC
Yes, that's 1.5.0 - I'm not sure if it happened with earlier versions, maybe I just never encountered it.

Thanks!
Comment 3 Markus Krötzsch 2010-05-27 12:58:15 UTC
This problem was introduced by a typo in SMW 1.5.0 and will be fixed in SMW 1.5.1. Moving an affected page back and forth again fixes the database entry. I fear that the usual date repair feature of SMW may not achieve this (just like a normal re-safe of the page may not suffice). If many pages are affected, then the thorough repair (deleting all data first, as described on the SMW homepage under "repair") is required.

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


Navigation
Links