You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just discovered that is IS actually possible to edit the default content, BUT really you have to know that and where to click for editing the content. In that screenshot i have marked the very tiny area with a custom border for the subject.
You only see the span without any indication of its size. I would expect a normal text input. Why is it that complicated?
I first thought, i have to add multiple language templates and only then can mark one as the default, but no .. that interface should be optimised!
I will add CSS to my admin to at least display a border for ".CodeMirror pre".
But this should be fixed in some future version as this admin interface is not usable that way!
The text was updated successfully, but these errors were encountered:
I would remove all the pre stuff and just display the normal admin fields, but why was that overlay added in the first place?
It might have been a good idea, but i dont get it yet.
Okay, after playing around with it a bit more i see that the current elements display code highlights. Thats nice, but still the borders are missing to actually know where to click to start entering text.
Hi
I just discovered that is IS actually possible to edit the default content, BUT really you have to know that and where to click for editing the content. In that screenshot i have marked the very tiny area with a custom border for the subject.
You only see the span without any indication of its size. I would expect a normal text input. Why is it that complicated?
I first thought, i have to add multiple language templates and only then can mark one as the default, but no .. that interface should be optimised!
I will add CSS to my admin to at least display a border for ".CodeMirror pre".
But this should be fixed in some future version as this admin interface is not usable that way!
The text was updated successfully, but these errors were encountered: