-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I figured out the solution to my problem
TRUNCATE TABLE objectcache;
It would be nice for MediaWiki to truncate the table for you if you
change $wgCachePages from it's default to FALSE. Or anyway, just have
$wgCachePages be false by default.
my $0.02
Some of my questions still stand, why do the preferences in the user
table effect wether or not to use the cache, I wonder??
Thanks,
On Mar 16, 2006, at 12:17 PM, Jon Belanger wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
First time posting to the list, so sorry if I'm out of touch a bit. I
did search through the documentation using the obvious keywords.
I'll lay out my problem...
I had MediaWiki at
https://hostname.domain.edu/user/wiki
the LocalSettings.php reflected this path...
I then changed to
https://hostname.domain.edu/wiki
and changed LocalSettings.php to reflect this
Logging in anonymously the links in the wiki reflect the updated path,
but when I log in as a pre-existing user, they reflect the old path.
This is odd, and I suspected caching immediately. If I make any change
to a single page the new URL goes into the links for that page as it
should.
I did a little more exploring though, and found out a few odd things.
If I deleted the pre-existing user and simply logged in again as that
user (I'm using the LdapAuthentication.php module, so no need to
manually recreate, I can just log in with LDAP credentials and it'll
build the record in wiki.[wiki]_user for me.
When the LDAP user is created in the DB the user doesn't have all of
the "extra" preference values. In this state all the pages reflect the
proper URL in the links when logged in as the newly re-created user.
However, if I make a change to the preferences of the newly re-created
user (e.g. update real name, but could be any preference) then the URL
in all of the links break once more. But, like I said, If I page a
change to single page, that page works, but the rest of the pages will
not.
So my questions are as follows:
#1 Why is caching on when I've set $wgCachePages = false
#2 Why the odd behavior with the "extra" preferences. Why does it work
without then, and why does it break with then. More to the point, why
does this effect server side caching?
Thanks,
Jon Belanger
Computer Systems Specialist
Departments of Chemistry, Biochemistry and Molecular Biology
University of Massachusetts Amherst
-----BEGIN PGP SIGNATURE-----
iD8DBQFEGZ2okcuAthB9NCYRAmSYAJ0Z5m0NVk6IUj9OugzwjfRWNqxVMQCfeTGY
tuwGzFqucGSOa+DOc3h0MAU=
=CWx1
-----END PGP SIGNATURE-----
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Jon Belanger
Computer Systems Specialist
Departments of Chemistry, Biochemistry and Molecular Biology
University of Massachusetts Amherst
-----BEGIN PGP SIGNATURE-----
iD8DBQFEGakAkcuAthB9NCYRAutPAJwPq+O/xP+JSGCqk41exqWO0gz6/QCgg0f8
iU4NfQSGVRORdI0y5r0zhHQ=
=86tV
-----END PGP SIGNATURE-----