Using on Mediawiki 1.30. It logs views just fine however it doesn't log any edits.
Extension talk:Access Log
has anyone tried it on the latest release of 1.31
When installing 1.15-1.20 on Mediawiki 1.24.2 get a database error after installing and starting mediawiki (after IISreset).
Isn't there a newer version available or has someone experience with running on a newer MediaWiki?
The update op the database didn't give errors, looks good.
I am afraid that this extension is unmaintained and marked it as such. You could try to get in touch with the original authors directly.
Support for MW beyond 1.20?
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?).
in MW 1.28 purge log does not delete old entries
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??
AccessLog Warning when creating class in extension PageForms
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?
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.
My pleasure By the way, the name Tenbergen sounds dutch ^_^
Fatal error: Call to undefined method SpecialAccessLog
Modify /extensions/UMEduWiki/AccessLog/AccessLog.body.php (use Notepad++ or vim to prevent BOM) and on line 185 change GetLang to GetLanguage
My MediaWiki is v1.24alpha, but after configuring LocalSetting.php and
php update.php, I still getting the error when I access the page
Fatal error: Call to undefined method SpecialAccessLog::getLang() in /home/sunjizu/www/njuscda/mediawiki/extensions/UMEduWiki/AccessLog/AccessLog.body.php on line 185
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
Can confirm this worked for me on 1.26.1, PHP 5.4.16
Special:AccessLog return black page.
After making the change in line 185 from GetLang to GetLanguage everything started working.
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.
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?
- 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.
That worked for me on MW 1.25.2. Thanks!
PHP Parse / Fatal Errors MWDebug.php & GlobalFunctions.php
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!
How to get a .csv or similar dump
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.
Specify a limit to avoid huge databases...
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.
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.