Last modified: 2012-06-07 15:52: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 T33642, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 31642 - Second special property Modification Date of Type Page (1.7.1)
Second special property Modification Date of Type Page (1.7.1)
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Unprioritized normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-12 09:00 UTC by [[kgh]]
Modified: 2012-06-07 15:52 UTC (History)
3 users (show)

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


Attachments

Description [[kgh]] 2011-10-12 09:00:02 UTC
MW 1.16.5 and SMW 1.6.1

In this configuration a second special property "Modification Date" of Type Page appears which is not recognised as a special property. As you click on it you get 25 results. Browsing to the next 25 results is not possible. On Special:Properties it say that there are only 3 pages containing this property.

See here http://www.fundraising-wiki.de/s/Spezial:Attribute
Comment 1 [[kgh]] 2012-06-07 00:26:49 UTC
MW 1.16.5 and SMW 1.7.1

The problem persists. The next step will be to upgrade to MW 1.19.x which unfortunately will not take place within the next 8 week. Keeping this open, however this bug may be kept on hold until the upgrade was performed.
Comment 2 [[kgh]] 2012-06-07 15:52:59 UTC
I had to downgrade to SMW 1.6.1 again since SMW 1.7.1 caused too many issues, e.g. #set and #info on the wiki. By doing so, I deleted the smw datatables and rebuild them from scratch. The good news is, that the behaviour described with this bug vanished. Thus I am closing this in good faith as RESOLVED WORKSFORME. :)

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


Navigation
Links