v3.1.6 compatibility issues

hus_hmd · Jun 5th 2020

Here are some of the PHP 7.4 compatibility issues the community spotted so far:

PerchUtil::safe_stripslashes() uses get_magic_quotes_gpc(), which is a deprecated function.
PHP 7.4 is now strict about the order of the parameters in implode($glue, $array). Perch core uses the alternative order in multiple files.
money_format() is now deprecated. It is used for formatting currency values with the format attribute.

There is also a mysql 8 compatibility issue as it appears not to support using [[:<:]][[:>:]] for word boundary in regex expressions. This affects the content search handlers and the contains / !contains filters, which can be found in the following classes:

PerchFactory
PerchContent
PerchContent_Runway

ryan · Jul 1st 2020

I'm also seeing issues with S3 uploads on later versions of PHP. One issue being:

`Warning /admin/core/runway/apps/perch_s3/lib/guzzlehttp/guzzle/src/Handler/CurlFactory.php67` and `

: count(): Parameter must be an array or an object that implements Countable in`

And another, I think is linked to the S3 library and it's handling of Assets:

https://github.com/aws/aws-sdk-php/issues/1923

I've always been really confident in updating to later versions of PHP with Perch, one of it's major selling points is that it just well, works. Hoping we can see some updates really soon to address these issues and keep Perch stable.

ex-jedi · Jul 1st 2020

We were all very pleased to see a long awaited update, but there's still a lot to be addressed. Have any of the issues above been noted drewm or rachelandrew?

Thanks

SimonClay · Jul 1st 2020

Following thread.

nascent · Jul 19th 2020

I have deprecation messages, right throughout the CMS.

hus_hmd · Jul 19th 2020

Quote from nascent

I have deprecation messages, right throughout the CMS.

Can you share what they are?

Clive Walker · Jul 20th 2020

Quote

I've always been really confident in updating to later versions of PHP with Perch, one of it's major selling points is that it just well, works. Hoping we can see some updates really soon to address these issues and keep Perch stable.

Yes, please. A Perch update addressing PHP 7.4 issues would be very welcome right now.

ex-jedi · Jul 20th 2020

Any response would be welcome.

jsphpndr · Jul 25th 2020

This isn't PHP related, but Perch related and having to do with updates. The present Dashboard isn't adapted for a strong Content-Security-Policy.

As of right now, the CSP requires and unsafe-inline directive to permit inline styles and scripts. This defeats the whole purpose of the CSP.

It's just a wishlist item. I would've loved to have carried on with Perch in other projects. Sad to see it go.

SimonClay · Jul 28th 2020

It seems we are stuck. I worry that PHP7.4 compatibility issues will force us away from this CMS and cost a lot of development time to migrate to a CMS that work with newer versions of PHP.

I have over 40 Perch sites that would need to be re-purposed.

drewm · Jul 30th 2020

Thanks for the detailed notes, all. They've helped me identify and fix nearly all the above issues.

The only ones I've not been able to address are the weird PhotoShop EXIF issue (need to source some images to reproduce) and the CSP issue, which I'm not sure is a simple fix.

ryan · Jul 30th 2020

Quote from drewm

The only ones I've not been able to address are the weird PhotoShop EXIF issue (need to source some images to reproduce) and the CSP issue, which I'm not sure is a simple fix.

I've just popped you an email Drew with an image that should help reproduce the issue - hopefully it helps

seoMatt · Jul 30th 2020

drewm Thank you sir I appreciate your work. If I can get PHP 7.4 & then 8 to be bug free I'm good to moving forward.

nascent · Aug 1st 2020

Quote from j-pinder

This isn't PHP related, but Perch related and having to do with updates. The present Dashboard isn't adapted for a strong Content-Security-Policy.

As of right now, the CSP requires and unsafe-inline directive to permit inline styles and scripts. This defeats the whole purpose of the CSP.

It's just a wishlist item. I would've loved to have carried on with Perch in other projects. Sad to see it go.

Perch is working better since the 3.1.7 update.

I have an ongoing issue with running a Service Worker, bringing the Perch Login to an unfound page but all in all the update has improved performance.

One thing I had to do though, was create a new database and import but that happened while I was running 3.16.

Unconfirmed but I think I can now have multiple tabs open and edit region content independently, which is very welcome if operational.

All in all, the CMS is supported by the developers, which is very comforting for me since I have invested a huge amount of time into my templates and I don't want to have to run a HTML only website just to salvage my work, or re-design something on a new CMS.

nascent · Aug 1st 2020

Quote from hus_hmd

Can you share what they are?

No problems anywhere now with 3.1.7:

PHP 7.4.8 is up to date
MySQL 5.5.5-10.2.32-MariaDB is up to date

Thank you for taking time to look into it.

ex-jedi · Aug 1st 2020

Successful update to 7.4.8. Looking good!

Mikeymu · Feb 1st 2021

Hi. This is my first comment here. I'm glad to see the post mentioning a content security policy, as it's something I feel is important, having spent the time to learn how to create one myself in an htaccess file on my own business website.

OK, from j-pinder's comment, inline css is a problem, but does anyone know if the other vulnerabilities throw no conflicts between PerchCMS and a csp?

Am looking into using Perch for the first time.

James Fox · Apr 14th 2021

Was anyone else still getting a Deprecated: implode() message after installing v3.1.7?

On line 352 of the PerchContent.class.php file I had to swap the parameters around from:

PHP

$sql .= ' AND ('.implode($where, ' OR ').') ';

to

PHP

$sql .= ' AND ('.implode(' OR ', $where).') ';

v3.1.6 compatibility issues

Similar Threads

Perch and Runway 3.1.6

Error Deprecated : Function get_magic_quotes_runtime() is deprecated in C:\PortableApps\UniServerZ\www\perch\core\lib\PerchDB_MySQL.class.php on line 375