Edition de Communiqués

[tintin974]

Bonjour suite à la mise a jour, je n’arrive plus a creer ou editer un communiqué

les champs acroche et contenu sont inaccessible ,

[tintin974]

[tintin974]

document.querySelectorAll(‘et2-htmlarea’).forEach(htmlarea => {
const component = htmlarea.shadowRoot?.querySelector(‘tinymce-editor’)
const root = component?.shadowRoot

if (!root) return

root.querySelectorAll('.tox-tinymce, .tox-editor-container, .tox-edit-area, iframe').forEach(element => {
    element.style.setProperty('visibility', 'visible', 'important')
})

})

dans le Console , cette commande permet d’avoir les champs en edition,

[tintin974]

Version : egroupware-docker 26.6.20260619
Application : News Admin
Composants concernés :

• news_teaser
• news_content

État :

• ET2-HTMLAREA visible
• TINYMCE-EDITOR présent
• iframe présente
• dimensions correctes
• disabled = false
• .tox-tinymce visibility = hidden

Contournement confirmé :
forcer visibility: visible rend l’éditeur visible et éditable

[RalfBecker]

Hi Tintin974,

If I create a new news item, I’m able to edit both teaser and content:

Maybe the problem on your side is due to the invalid certificate show in the top of your screenshot.

Ralf

[tintin974]

SLT? je suis en Serveur local, en acces intranet seulement , le certificat devient obligatoire ?

[tintin974]

la visibilité des champs est lié au certificat ??

[tintin974]

j 'ai releve ceci, je sais pas si ca impacte directement mon bug!

dans api/js/etemplate/Et2HtmlArea/Et2HtmlArea.ts

return (api.webserverUrl+“api/js/etemplate/Et2HtmlArea/skins/ui/egw”+((darkmode == “0”)?"":"-dark"));
si api.webserverUrl = /egroupware
alors ca donne /egroupwareapi/js/etemplate/Et2HtmlArea/skins/ui/egw au lieu de return (api.webserverUrl+"/api/js/etemplate/Et2HtmlArea/skins/ui/egw"+((darkmode == “0”)?"":"-dark"));

dans mon code html j’ai

/egroupware/api/js/tinymce/langs/fr_FR.js 404

[RalfBecker]

Hi? I’m on a local server, with intranet access only. Is a certificate now mandatory?

Not by us (EGroupware), but there are many areas were browsers enforce that more and more.

Was just something which might cause your problem …

Ralf

[RalfBecker]

We found a problem with the skin URL and it’s fixed now with a patched image:

partially revert 2a985c4744e0738b2e6b31d5f30fbfacefe50739 to fix missing / in skin url and translations

Might make sense to pull the image again and see, if that also fixes your problem in news-admin.

Ralf