Deprecated: Function get_magic_quotes_gpc() is deprecated in /libraries/cegcore2/gcloader.php on line 63

Resolve a deprecated function warning in ChronoForms.

Overview

The warning occurs because the code uses the deprecated PHP function get_magic_quotes_gpc().
Apply the official patch provided in the ChronoForms FAQ to correct the code, which resolves the warning for compatibility with newer PHP versions.

Answered
Gr GreyHead 03 Apr, 2020
HI,
​
Please see this thread and, for the meantime you can hide the message by setting your site Error Reporting to System Default or to None.
​
Bob
U U Can Drive 03 Apr, 2020
Thanks Bob, I'd already done that one, I was just hoping there was an actual fix😉
Er Erik66 10 May, 2020
Could I ask wether there is a real fix in the making?
Max_admin Max_admin 11 May, 2020
Yes, in the next update!
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
jj jj135 08 Sep, 2021
I still see this warning in our server error logs. I know it's 'just' a warning, but it might be good to fix this in the code?
Er Erik66 08 Sep, 2021
Dito. The majority fo our websites still use CF6 and this error is one of the few outstanding issues we have with them.
jj jj135 06 Oct, 2021
Hi! Is still see this warning in our logs. Hope this can be fixed in a next release?
St StefaNovak 14 Dec, 2021
Hi, I have the same issue with the newest v6 version. Is there any increase?
Stefan
Gr GreyHead 14 Dec, 2021
Hi ctweed,
​
You will find a fix for this and some other bugs here This should resolve the problem until Max is able to create an update.
​
Bob
ar arvendal 13 Jan, 2022
Hello,
I tried the solution at https://www.chronoengine.com/faqs/76-chronoforms/5335-greyhead, but it created this error instead:
​
0 - Attempt to modify property "_vars" on null
​
I need to update my website to PHP 8. And this problem is preventing me. Do you have a solution?
​
Best regards
Gr GreyHead 14 Jan, 2022
Hi arvendal.
​
The same FAQ includes a fix for this error found by user Elitakey.
​
Bob
This topic is locked and no more replies can be posted.