Last modified: 2013-03-01 04:03:33 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 T47364, 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 45364 - Moving / renaming files does not work
Moving / renaming files does not work
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
NSFileRepo (Other open bugs)
master
All All
: Normal normal (vote)
: ---
Assigned To: Jack D. Pond
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-02-25 17:33 UTC by Jack D. Pond
Modified: 2013-03-01 04:03 UTC (History)
1 user (show)

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

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

Description Jack D. Pond 2013-02-25 17:33:18 UTC 
When I move rename the page which contains the attachments to another namespace, the files are not moved successfully.
 
For instance I try to copy the page: File:Example.png to File:Protected_Namespace:Example.png I get the warning:
 Warning: rename(C:\inetpub\wwwroot\w\images\/8/8a/Hugo14.png,C:\inetpub\wwwroot\w\images\/103/8/8a/Protected_Namespace:Hugo14.png):
The filename, directory name, or volume label syntax is incorrect.
(code: 123) in C:\inetpub\wwwroot\w\includes\filerepo\FSRepo.php on line 217 
 
I'm obviously using a IIS Server (Windows NT 6.1 build 7601 (Windows Server 2008 R2 Datacenter Edition Service Pack 1) and PHP 5.3.8.
 
Mediawiki 1.17 and NSFileRepo 1.4 (latest trunk: r108492)

Am I the only one experiencing this error? Might it be a bug?
 
http://www.mediawiki.org/w/index.php?title=User:Tschuliaen
Comment 1 Jack D. Pond 2013-02-27 23:10:43 UTC 
Class Title was changed so that it now looks at both the reply status from hook userCan and the array.  Therefore, in order not to return a positive result, the array $result needs to be emptied or Title now interprets a non-null as a positive response (user can).

I've added this fix to this bug and will fix it concurrently.
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