3.7.0 WYSIWYG

After upgrade to 3.7.0, the WYSIWYG editor is completely gone, whether the module is enabled or not, and the configured options inside this module.

A way to reset it please ?, is a bit urgent.

thanks

Does anybody has this problem in 3.7.0 too?, please confirm

Hi planpc,

If you do a new installation 3.7.0 is running properly editor?
In my dolibarr after upgrade (3.6.2 to 3.7.0) has not presented problem.

Hello ndrosis, thank you for your answer

maybe the problem is because I updated from 3.6.0 to 3.7.0, is the dolibarr installation that I´m using since 3.2.2 and never before happen to me, don´t know how to solve it now, from my humble point of view, WYSIWYG was working before and must work after the update, as the update process replace every files of that module.

As I figure, I replace the new files and folder from the new version (3.7.0) to my current Dolibarr directory (3.6.0), run the update, and there must be all files necessary for this function works, but the true is that it does not , and I´m having problem with some other modules. I´m having too many coincidences in 3.7.0, reason why I opened this post, so other user can compare their experience and discuss.

I have some other open topics with very strange problems that I have never before experienced.

If somebody could please help me, point me to any documentation to make a fresh installation but importing my current database, I think that I´ll try it, after all, a new installation of 3.7.0 with no data will have no benefit as I am using dolibarr since 3 or 4 years ago. Some time ago I tried this (installation from scratch using my data), but never achieved it. Maybe some 3rd party modules installed along the time are making those mistakes.

Regards

See the permissions on the folders and files dolibarr

folders = 755
files = 644

1 Like

Files and folder permissions are Ok, but still no work.

After a new installation from scratch WYSIWYG is working with a blank database but when I point to my current database WYSIWYG stops working, it´s seems clear the problem is in the database, but why after a simple update?.

Its the same thing with margin module, so updating from 3.6.0 to 3.7.0 is the problem.

Any idea how to solve it?

I found what was causing that problem, in not the database nor the 3.7.0 update is my curiosity (sorry), if this GLOBAL OPTION is set to 1, (tested with Firefox and Chrome, lastest versions).

MAIN_USE_JQUERY_MULTISELECT => Allow to use Ajax when a choice that require multiselect is used (for the moment only external modules uses select box with multiselect values).

The WYSIWYG and margin module doesn´t work, deleting that entry of setting to 0 those modules work again. Hope this could help to others.