after deleting a joomla-user akeeba engage throws a warning in front- and back-end #128
Replies: 1 comment
-
This is Joomla throwing the warning, not Akeeba Engage. There is a comment made by that user. Since that comment is not deleted, Akeeba Engage is asking Joomla to give it the information of the user ID which submitted the comment. Joomla cannot find the user and Joomla itself throws a warning which cannot be suppressed. Checking whether a user exists actually goes through the same code in Joomla itself which is throwing the warning. Therefore there is really nothing we can do on our end. You will have to delete the comment of this user yourself. Also note that normally you do not need to do that. As long as you have the “User – Akeeba Engage” plugin published and its Access set to Public it will automatically pseudonymize all comments the user made. Also note that this will ONLY work if whatever deletes the user goes through the standard Joomla User API class to delete the user as is the only correct way to do so in Joomla. If something goes and deletes something from the Pseudonymization means that the comment text is replaced with “Comment removed due to account deletion”, the comment is disassociated from the user ID and given a fake email (similar to |
Beta Was this translation helpful? Give feedback.
-
yesterday I deleted a joomla user in the back-end,
it was a temporary user (user-ID 615) that was member of the super-user group (w/ super-user-rights)
(this user did not create any akeeba engage comments)
After that, akeeba engage throws a visible warning in back-end and front-end,
(a warning that it cannot find this user-ID 615 anymore...)
--> see attachments
(Joomla! 3.10.3 / engage 2.0.5)
Beta Was this translation helpful? Give feedback.
All reactions