Last modified: 2010-08-13 19:10:22 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 T26503, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24503 - [SMWWriter] Only check correctness of add object if remove object does not exist
[SMWWriter] Only check correctness of add object if remove object does not exist
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Other (Other open bugs)
unspecified
All All
: Normal critical (vote)
: ---
Assigned To: denny vrandecic
: patch, patch-need-review
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-22 21:10 UTC by Samuel Lampa
Modified: 2010-08-13 19:10 UTC (History)
1 user (show)

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


Attachments
Only check correctness of add object if remove object does not exist (615 bytes, patch)
2010-07-22 21:10 UTC, Samuel Lampa
Details

Description Samuel Lampa 2010-07-22 21:10:09 UTC
Created attachment 7585 [details]
Only check correctness of add object if remove object does not exist

in checkSubject(), the first line:
if ( !$add->equals($this->title) ) return false;
... creates errors when doing delete operations using the internal API.

This is apparently due to the fact that it is executed regardless of whether a remove object exists or not, while the correct behaviour would be to only execute it if a remove object does not exist (because when doing remove operations, you will not send a valid add object).

Solution: Move the line above into the "else" part of the if ( $remove->exists() ) just below it (see submitted patch).
Comment 1 denny vrandecic 2010-08-13 19:10:22 UTC
Resolved for now as suggested (in revision 71039). Need to figure out what it means though, may lead to other bugs...

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


Navigation
Links