Good morning all,
I have a question about a problem that cropped up during my update from 1.18 to 1.21.1.
With one exception everything went smoothly during my update, but now all of my images, appear to be without thumbnails and inadvertently using File protocol links.
The generated source for embedded images looks like this: <p>[<a rel="nofollow" class="external text" href="File:ReportedTime.jpg%7C451px%7CReported">time per activity on Project</a>]</p>
Generated from: [[File:ReportedTime.jpg|451px|Reported time per activity on Project]]
Any idea what I may have done wrong. Is there a new setting that I may have missed? Has anyone ever seen this sort of issue before?
Thank you, Derric Atzrott Computer Specialist Alizee Pathology
On 7/9/13, Derric Atzrott datzrott@alizeepathology.com wrote:
Good morning all,
I have a question about a problem that cropped up during my update from 1.18 to 1.21.1.
With one exception everything went smoothly during my update, but now all of my images, appear to be without thumbnails and inadvertently using File protocol links.
The generated source for embedded images looks like this:
<p>[<a rel="nofollow" class="external text" href="File:ReportedTime.jpg%7C451px%7CReported">time per activity on Project</a>]</p>
Generated from: [[File:ReportedTime.jpg|451px|Reported time per activity on Project]]
Any idea what I may have done wrong. Is there a new setting that I may have missed? Has anyone ever seen this sort of issue before?
Thank you, Derric Atzrott Computer Specialist Alizee Pathology
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
What happened is that url protocols became case insensitive. So if you had added file: as a url protocol, previously it would trigger only on file:foo not File:foo. The solution is to change your entry in $wgUrlProtocols so that it is 'file://' instead of 'file:'.
--bawolff
What happened is that url protocols became case insensitive. So if you had added file: as a url protocol, previously it would trigger only on file:foo not File:foo. The solution is to change your entry in $wgUrlProtocols so that it is 'file://' instead of 'file:'.
--bawolff
Thank you bawolff. That explains the root of the issue much better as opposed to the change I needed to make to fix it, which would have been much more useful had I decided to keep File protocol links enabled.
I've opted to just disable file protocol links in general though as it was just a left over configuration change from some time ago that I had forgotten to remove when we determined we wouldn't be using it.
I think that's now twice in as many days I've been ninja'd in an email. Makes me laugh a little bit every time it happens.
Thank you, Derric Atzrott
wikitech-l@lists.wikimedia.org