Extension talk:Access Log

Jump to: navigation, search

About this board

No previous topics.

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL
118.92.37.136 (talkcontribs)

Access log says that its only supported on MW versions 1.15 to 1.20.

One server in the cloud I want to install this extension on is 1.21.1 (will it work ok?).

Thanks.

Reply to "Support for MW beyond 1.20?"

in MW 1.28 purge log does not delete old entries

1
Jackqbox (talkcontribs)

weird issue

purging old entries no errors generated, but nothing is deleted whenever $wgLanguageCode = "zh-tw";

This is caused whenever i have my chrome browser set to automatic translation to english

using the default chinese in my browser (zh-tw) it is deleting correctly

anyone encountered the same??

Reply to "in MW 1.28 purge log does not delete old entries"

AccessLog Warning when creating class in extension PageForms

4
Tenbergen (talkcontribs)

I have an old, working install of AccessLog. I recently installed Extension:Page_Forms; it essentially facilitates the editing of template calls in pages.

When I try to "generate a class" (which edits pages in template, forms and possibly property (semantic MW) namespaces), I get the following error: Warning: Missing argument 12 for accessLogEditAction() in /home/ccmdb/ccmdb.kuality.ca/extensions/UMEduWiki/AccessLog/AccessLog.php on line 104

The template gets generated, but the form does not. Does AccessLog fail on non-standard namespaces?

Jackqbox (talkcontribs)

just look here https://www.mediawiki.org/wiki/Manual_talk:Hooks/ArticleSaveComplete#PHP_Warning:_Missing_argument_12_in_extension_that_uses_ArticleSaveComplete

Tenbergen (talkcontribs)

That did the trick, thanks Jackqbox. The class generator in extension PageForms still doesn't actually generate a class, but at least this is no longer the reason.

Jackqbox (talkcontribs)

My pleasure By the way, the name Tenbergen sounds dutch ^_^

Reply to "AccessLog Warning when creating class in extension PageForms"

Fatal error: Call to undefined method SpecialAccessLog

3
Summary by Jkmartindale

Modify /extensions/UMEduWiki/AccessLog/AccessLog.body.php (use Notepad++ or vim to prevent BOM) and on line 185 change GetLang to GetLanguage

Sunjizu (talkcontribs)

My MediaWiki is v1.24alpha, but after configuring LocalSetting.php and php update.php, I still getting the error when I access the page Special:AccessLog

Fatal error: Call to undefined method SpecialAccessLog::getLang() in /home/sunjizu/www/njuscda/mediawiki/extensions/UMEduWiki/AccessLog/AccessLog.body.php on line 185
Adamlonsdale (talkcontribs)

You need to modify /mediawiki/extensions/UMEduWiki/AccessLog/AccessLog.body.php (use Notepad++ or vim to prevent BOM) and on line 185 change GetLang to GetLanguage - that will fix it

Chazbot7 (talkcontribs)

Can confirm this worked for me on 1.26.1, PHP 5.4.16

Special:AccessLog return black page.

3
Summary by Jkmartindale

After making the change in line 185 from GetLang to GetLanguage everything started working.

TDeeming (talkcontribs)

I am migrating my wiki from MW 1.19.1, PHP 5.3.8 and MySQL 5.5.16 to another server with MW 1.24.1, PHP 5.6.3 and MySQL 5.6.21. Previously I was using Access Log 1.02 and it worked great. I am now trying to get AccessLog 2.0 to work with a new installation of MW 1.24.1.

Access Log appears on the Special Page, however when I try to access the page... it is blank.

You help would be appreciated... as it is a very useful function.

Thanks,

TDeeming (talkcontribs)

I am now moving my contents from local to real virtual server 2012.

When I installed to new 1.24.2 (previously 1.24.1) I would get a DB Enquiry Error on every page... So I ran the update.php and that error went away.

However when I try to access the "AccessLog" I no longer get a blank page... but a

"Fatal error: Call to undefined method SpecialAccessLog::getLang() in D:\xampp\htdocs\wiki\extensions\UMEduWiki\AccessLog\AccessLog.body.php on line 185"

Is this tool dependent on another extension? Any ideas?

Update
Sorry I had looked at the "Fatal error: Call to undefined method SpecialAccessLog" but at the time I was getting a blank page... after making the change in line 185 from GetLang to GetLanguage everything started working.
Clifford.kasper (talkcontribs)

That worked for me on MW 1.25.2. Thanks!

PHP Parse / Fatal Errors MWDebug.php & GlobalFunctions.php

1
Alejanic (talkcontribs)

Please help, I noticed today that my wiki is suddenly completely white. I viewed the error logs and saw two errors that were breaking it (previously it was fine before this and I hadn't touched it) It was working for awhile then all of a sudden it goes white with these errors:

[19-Apr-2015 22:58:58 America/Chicago] PHP Parse error: syntax error, unexpected '|' in /wiki/includes/debug/MWDebug.php on line 341 [19-Apr-2015 22:58:58 America/Chicago] PHP Fatal error: Class 'MWDebug' not found in /wiki/includes/GlobalFunctions.php on line 981

I'm very novice when it comes to PHP, if anyone has any insight I would be greatly appreciative!

Reply to "PHP Parse / Fatal Errors MWDebug.php & GlobalFunctions.php"
Fustbariclation (talkcontribs)

I'm finding this a very useful extension, for all sorts of reasons. What I'd like to do is get the last month's worth of access log in a flat file so I can do my own analysis. I'm running on a hosted server, which times out if the access log program runs too long. I can get there by going through it 500 lines at a time, but it's quite a tedious solution.

I've looked at the database table:

tw_log_id tw_log_timestamp tw_log_user tw_log_username tw_log_namespace tw_log_title tw_log_action

Naturally, these keys are binary, pointing to the actual name, action and so forth, and the timestamps are encoded. I don't know enough SQL (I don't know any, to be more precise), to know how to set up a query to return what turns up in the access log.

So, I was just wondering, if there was a handy sql query lying about that I could use - if so, I'd be most grateful.

The other solution would be to mess about with the access log program - it might not be too difficult if all I did was to put in a sleep every hundred or so queries to stop the server stopping it, but I think that a SQL query would be a more sensible solution if I had it.

Any other suggestions gratefully received.

Reply to "How to get a .csv or similar dump"

Specify a limit to avoid huge databases...

2
195.101.137.127 (talkcontribs)

Great extension ! Is it possible to add an option to purge automatically entries older than X days or/and to limit the number of entries ?

Thx in advance.

M├ęgajoule

Robertpba (talkcontribs)

Thanks for your kind words. There is unfortunately not such an option. You need to go into the access log special page and use the purge option to manually purge logs older than a specified number of days. However, you are welcome to implement and contribute an automatic purge function.

Reply to "Specify a limit to avoid huge databases..."
217.91.162.122 (talkcontribs)

Hey Guys,

i have installed the extension successsfull, but i doesnt see a "AccessLog" Special-Page... if i manually access: wiki/special:acceslog the wiki means the site does not exist!

in apache errorlog is the following: PHP Parse error: syntax error, unexpected T_VAR, expecting ')' in /etc/mediawiki/LocalSettings.php

Any idea?

Robertba (talkcontribs)

First guess: an error in your LocalSettings.php file.

Ours looks like this (just the line that adds the AccessLog extension):

require_once( "$IP/extensions/TransWiki/AccessLog/AccessLog.php" );

Please check if yours looks similar, or post here what you have.

Reply to "PHP Parse error"
76.100.19.118 (talkcontribs)

I would like to see an option to filter by the specific page viewed. Sometimes this functionality is helpful in dealing with abuse directed towards specific topics.

76.100.19.118 (talkcontribs)

Yeah, I had insomnia and mountain dew tonight. Here's an updated version of AccessLog.body.php which implements both page filtering and filtering for anonymous (IP-only) users: I've tested the new patches and they seem to work as intended, but programming is not really my strong suit so I would advise double-checking the code I've cobbled together before using it on your own site.

76.100.19.118 (talkcontribs)

Sorry folks, one small bugfix -> remove the $ from the end of the LIKE expression on line 434.

Reply to "Filter by Page"