1.9.x: mysql error: tikilog iattempts to nsert new actions in tiki_logs as logId=0, on mysql 4.0.x
Using 1.9.7 or 1.9.cvs from mid july 2007, and mysql 4.0.x
When clearing cache through "Admin > System Admin", for instance (tiki-admin_system.php?do=templates_c), I hit a warning mysql error:
Warning: mysql error: Duplicate entry '0' for key 1 in query:
insert into `tiki_logs` (`logtype`,`logmessage`,`loguser`,`logip`,`logclient`,`logtime`) values (?,?,?,?,?,?)
in /home/virtual/site21/fst/var/www/html/tikiwiki/lib/tikidblib.php on line 134
Looking at tikilog table in tiki db, I see:
^0 system erased templates_c content Xavi 22.214.171.124 Mozilla/5.0 (Windows; U; Windows NT 5.0; ca; rv:1.... 1186492878^
When I delete this record from the db, then Tiki can delete templates once (through "Admin > System Admin"), but if I attempt to do it a second time, I get the same mysql error message.
It looks as if those actions are not saved with the right logId number, but to logId=0
This happens to one of the tikis I admin at:
action log + contribution: admin should be able to edit contributors also, besides contribution type
Using tiki 2.1., action log + contribution feature.
Admin cannot re-set the contributors to a wiki edition, for instance.
Admin can re-set the contribution type, but not change the co-authors, and this is needed (in educational scenarios, students select no mates by mistake, and then, there is no way for the admin to re-set the author or co-autors).
|Action log broken: wiki page editions not shown (and detecting & banning spammers much harder)||tracker item|
Action log error and no results
At the MyTiki Action Log page (a URL like tiki-admin_actionlog.php?selectedUsers%5B0%5D=admin), this message displays a number of times at the top of the page:
"Deprecated: Assigning the return value of new by reference is deprecated in ...\tiki-admin_actionlog.php on line 392"
And no results display. This is in trunk r22552, but has probably been like this for quite a while.
|Action log form broken in doc.t.o (fivealive theme)||tracker item|
|Action log: Filters not localized||tracker item|
|Activity stream can't be chosen in PivotTable Plugin Edit UI||tracker item|
|Activity Stream doesn't display created or modified wiki pages||tracker item|
Add help link to tiki-admin_actionlog.php
The tiki-admin_actionlog.php page does not have a help icon that links to docs.
Add IP to syslog and/or action log when anons (at least) add content (for spam protection)
Add ip to syslog and/or action log, so that when anons (at least) are allowed to add content and it's spam (robots seem to be able to post with our current antibot captcha), there is way to identify the ip of the spammer.
So far, antibot captcha is added (in trunk, at least) to:
* wiki edit
* wiki page comments
* forum posts
* tracker item comments
* calendar items
* newsletter subscription
The action of adding content on those features should be logged in syslog and/or action log and IP recorded.
All preferences changes in logs
When we have many admins on a site, it's hard to keep track of who changed what.
One admin may turn on a feature, and a second turns it off. This should be logged.
So when a change is done on tiki-admin.php, the old & new value should be available in the logs.
This will permit a "manual restore" after applying a profile.
Category changes in watch and logs
There is currently no history of changes to categories.
Since permissions can now be restricted by categories, it is more & more important to know when an object is changed from one category to another.
Therefore, we need this info to be logged in tiki-syslog.php and to be added to the watch item feature.
Reminder: categories can be assigned in tiki-admin_categories.php but also when editing a wiki page.
|DB error: Column 'commentDate' in where clause is ambiguous||tracker item|
|Display Realname instead of login at ActionLog feature||tracker item|
|emails appended to tiki-syslog.php data||tracker item|
Empty screen after select date range in action log and pressing report
Empty screen after select date range in __Admin/Action log__ and pressing __report__. Logging on __Action Log__ settings page set up correctly. I have tried different data ranges and selecting different users and groups and it combination. The result the same. Pressing __export__ instead __report__ also produces empty screen.
|Expose Action log data to the pivottable plugin||tracker item|
|Getting the users IP when Tiki is behind a reverse proxy||tracker item|
Tiki-Log sort by ID broken
in debug mode (eg. when debugging ldap logins) many log entries are created at the same time so sorting by time is not sufficient to get the entries in their real order. Sorting by ID is better then.
Unfortunately sorting by ID leads to an unexpected result.
Looking at the code the problem can be fixed easily: The problem is that two tables are being joined (actionlog and actionlog_conf) and sorting by ID leads to sorting by actionlog_conf.id instead of actionlog.actionID.
Both needs to be fixed - in the SQL query the table for sorting must be added in the sort statement, in the template the columnname must be changed from Id to ActionId.
Tiki logs sort by Id or Message not working
When attempting to sort the Tiki logs by either Id or Message, the lines do not sort as expected. The actual order appears to be random, regardless of the requested sort direction (ASC or DESC.)
Incorrect logs truncate before inserting to database
It happens, when multibyte strings is recording to database.
Function "substr" work incorrect with multibytes string.
LDAP debugging causes error?
Windows Server 2008 64bit
Apache x64 2.2.11
PHP x64 5.2.5 (lib/smarty/libs/internals/core.is_secure.php patched to make it work)
LDAP authentication against AD does work once configured properly
Debugging the configuration was hard because turning on logging caused errors!
When logging is off, all is well. When logging is on and line 346 of lib/auth/ldap.php is commented out, all is well.
It seems that when logging is active, "$filter->asString()" on that line causes an error on our system. The same call is made on line 262 with a simpler filter and works OK.
Perhaps when checking groups, asString is returning too much for the logging system to handle?
|Login popup area is outside the screen on Ipad||tracker item|
|Login with Facebook appears when Social Networks Disabled||tracker item|
Module last action lists tiki-index.php after upgrade to 2.4
After upgrading from 1.9.11 to 2.4 the links in last action log are all linking to tiki-index.php.
In the old system everything is working fine.
|Most PHP errors caught by custom error handler not logged||tracker item|
|Pivottable of activitystream data: offer aggregation of modification date in weeks, months, etc||tracker item|
|Wrong user logged in Admin Logs||tracker item|
|Record Calendar-related actions at the Action log||tracker item|
tiki-syslog.php has no browser title
Bugs & Wish list
|tiki-syslog.php should be sorted with sort_mode=actionid_desc by default||tracker item|
|TRIM make backup and php console.php database:backup -> Community recipe for protection against data inconsistency in backups (especially for large projects)||tracker item|
|URL Rewriting Revamp: adding to Tiki log or error log so we catch them all through usage||tracker item|
User creation & deletion in logs
So we know which admin created a login...
We currently have a log entry when a user is assigned to a group, but not when he is unassigned.
Also, we have:
unassigned perm tiki_p_broadcast from group admin
assigned perm tiki_p_broadcast from group admin
Maybe adding failed login attempts would be good too...
Version history for trackers
((doc:Trackers)) are powerful. But there is no built-in version history like the wiki pages and the spreadsheet. A workaround is to watch the tracker and have the history in your inbox. You can also permit users to comment the tracker item instead of editing it.
A real history, accessible via the interface would be nice to have. Please see SourceForge trackers for an example.
Adding a field "Edit Summary" would be useful for this history.
Low-hanging fruit solution is to copy the diffs (that we already send by email but should be improved: [wish1982|Trackers :: email notifications of changes :: more emphasis on changes.]) to a new "history" tab.
More work would be an interface to revert to a previous value, which could be nice-to-have but too complex.
[wish953|Tracker field type: wiki page]
WikiBlame and WikiTrust
Please see ((WikiBlame)) and ((WikiTrust))
In the italian version of Tikiwiki 3.3 near login boxes the link "I forgot the password" is "Ho dimanticato la password". The correct translation is "Ho dimenticato la password".
The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.
Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.
Accessibility (WAI & 508)
Articles & Submissions
Contacts Address book
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Draw -superseded by Diagram
Friendship Network (Community)
i18n (Multilingual, l10n, Babelfish)
Kaltura video management
Logs (system & action)
Lost edit protection
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Performance Speed / Load / Compression / Cache
Search engine optimization (SEO)
Spam protection (Anti-bot CATPCHA)
Staging and Approval
Syntax Highlighter (Codemirror)
Tell a Friend
Terms and Conditions
Webmail and Groupmail
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives