Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

PSA: 7.3 compatibility issues (saving field meta) #380

Open
Mosnar opened this issue Feb 19, 2019 · 3 comments
Open

PSA: 7.3 compatibility issues (saving field meta) #380

Mosnar opened this issue Feb 19, 2019 · 3 comments

Comments

@Mosnar
Copy link

Mosnar commented Feb 19, 2019

This is just a warning and reference for people searching for this issue in the future. One of our servers automatically upgraded to PHP 7.3 due to the version constraint being set incorrectly. Craft compatibility aside, this causes some pretty weird behavior with SEOmatic. The primary symptom I observed was that SEO meta field data would not save (though the overrides were working, no errors thrown).

I suspect this has something to do with string sanitation parameters having changed in 7.3; however, I didn't look into it very much since we weren't supposed to be on 7.3 anyway.

If you're using services like Heroku, make sure you set your PHP version constraint to this to avoid automatic upgrades to 7.3:
"php": "~7.2.0",

This package is deprecated and unmaintained, so I'm just posting this to help save the next person some time.

@darylknight
Copy link

Yep, thanks mosnar. I'm maintaining an old Craft 2 site. My local Valet installation runs on PHP 7.3, and I can't see the front end of this site - getting this error:

Property "Craft\Seomatic_MetaFieldModel.0" is not defined.

@ow
Copy link

ow commented May 22, 2019

Ah crap, I'm affected by this too—I haven't been able to migrate yet and this kinda leaves me stranded

@jamesmacwhite
Copy link

jamesmacwhite commented Jan 5, 2021

I'm aware this is old issue, but our upstream provider intends to remove PHP 7.2 soon. I deployed our Craft 2 (latest version) site on PHP 7.3.21 to test things and I don't seem to have any issues saving entries and no issues on the front end. No PHP errors related to SEOMatic and it's meta field. Either I'm not hitting the right issue with my environment or this magically got fixed somehow.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants