Upgrade, same procedure as always? Upgrade, same procedure as always?
 

News:

CPG Release 1.6.27
change DB IP storage fields to accommodate IPv6 addresses
remove use of E_STRICT (PHP 8.4 deprecated)
update README to reflect new website
align code with new .com CPG website
correct deprecation in captcha

Main Menu

Upgrade, same procedure as always?

Started by nickelas, March 23, 2018, 03:21:30 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

nickelas

Happy to see the project is still going!
I am looking to upgrade to 1.6 and am unsure of the process. Is it the same as always, but grab the files from github instead?
Human

ron4mac


nickelas

Thank you! Used the stub and it appears to have worked.

(It said depreciated connection method, I choose mysqli but got a critical error when I first tried to log in. But navigating back looks like it triggered something and all seems good)
Human