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

Setting unknown property: craft\records\Element::draftId After upgrading to Craft 3.2 #4509

Open
Sam-Black-0013 opened this issue Jul 10, 2019 · 7 comments

Comments

Projects
None yet
3 participants
@Sam-Black-0013
Copy link

commented Jul 10, 2019

Description

After i upgraded to Craft 3.2 I get this error when visiting the control panel: Setting unknown property: craft\records\Element::draftId
The entire control panel urls show this error

@Sam-Black-0013 Sam-Black-0013 changed the title Setting unknown property: craft\records\Element::draftId Setting unknown property: craft\records\Element::draftId After upgrading to Craft 3.2 Jul 10, 2019

@brandonkelly

This comment has been minimized.

Copy link
Member

commented Jul 10, 2019

Did you get any errors when updating? Can you check if your elements database table in fact has a draftId column now?

@Sam-Black-0013

This comment has been minimized.

Copy link
Author

commented Jul 11, 2019

I did not get any errors while updating. I did not get an "Update database" screen after i finished the update, so the database is still for Craft 3.1.34

@ep-iain

This comment has been minimized.

Copy link

commented Jul 11, 2019

I am also having this issue.

In my case the migrations for Craft 3.2 all ran successfully and my elements table has a draftId column.

@ep-iain

This comment has been minimized.

Copy link

commented Jul 11, 2019

Update: Clearing caches from the CP seems to have fixed it

@brandonkelly

This comment has been minimized.

Copy link
Member

commented Jul 11, 2019

@Sam-Black-0013 How did you update? From the Control Panel or by running composer update / ./craft update craft ?

@Sam-Black-0013

This comment has been minimized.

Copy link
Author

commented Jul 12, 2019

Composer update

@brandonkelly

This comment has been minimized.

Copy link
Member

commented Jul 12, 2019

@Sam-Black-0013 Can you search for the error in storage/logs/web.log and post the full error log, with the stack trace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.