Edithow can I do that?
siropu_shoutbox_shout_list_macros
template and replace @ with a FA icon (line 9).ThanksEditsiropu_shoutbox_shout_list_macros
template and replace @ with a FA icon (line 9).
Editsiropu_shoutbox_shout_list_macros
template and replace @ with a FA icon (line 9).
I agree,You can change the @ button that is used before the username to tag someone but can't change the @ in the post when a user is tagged because @ is required for tagging.
I just had one small question: would it be possible to modify the shoutbox manual directly on the forum instead of going through the ACP?I assume you are using CSS to define the FA icon for that class? It's ok.
Added the option to edit shoutbox header and footer admin options from the front-end with the ability to use the BB code editor.
Added error log for open AI API to troubleshoot issues.
Fixed an issue with the /ai command response where the user BB code would not work when bb code is disabled.
I still think if your using a predefined existing account for the AI it should use the avatar and markup so it keeps everything looking uniform.Siropu updated Shoutbox by Siropu with a new update entry:
Improvements & Bug Fixes
Read the rest of this update entry...
Good evening Siropu,Siropu updated Shoutbox by Siropu with a new update entry:
Improvements & Bug Fixes
Read the rest of this update entry...
What does it say there?More error details can be viewed in the browser console.
The problem is that there are no errors in it... so I don't understand...What does it say there?
Added the ability to report shouts and view them in the archive for easy moderation (requires the new Report shouts user permission).
Added the ability to use a predefined user account for ChatGPT responses.
Added the @ before the ChatGPT bot name for easy /ai command insert.
Thank you for the update Siropu,Siropu updated Shoutbox by Siropu with a new update entry:
New feature & Improvements
Read the rest of this update entry...
Since it is an admin option, it is available to admins only.Is it possible to put header editing for some user groups under permissions?
We use essential cookies to make this site work, and optional cookies to enhance your experience.