Hi Tieku, sorry, I got half way through replying to this at the start of July, and then got distracted. Can you please test this in v24.0.00? I believe you are seeing the results of a bug that was fixed with the following MySQL change:
UPDATE gibbonSetting SET value=‘br[style|class],strong[style|class],b[style|class],em[style|class],span[style|class],p[style|class],address[style|class],pre[style|class],h1[style|class],h2[style|class],h3[style|class],h4[style|class],h5[style|class],h6[style|class],table[style|class],thead[style|class],tbody[style|class],tfoot[style|class],tr[style|class],td[style|class|colspan|rowspan],ol[style|class],ul[style|class],li[style|class],blockquote[style|class],a[style|class|target|href],img[style|class|src|width|height],video[style|class],source[style|class],hr[style|class],iframe[style|class|width|height|src|frameborder|allowfullscreen],embed[style|class],div[style|class],sup[style|class],sub[style|class],code[style|class],details[style|class],summary[style|class],pagebreak,columnbreak’ WHERE name=‘allowableHTML’ AND scope=‘System’;
You could always try and run this command on your v23.0.02 database to see if that solves the issue.
Cheers,
Ross