-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with field type "wysihtml" #224
Comments
@sachatrauwaen Do you think this is something that might be able to be fixed quickly? Do you need one of us to try and fix it? |
Is it An upgraded Open Content? OR a new install? I believe the WYSIHTML field is not supported anylonger. Check https://opencontent.readme.io/docs/migrating-existing-templates-to-builder-v2 |
Also… if you use the fields buttonText and buttonLink… take a look at the field ‘link’. It gives you the possebility to choose what kind of link it is and a text field. |
@b-creative The button link thing was just an example. We're really using that kind of value elsewhere. |
@b-creative is right, in the new V2 editor WYSIHTML is not supported any more.
It should work if you are still using the old form editor. |
I am using Bootstrap 5 for my theme. Any alternative within opencontent with the same possibilities that it provided using WYSIHTML type fields? |
This folder is removed by error |
@sachatrauwaen Thank you! |
Or you could switch to the CkEditor.. |
Do you need anything else for this @ArielBlanco1990 ? |
@WillStrohl No, I think everything is ready on my end. They just have to keep this in mind for future releases. |
Describe the bug
Problem when trying to edit the module when I have a field of type "wysihtml". (This worked correctly until OpenContent version 04.07.00)
Software Versions
DNN: 09.11.02
OpenContent: 05.00.06
Expected Result
The edit window should be displayed to update the values.
Actual Result
When trying to edit the module when I have a field of type "wysihtml". The editing window does not show any fields and the error can be seen in the console.
CC; @WillStrohl
The text was updated successfully, but these errors were encountered: