@Waindigo
Thank you for this Add-on, but there are some hardcoded phrases. Are you able to change them, please?
In your options for the conversation on moderator action there is no chance to translate:
Thanks for your support
- Conversation
- Alert
- None
Test Account,
Your post in the thread titled 2014: New Year's Resolutions has been deleted. Reason: Spam.
Amaury
Test Account,
Your post in the thread titled 2014: New Year's Resolutions has been deleted.
Reason: Spam.
Amaury
{to},
Your post in the thread titled {title} has been deleted. <br><br>{reason}
{from}
Test Account,
Your post in the thread titled 2014: New Year's Resolutions has been deleted. <br><br>Reason: Spam.
Amaury
Not all phrases support HTML. This phrase supports BB code, not HTML. Regular line breaks (not HTML ones) should be fine. Just like there are line breaks after {to} and before {from}.@Waindigo
I've been adjusting the phrases a bit to suit, but how can I get the reason on a separate line for soft-deleted threads and posts?
Currently, it's like this:
I want it to be like this:
I've tried adding line breaks to the phrase -- and phrases do support HTML -- but instead of line breaks, it just displayed the HTML.
HTML:{to}, Your post in the thread titled {title} has been deleted. <br><br>{reason} {from}
Result:
Thanks in advance!
Bug fixes:
- Options are now fully phrased, allowing for the entire add-on to be translated to other languages.
- Fixed bug that unable to perform moderation actions on threads with long titles. Conversation titles are now trimmed to make sure they don't exceed character limits.
- Errors when moderator cannot send conversation message to user are now silenced. Administrators should still check to ensure that moderators can send conversation messages to users if they want to...
Not all phrases support HTML. This phrase supports BB code, not HTML. Regular line breaks (not HTML ones) should be fine. Just like there are line breaks after {to} and before {from}.
Waindigo updated Conversations on Moderation Actions by Waindigo with a new update entry:
Version 1.0.5 released
Read the rest of this update entry...
Not silently, no...Did you silently fix the bug I mentioned above?![]()
- HTML entities are no longer escaped in phrases.
Not silently, no...
It is a global option at present.Can the Moderator choose whether or not an alert or conversation is generated? I think we'd want the option to do our thing "silently" in some cases.
We use essential cookies to make this site work, and optional cookies to enhance your experience.