Skip Navigation

[Resuelto] WYSIWYG editor has no css. Client denied by server configuration on server logs

This support ticket is created hace 5 años, 6 meses. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

Este tema contiene 6 respuestas, tiene 2 mensajes.

Última actualización por stefanoT-2 hace 5 años, 6 meses.

Asistido por: Nigel.

Autor
Mensajes
#1249177
Annotazione 2019-05-24 123651.jpg

I have a toolset form which create a new Custom Post Type in my website. This form has a lot of fields, including two WYSIWYG Editors. The buttons and tabs in the WYSIWYG editor looks like they don't have any "css style" (see screenshot).

I checked the logs on my server and is see this errors:
1. GET /wp-admin/load-styles.php?c=0&dir=ltr&load%5B%5D=editor-buttons&ver=5.2.1 HTTP/1.1
2. AH01630: client denied by server configuration: /path/to/website/directory/wp-admin/load-styles.php, referer: enlace oculto

For testing, I removed all the fields from the form except one WYSIWYG editor but the error still occurs.
If I remove the two WYSIWYG Editors the logs don't show any errors.

I have 5 website which have the same form, plugins and configuration, but only on 2 of these happens this error. The other 3 are fine.

I don't know what to check anymore, any advice?

#1249209

Nigel
Supporter

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+00:00)

Hi Stefano

Can you identify any differences in the server configuration between the sites which work and the sites which do not?

Your debug info is from a site that works or does not?

Can you try on a minimal install, i.e. after disabling all plugins except Types and switching to twentynineteen theme, to see if that highlights any conflict that may be involved?

#1249369
Annotazione 2019-05-24 152034.jpg

The server configuration is the same between the websites (see attached screenshot).
Usually I don't edit any server configuration other than the ones in the image.

The debug info is from a site that DO NOT work. If needed, I can provide debug info of a working website.

The plugins installed in the 5 websites are all the same.
Unfortunately, the two websites where the problem occurs are live sites. I cannot disable all plugins or switch to default theme without making a copy, which requires some time.

I hoped in a fast solution, maybe it was a known bug or something that I overlooked.
If there's no fast solution, I'll find the time to make a copy of a "broken" site and check plugin by plugin to search any conflicts.

Thanks for the fast reply!!

#1249389

Nigel
Supporter

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+00:00)

Unfortunately it is not a known issue, so we'll need to try and identify the cause on the problem sites.

If you are able to duplicate them for testing then please do, and let me know what you find.

#1250697

I have duplicated the two websites which have the problem. In these copies, the forms show well and there isn't any error in the logs. I can't really explain why.

I copied all the files to a new folder, copied the database and changed the URL to the temporary one in the new database. I didn't edit anything.

I don't know what to think. Maybe is something domain-related?

#1250977

Nigel
Supporter

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+00:00)

I'm not sure what to suggest if you transferred the site to another server, where it then works correctly.

I understand the problem is on live sites. Can you just briefly temporarily disable the caching and security plugins on the site to test without those?

#1251579

I found a solution.

I made a copy of the website directory and changed the website root to the new folder. And the error automagically disappeared.

Sadly, I don't know the cause of the error, but at least I found a workaround.