> From: "John W. Foster" <jfoster81747(a)verizon.net>
> On Sun, 2011-12-04 at 22:09 +0100, Platonides wrote:
>> > On 01/12/11 00:51, John Foster wrote:
>>> > > My mediawiki 1.17 installation as gone nuts. It is not correctly
>>> > > identifying things where the first letter context has changed. example:
>>> > > Template: tlx call does not find Template:Tlx In the past this has made
>>> > > no difference.
>> >
>> > Did you change $wgCapitalLinks to false?
> I did indeed, as per the instructions at the WorkingWiki site. I have
> been advised by the author that it is actually not necessary, but for
> now the damage is already done, so I will just leave it& clean up the
> issues.
> I would appreciate any advice as to which way is best...context
> sensitive or not. It wont matter once I get finished using templates
> built by others that I've borrowed from other sites. I intend to never
> allow content that depends on shortcuts or acronyms and I like the
> titles of everything to begin with caps. Just a personal thing LOL.
> Thanks for the reply.
If you prefer titles beginning with caps, you probably prefer
$wgCapitalLinks = true. In that case, your WorkingWiki project titles
will also begin with capitals, because they're implemented as page
titles. Otherwise, as far as I can recall, it makes no difference to
WW. I apologize for not being more clear in my installation
instructions. I've improved them now.
Did you take a backup before running cleanupCaps.php? If you did
take one, you may be able to undo the damage by restoring from backup
and changing $wgCapitalLinks back to true.
Lee Worden
>> >
>>> > > Only recent changes are installation of the
>>> > > Extension:WorkingWiki. The extension seems to be doing its job though there
>>> > > are some issues with Latex (.sty) sheets. I just do not know if the
>>> > > WorkingWiki, which did alter the editing interface, is the cause. I will be
>>> > > contacting the author re: this.
>> >
>> > I don't think Extension:WorkingWiki would have changed the
>> > $wgCapitalLinks setting for you, but it's easy to test: Comment the line
>> > including the extension and check if it now works.
>> >