Awesome!
I don't know. As far I remember, this issue was reported once and I thought to have read the solution was to update XenMediaGallery. As I wrote it again in the update, since it's a paid addon and don't have access to it, the issue would have to be reported to the developer. If the issue is confirmed to come from my addon, its source code is on Github and any pull request can be made.Is the 2.5.0 version fix the issue in comment loading with Xenmediagallery add-on?
Thanks!
You will have to ask this question in the Tapatalk thread. But since it seems they have coded their own Bb Code formatter, they can easily modify it to strip all Bb Codes but the ones they need (probably bold, italic, underline, list, etc.). You will find two examples of Bb Codes formatters here, so feel free to share it with the Tapaltak developers.Is there a way to avoid the bbcode rendering this way in tapatalk that I'm unaware of?
Many thanks,
Nick
View attachment 85254
As told my pm, read the FAQ and start by its first paragraph. If you do have given some usergroups mce permissions, then check if you didn't create some custom configs in the BBM - Buttons Manager Options (by viewname, controller action, etc).Pls help me active it, it's don't work with my board !
Works great!@Xon
Thanks. It was just because my xen/mce framework was calling the getForm function where as the editor was not yet initialized. A few updates before, I've made this function global to make the code cleaner, but it still has to be called after the editor is ready (which is logical). So, check this commit.
Since it's a minor modification, I don't publish it yet here. I'm waiting for more feedbacks.
Ah, I thought so but wasn't sure.P.S: the autosave Interval & Retention params are for the MCE draft plugin, not for the XenForo draft method.
If you don't check the first paragraph of the FAQ and don't give some usergroups the permission to use MCE, there's nothing I can do for you.my config is here
Sadly still buggy. Some more testing discovered the following:Since it's a minor modification, I don't publish it yet here. I'm waiting for more feedbacks.
This bug is new, it must come from the new event (and its related function => modifies the dom) that has been added in the jquery serialize function. I will look at it tonight.Sadly still buggy. Some more testing discovered the following:
When the periodic "Draft Saved" occurs, the marker (or any text selection) is lost and it interrupts the user's writing by forcing them to re-find where they where writing.
/js/sedo/tinyquattro/tinymce/tinymce.min.js?_v=bccd8a22
/js/sedo/tinyquattro/tinymce/langs/xen.js
/js/sedo/tinyquattro/tinymce/themes/modern/theme.min.js
/js/sedo/tinyquattro/tinymce/plugins/xenforo/plugin.min.js
...
We use essential cookies to make this site work, and optional cookies to enhance your experience.