-
I might be very far off, but it reminded me of the iframe problem and that the work around for it was to inject a js script in studio/designer, seemingly reactivating iframe capabilities within post or editor for that sake. Iframes worked well in studio/blocks/raw but failed when used in post/editor... or there was a switch almost like activate or deactivate a particular setting within studio...
-
However, the error I encountered with the HTML button code occurred on my test site running version 14.0.0. I translated UNA 14 into Romanian and added the Terms and Conditions via Studio to prepare the site for the migration to version 14. That's when I noticed this issue. Until I solve the migration, I hope to understand how to solve this problem in the editor.
-
Why 12, in recent days.. I was involved with a similar project where we had to migrate from ossn to unacms.. but we migrate straight to the current version we were using... The only challenge we had or consideration was the fact that unacms uses SHA-1 password encryption whereas ossn used MD5 hashing. and we wanted to move the users across. We used a script, but had to in the end let the users be directed to password reset to avoid further complication, other than that, go for RC5.. I think the patches are released and fixed most of the problems... and might just fix the one you currently have.
-
I tried to migrate directly to recent versions but we lose content due to incompatibility, so now I'm testing with version 12.0.0 and then I will update to higher versions if works. migrating to higher versions I lost the avatars and image headers
Comment to 'Issues with Code Formatting in the Forum Editor'
