Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.x]: siteId should be a reserved word #12577

Closed
siebird opened this issue Jan 25, 2023 · 4 comments
Closed

[4.x]: siteId should be a reserved word #12577

siebird opened this issue Jan 25, 2023 · 4 comments
Assignees

Comments

@siebird
Copy link

siebird commented Jan 25, 2023

What happened?

I stumbled across this one as we were using siteId as a custom field in Burrow and was wondering why generated titles {siteId}_{date} was using 1 instead of the value in that field entry.

Craft CMS version

4.3.6.1

@brandonkelly
Copy link
Member

We’ve added a whole bunch of new reserved field handles for the next Craft 3 and 4 releases, to avoid additional conflicts with craft\base\Element properties.

@brandonkelly
Copy link
Member

Craft 3.7.64 and 4.3.7 have been released with that change.

@leevigraham
Copy link
Contributor

@brandonkelly How does adding new reserved field names effect existing fields which already have a reserved field name?

@brandonkelly
Copy link
Member

@leevigraham You’d get a validation error the next time you try to save the field.

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

No branches or pull requests

4 participants