Forums

First of all
i will recover the missing view & function names via a backup (retype the names manually).
​
But Max you may be informed that the following happened:
My Hoster in Switzerland has a really strict setup for ModSecurity, while using your site you will always face multiple times that your action was blocked by security policy. This can happen while saving an article, change something in the joomla! params and and and... then you can go into the control panel (from the hoster) and disable that rule that you triggered before....
​
Yesterday i had such an issue while saving my connection and i tough, hey - not a big thing... but unfortunately I found that the incorrect save destroyed the entire connection.

​

​
in my situation its not a big deal because i know why that happened and yes its not really your fault.
​
but - it would be great to have an option to idk... go to the last version back or something like that just with one click....
its a bit weird that the whole config is there its just the names of functions and views that was replaced by empty strings because of a failed saving...
​
could probably been improved in some way? :-)
​
kind regards

English
I have exactly the same problem.
But have no solution...
What should I do ?
​
Français
J'ai exactement le même problème.
Mais n'ai aucune solution...
Que dois-je faire ?

You should talk to your host about removing mod_security or whitelisting your IP.

Hello
​
mod_security ? Where ? For MariaDB ? MySQL ? Apache ? Witch file ?
whitelisting my IP ?
​
I'm Working on Windows 10 famille 1909, development platform with WampServer...
- Apache : 2.4.41
- PHP : 7.3.12
- MariaDB : 10.4.10
- Joomla : 3.9.15
I have reinstall ChronoConnectivity and my error is gone...
Why ?Can certain other installations destabilize CronoConnectivity?

I found that installing Forms after Connectivity caused this error. The Function Name field gets lost and so saving seems to remove that information. Uninstalling everything and then reinstalling, but with Forms first and then Connectivity has restored visibility of the field, but I'm guessing it will have done something similarly horrid in Forms. There's clearly a conflict here in the code.

English
Indeed, it seems that there is a bug because we are not the only ones to have encountered this problem.
Hoping for a correction in a future version ...
​
Français
En effet, il semblerait qu'il y ait un bug car nous ne sommes pas les seuls à avoir rencontré ce problème.
En espérant une correction dans une prochaine version...

Is there a solution for this? I have the same problem.
Every time I restore it, everything is lost when I save it ... HELP