Love this package, and I am mainly using this for identifying member accounts which are locked, and unlocking them.
Using Umbraco v7.5.14 and v 0.9.12 of the package.
I have encountered one problem though - that I seem to need to rebuild the Examine index manually each time before locked accounts show with the red padlock in the Manage tab or when filtered for Locked Accounts only.
If you click on a locked member record (which shows with the green icon), it does correctly show that the member is locked.
I'm hoping to enable content editors to take on this role, so I'd like them to be able to use the Members / Manage tab without needing to give them access to the Developer tab or any rights to the indexing etc. But I can't do that if they can't search properly on which members are locked.
Perhaps there's something in my Examine settings that isn't right - perhaps the index is not refreshing automatically or sufficiently frequently - but I'm no expert on that!
Any thoughts on how to fix this would be appreciated!
Locked status not shown correctly
Hi
Love this package, and I am mainly using this for identifying member accounts which are locked, and unlocking them.
Using Umbraco v7.5.14 and v 0.9.12 of the package.
I have encountered one problem though - that I seem to need to rebuild the Examine index manually each time before locked accounts show with the red padlock in the Manage tab or when filtered for Locked Accounts only.
If you click on a locked member record (which shows with the green icon), it does correctly show that the member is locked.
I'm hoping to enable content editors to take on this role, so I'd like them to be able to use the Members / Manage tab without needing to give them access to the Developer tab or any rights to the indexing etc. But I can't do that if they can't search properly on which members are locked.
Perhaps there's something in my Examine settings that isn't right - perhaps the index is not refreshing automatically or sufficiently frequently - but I'm no expert on that!
Any thoughts on how to fix this would be appreciated!
Thanks, Allan
Any thoughts on this anyone please? I still have the same issue in 7.5.14 sites and also in 7.10.4 sites, with package version 1.2.0 in both cases.
Thanks Allan
is working on a reply...