Package: collective.login-monitor
Save anylogin operationdone in your Plone site to an external database and provide a Plone interface
for query the database.Table of contentsIntroductionHow to useMultiple sitesInstallation and configurationCreditsAuthorsChangelog1.0.0 (2022-07-15)0.4 (2015-08-21)0.3.1 (2014-11-06)0.3 (2014-10-28)0.2 (2013-04-18)0.1 (unreleased)IntroductionThis Plone add-on is based onz3c.saconfigandSQLAlchemy, and can’t provide any new feature to Plone
without a proper configuration.Keep reading for installation and configuration guide.How to useAfter the installation, any login done in your Plone will save to an external database an entry that store:user ida timestampThen a new configuration panel can bhe found in the site configuration: “Monitor user logins”.From this view you can query the database previously populated:You must limit the search inside a rande of dates, and optionally limiting users to members of a group.
Results of the table displayed can be export to a CSV file.Multiple sitesIf your buildout hosts multiple Plone sites, all of them will store data in the database keeping same username
on different sites separated.Installation and configurationYou must configure an access to an external DBMS. The name of the engine used must beplone_logins.Follow an example based onsqlite(not advised for production environment).Addcollective.login_monitorto your buildout, then provide a SQLAlchemy connection string:[buildout]
...

[instance]
...
eggs=
   ...
   collective.login_monitor

zcml-additional =
    ...
    <configure xmlns="http://namespaces.zope.org/zope"
              xmlns:db="http://namespaces.zope.org/db">
       <include package="z3c.saconfig" file="meta.zcml" />
       <db:engine name="plone_logins"
                  url="sqlite:///${buildout:directory}/var/filestorage/plone_logins.db"
                  setup="collective.login_monitor.prepare_model.prepare"
                  />
       <db:session name="plone_logins" engine="plone_logins" />
   </configure>CreditsDeveloped with the support of:Azienda USL FerraraS. Anna Hospital, FerraraAll of them supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.Changelog1.0.0 (2022-07-15)major refactoring for python 3.8 and plone 5.2.
[reflab]0.4 (2015-08-21)Added a contact form, for sending ad email message to all users found by the search
[keul]Added an (hidden) export to JSON feature. 3rd party add-ons can use this for performing
operation of search results
[keul]Search view is now “callable” with custom parameters
[keul]Added a negative search filter, for looking for users who didn’t logged in
in the given range.Please notethat users must still be indexed by the table (a user who never logged in
will not be found)
[keul]Added search filter by user id
[keul]Added new information about last login date of the user
[keul]Fixed errors in foreign key definition on schema models
[keul]0.3.1 (2014-11-06)Fixed date error in that will be raised in some cases
[keul]React to a wider range of problems when database connection
is not working
[keul]0.3 (2014-10-28)Dropped Plone 3 compatibilityAdd Full Name and E-mail columns to the search results and CSV output.
[davidjb]Fix selected Group logic on search form.
[davidjb]Clarify description for group selection field.
[davidjb]Minor grammar update for column headings on search page and export.
[davidjb]Change icon URLs to use PNG format rather than deprecated GIF images.
[davidjb]Add exception handling in the event, if no db is configured [cekk]0.2 (2013-04-18)First public releaseold code totally refactored (removedsqldictfor a pureSQLAlchemyapproach)
[keul]i18n support
[keul]0.1 (unreleased)Initial release