I used the test beta wiki, moving this file from de.wikipedia.org there: https://test.wikimedia.beta.wmflabs.org/wiki/File:Rajamangala_University_of_Technology_Rattanakosin_Salaya_Campus_Stadium.jpg
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 12 2019
Jun 11 2019
Jun 3 2019
@DannyS712 perfect, thanks!
Clicking on the "move to commons" link for this file:
https://de.wikipedia.beta.wmflabs.org/wiki/Datei:TEST_Euro_exchange_rate_to_TRY_-_Turkish_Currency_and_Debt_Crisis_2018.svg
Renaming by adding AGAIN in front of the title and clicking submit then
Not sure how I can test this, i.e. create a file page without a file. So far I did not manage to "get rid of the file". Could you either prepare a page for me on a test wiki, or I double check once it is deployed?
summarizing daily: For now we are ok with "good enough". No further scoping necessary :)
When trying to test this, I get an error message with the following details
Not sure this is us, but just in case pasting it here
May 31 2019
This error page exists already (I think it was done back then: T189439: Error situations (wrong file format, abuse filter failure...) lead to an error page )
@awight I would be ok with using the core message for now, since we are showing this from our blocking error page anyways.
Since in the screenshot you posted the message is shown o top of the file import preview page, I'm pasting the blocking error page mock in here again to be sure we have the same thing in mind:
@Aklapper Yes, the codebase is part of Extension:Popups. However, I would not call it a subproject of Page-Previews, but another instance of popups. So I guess we could have a Popups project and then ReferencePreviews and PagePreviews as subprojects, but I'm not sure if that will help very much. And thinking about it, I would like to keep the option of tagging sth with both projects, and other tickets with just one of them.
The ticket was linked a bit misleadingly, it is general background on why we remove the keywords.
Self, self2 and mutlilicense are the instances where I could find the keywords being used. What the replacement does is only add the magic keywords, thus, to keep the config file as concise as possible, in this case, where the template replacement becomes obsolete by removing the magic keywords, we should not list them anymore.