[Résolu] Tiny MCE is throwing errors causing problems.
This support ticket is created Il y a 5 années et 6 mois. 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.
Aucun de nos assistants n'est disponible aujourd'hui sur le forum Jeu d'outils. Veuillez créer un ticket, et nous nous le traiterons dès notre prochaine connexion. Merci de votre compréhension.
TinyMCE is throwing errors in console and therefore creating links and saving links is not working and previous links break.
Errors are this (see screenshot as well):
- Failed to initialize plugin: wordpress ReferenceError: types_tinymce_compatibility_l10n is not defined
- Uncaught TypeError: s.toLowerCase is not a function
- Uncaught TypeError: Cannot set property 'tempHide' of undefined
I disabled all plugins and switched themes to twenty seventeen. Problem still occured.
Hi Nigel,
Thanks for your help.
- I just disabled all plugins except for Types (necessary to see the error) and really simple SSL (else the site is not visitable anymore). The problem was still there.
- The problem occurs on pages that have a repeatable field group (as far is i can see that is the trigger).
- Furthermore i have the same issue with the big images in backend (see other issue).
- And i see a error message on a strange place (see screenshot) stating: Failed to initialize plugin: wordpress
If you would like to have access to create a copy; please make next answer private.
Thanks!
Hi Nigel,
thanks for the update and all the effort. Is it possible to give me a timeline? Since the client has problems adding links in repeatable fields at the moment.
Thanks and have a good day!
Marc
Les langues: Anglais (English )Espagnol (Español )
Fuseau horaire: Europe/London (GMT+00:00)
I can't really say as we haven't got to the bottom of the issue yet.
My colleague has been checking a copy of your site and notes various problems, some of which are not obviously Toolset, and sees that it is impossible to export then import your Types settings to another site, which suggests some corruption of the database.
They are asking if you can provide any history as to when this issue began and what steps you may have taken before it appearing.
Hmm, that does not sounds good at all.
The site is build and currently hosted on Siteground, so dbase corruption did probably not occur on migration. I have the idea that problems started while updating to Types 3.3 (but i can not be 100% sure).
If you see a non TS related problem, please let me know so my devs can check it out.
Thanks for all the good work, Nigel.
Marc
Les langues: Anglais (English )Espagnol (Español )
Fuseau horaire: Europe/London (GMT+00:00)
Hi Marc
My colleague exported your Types settings to a new site and was able to see the issue, and then we got another report of the same, so it's not something specific to you.
We've added an erratum and the devs are aware of the problem and looking into it now. We'll hopefully have a fix soon, i.e. this week.
Ok. Good to know. I hope the devs are able to provide a fix soon. Thanks for your help in this.
For the large images in the backend (of pages for example); do you see them as well?
Les langues: Anglais (English )Espagnol (Español )
Fuseau horaire: Europe/London (GMT+00:00)
On my local install I have just Types and twentynineteen theme active, and when editing the homepage the images I add to the image field are sized normally (see screenshot after I replaced the current image with one of my own).
In the other thread which is closed you didn't confirm if you have tested with other plugins disabled to eliminate conflicts.
Les langues: Anglais (English )Espagnol (Español )
Fuseau horaire: Europe/London (GMT+00:00)
Hi Marc
We have released Types 3.3.1 which includes a fix for this issue, and it also includes some CSS fixes that might resolve the issue with the image fields.
Can you update and let me know the progress of both?
Hi Nigel,
good news, the issue in the WYSIWYG editor is resolved. The issue with the large images in the backend is still there. I will dive into that later this week and update you once i've done that.
Thanks!
