Thanks flop25, that did stop errors from showing at the top of the page.
It looks like the "Undefined index: username" error is from when autologin in used. If autologin is used the User Info Tracking log shows "User ID", but "User Name" is blank.
Offline
Charles2012 you should really REALLY clean your plugin
you left many useless stuff from Skeleton which induces errors like
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'skeleton_ws_add_methods' was given in /*********/include/functions_plugins.inc.php on line 161
as statted somewhere in the plugin you MUSN'T blindly copy-paste code from Skeleton, it's only a reference for common coding paterns of Piwigo
Offline
Unfortunately the author doesn't answer to my mails for months. We should continue the plugin and clean up
Offline
I feel awkward being 'a taker, not a giver' again, but is someone able to make this plugin compatable with the latest version of Piwigo? Thanks.
Offline
That is one of the biggest problems with Piwigo. You never know if the plugins will work with a future version of Piwigo. When a new version of Piwigo comes out, you do not know which plugins will work with that version. You only can try, and if the plugin does not work with the new version, you are likely to be in trouble. And going back to the older version is not that easy.
If that behavior of Piwigo could be changed, they would keep their users in the future and Piwigo could be a big hit.
Offline
Piwigo tells you before the update what plugin is not compatible for the next big update ( 2.x )
For small update, it shouldn't happened since it's about security fix and bug fix.
what was your update?
The problem is also plugins are third party; I have and tried many cms and the same problem remains. The plugins makes the cms bugy, slower etc ...
Offline
OK, if it is true that Piwigo tells you before the update what plugin is not compatible for the next big update, i am sorry. We will see with the next update to 2.6 ?
Offline