Breezing form migration problem

Good morning,Regarding Option 1:
I have activated maximum debugging as instructed, but no PHP error appears. The issue can be replicated at any time.Instead of providing a full Akeeba backup (the site is quite large), I have created a full snapshot of the current state, so there is no risk of breaking anything — I can restore the site to this exact moment at any time if needed.I can provide you with access to the Control Panel, FTP, Joomla backend, and the database.
Please let me know if this is OK for you to proceed, and how you would like me to send you the access credentials.Kind regards!

Hello oficinamediaes,

As already mentioned, we need an Akeeba backup of the website for local debugging.
Administrative access to the backend is not sufficient in this case.

We need an Akeeba backup of the website in a working version where the error can be reproduced.
Anything unnecessary for operation and error reproduction can be deleted and omitted.

Best regards, Ingmar

Hi,I have prepared the Akeeba backup file, but it is 18GB in size.I believe the fastest solution would be to provide you with full access to my server (as mentioned, I’ve already created a backup of the current state so I can restore it at any time if needed).Alternatively, please confirm that I should send the Akeeba backup file to forum@vi-solutions.de, using "Breezing Form migration problem" as the subject.Waiting for your answer,
thanks

Please let me know!
I need to solve this problem asap!!

Hello oficinamediaes,

We are happy to accommodate you and debug your Joomla instance regarding the error while saving the form configuration.

However, I would also like to point out that saving the form configuration works as expected everywhere else.
The reason for the error in your Joomla instance is therefore very likely not related to Visforms or a successful Visforms installation.

The 18 GB is simply far too large, and we won't be working with it.
There's absolutely no reason, especially for troubleshooting, why a Joomla instance needs to be this large.

It's far too much work to remotely debug the PHP code on an unknown live site from an unknown hosting provider with an unknown hosting package, even with all the necessary access options and credentials.

At this point, I must insist that the data volume of the Akeeba backup be reduced to a truly necessary and acceptable size.

I can only repeat myself and not write anything new:
We need an Akeeba backup of the website in a working version where the error can be reproduced.
Anything unnecessary for operation and error reproduction can be deleted and omitted.

Kind regards, Ingmar

Hello oficinamediaes,

Saving the form configuration works as expected everywhere else.
Visforms has no other problems saving the form configuration.
There is also no PHP error when saving the form configuration, which could indicate an existing problem in Visforms.

I suspect that the error is most likely related to the TinyMCE plugin (TMP).
TMP works intensively with the entered text.
TMP can be configured very extensively, for example, when editing and saving content.

I suspect that your problem is ultimately with TMP.

Since there are apparently no PHP errors, I suspect a JavaScript problem.
TMP primarily works with JavaScript in the web browser.
You could check the web browser's developer tools to see if there is a JavaScript error on the page.

The use of the web browser's developer tools is described in the documentation.
Use the developer tools:
docs.joomla-5.visforms.vi-solutions.de/e...-the-developer-tools

Kind Regards, Ingmar