rove that situation either. I maintain sites and
APIs that others call, and deprecating old code is both necessary and
trouble-inducing. Just... venting some frustration here.
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
On Mon, Jul 4, 2022 at 12:22 PM Benjamin Lees wr
mething to do with DefaultSettings.php being included
twice...?
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
On Mon, Jul 4, 2022 at 2:07 AM Benjamin Lees wrote:
> Pretty strange, since the error in question literally checks
> "$wgBaseDirectory !== MW_
here in my LocalSettings.php, so I
don't see why it would be generating this error. (Note that all of the
files in the stack trace are MediaWiki internal files.)
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
On Sun, Jul 3, 2022 at 6:44 PM Jeffrey Walton wrote
suggestion; that gives me the
"$wgBaseDirectory must not be modified in settings files!" error. Neither
option seems to work for me.
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
On Sun, Jul 3, 2022 at 2:57 PM Benjamin Lees wrote:
> Hi Jeffrey, I think this
the years. I've scanned through
the file multiple times now and I can't find anything to looks out of place.
Any help would be appreciated.
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
___
MediaWiki-l
cript
Jeffrey T. Darlington
General Protection Fault, The Comic Strip
https://www.gpf-comics.com/
On Sun, Apr 10, 2022 at 12:40 AM Toshi Esumi wrote:
>
> On 4/8/22 16:55, Toshi Esumi wrote:
>
>
> On 4/8/22 00:51, Andre Klapper wrote:
>
> [a50bfc1261fc29c06a343aec] 2022-04-08 05
ne 535] in
/var/www/gpf/mediawiki-1.36.0/includes/debug/MWDebug.php on line 376
Hope this helps...
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
___
MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
List information:
htt
orts from them all the time. I
have a few users of my subscription service and forum with Hotmail,
Outlook, and Yahoo! addresses. There are other services out there as
well that are pretty good with DMARC, but there are still a lot of mail
servers that haven't implemented any of these techno
low-end box
for $10 USD/month. There are probably other even cheaper options out
there, but I can vouch for Linode being *very* reliable.
- --
Jeffrey T. Darlington
General Protection Fault
http://www.gpf-comics.com/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCAAGBQJVpbyJ
not sure if it's my configuration (I didn't
explicitly set it this way), but if I try to force it to go back to
HTTP, it "forgets" that I'm logged in, so I'm assuming it's setting the
login cookie as HTTPS-only.
Hope this helps.
- --
Jeffrey T. Darlington
General Pro
de.
https://www.mediawiki.org/wiki/Manual:RebuildLocalisationCache.php
Hope this helps...
- --
Jeffrey T. Darlington
General Protection Fault
http://www.gpf-comics.com/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Th
reviously stated, as long as the wiki is publicly
accessible you can't stop scraping of the final rendered HTML. These
just block API access and the built-in export mechanism.
Hope that helps...
- --
Jeffrey T. Darlington
General Protection Fault
http://www.gpf-comics.com/
-BE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/3/2012 10:41 AM, Stefan Widmann wrote:
> if you are using the ParserFunctions Extension (I guess so), try to comment
> it out in LocalSettings.php.
> Do you still get this trace? If not try to uncomment it. I know this sounds
> strange but that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/7/2012 5:22 PM, Platonides wrote:
> What's your custom extension? Does MediaWiki 1.20 work if you disable
> it? In what language is your wiki?
It's a modified version of the CheckSpambots extension that hooks into
my custom spam block list syste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just tried upgrading from 1.19.2 to 1.20.0. I followed the standard
procedure of backing up my DB, extracting the tarball to a new
directory, copying over my images, LocalSettings.php, and one custom
extension, and running maintenance/upgrade.php.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After that, check that your PHP session directory is writable by the
user under which your web server daemon is running. I use a
non-standard user/group combination for Apache on my server and end up
locking myself out of my MediaWiki every time I upg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2011 5:50 PM, Platonides wrote:
> Not sure if it's an error of firefox (I can't find it), but I'm getting
> the login page marked as loading content insecurely on the first load
> (disappears if I reload).
Were ads displayed on the page? My
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2011 12:18 PM, Platonides wrote:
> I was thinking that instead of the languages/messages/MessagesEn.php
> shipped with MediaWiki 1.18 you could have there a copy of an older release.
> The md5 of the file is:
>> 59498d33f47acb0a25cb1eec986fad1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/4/2011 3:58 PM, Platonides wrote:
> That's strange. Do you have the language files up to date?
I have no idea. I'm starting from a clean yet slightly tweaked copy of
the 1.18.0 code (I have a custom skin derived from MonoBook), and I made
sure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know you guys are probably getting tired of seeing my name appear on
this list by now, but I've run into yet another 1.18.0 upgrade issue.
After lots of debugging over at the Bugzilla site, I finally found out
my custom skin was the cause of most of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
mhershber...@wikimedia.org wrote:
>> Have you filed a bug for this?
>
>I filed one for you now: https://bugzilla.wikimedia.org/32762
Thanks for filing the bug. I hadn't done so mostly because I didn't know about
the Bugzilla site. (That's why I joi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/29/2011 5:08 PM, Olivier Beaton wrote:
> It should be noted that the MediaWiki docs recommend doing the following
> for an upgrade (after your backups):
>
> tar xvzf mediawiki-1.18.0.tar.gz -C /path/to/your/wiki/ --strip-components=1
>
> https:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/29/2011 12:31 PM, Daniel Friesen wrote:
> Sounds like you upgraded MediaWiki by extracting 1.18 on top of 1.17
> instead of extracting 1.18 to a new directory then moving the config and
> other stuff to the new directory. And have an old Star
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/29/2011 11:58 AM, Gordon Joly wrote:
> *Fatal error*: Cannot redeclare wfprofilein() (previously declared in
> //public_html/includes/profiler/Profiler.php:14) in
> */x/public_html/includes/ProfilerStub.php* on line *25*
I'm gettin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
This morning I downloaded MediaWiki 1.18.0 and attempted to upgrade my
existing wiki from version 1.17.0. Unfortunately,
maintenance/update.php fails when it attempts to create the table
"uploadstash" with a MySQL error:
1064: You have an err
25 matches
Mail list logo
