we need to filter members on a date (last_login_time), to do this we extended the Plone members search form (by extending the IMemberSearchSchema) to add a schema.Date, this works fine and a calendar appears.
But then, this is not really handled by plone.app.users (will need to fix extractCriteriaFromRequest there) neither by ZODBMutablePropertyProvider.testMemberData.
What we need it set a date and then check if user last login is between now and this date.
It actually work by overriding things but we would like to put this back to Products.PlonePAS and plone.app.users to avoid 2 monkeypatches...
Did anybody already thought about this? Would it be acceptable to propose an implementation like for portal_catalog and being able to define a range of date and a "behavior" min/max/minmax?
Hi everybody,
we need to filter members on a date (last_login_time), to do this we extended the Plone members search form (by extending the IMemberSearchSchema) to add a schema.Date, this works fine and a calendar appears.
But then, this is not really handled by plone.app.users (will need to fix extractCriteriaFromRequest there) neither by ZODBMutablePropertyProvider.testMemberData.
What we need it set a date and then check if user last login is between now and this date.
It actually work by overriding things but we would like to put this back to Products.PlonePAS and plone.app.users to avoid 2 monkeypatches...
Did anybody already thought about this? Would it be acceptable to propose an implementation like for portal_catalog and being able to define a range of date and a "behavior" min/max/minmax?
Thank you for feedback, Gauthier