Conversation
BentiGorlich
commented
Feb 25, 2026
BentiGorlich
commented
- when a moderator purges content this should also be reflected in the modlog -> add new modlog types with a title property, as the entity is purged, so no longer referencable
- when a moderator purges content this should also be reflected in the modlog -> add new modlog types with a title property, as the entity is purged, so no longer referencable
BentiGorlich
added
enhancement
| { | ||
| $this->addSql('ALTER TABLE magazine_log ADD author_id INT DEFAULT NULL'); | ||
| $this->addSql('ALTER TABLE magazine_log ADD title VARCHAR(255) DEFAULT NULL'); | ||
| $this->addSql('ALTER TABLE magazine_log ADD CONSTRAINT FK_87D3D4C5F675F31B FOREIGN KEY (author_id) REFERENCES "user" (id) ON DELETE CASCADE NOT DEFERRABLE INITIALLY IMMEDIATE'); |
There was a problem hiding this comment.
please name the constraint and index with a meaningful name
There was a problem hiding this comment.
These are the doctrine generated ones. Afaik if I rename them to something else, doctrine will try to regenerate them in every diff... I can try if that it true
|
I see a potential issue with persisting the title: purging is a drastic action, so there must be reasons with it. What if the mod purged content because there was illegal content (potentially also in the title). Then it would continue existing on the server and UI which could get the server admin into legal trouble. |
Yes in theory that is a problem. I could not think of a reason why you would then delete a post, but not the user. If the user was deleted the modlog would also be deleted. Maybe this has to be postponed until the moderate actions have a useful page of their own so that we can add a checkbox there whether the modlog has to be hidden (not created) |
Yea; we also have the mod-action federation issue. So we need to plan some restructuring in general. |
2 participants
