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
Upgrade from v2.1.3 to v2.2 causes Undefined index: sectionUid error #42
Comments
Some additional info: I ran the After 3.1.6 came out, I attempted to update Craft only to 3.1.6 (from 3.1.5) via the command line using the Here's the stack trace from that:
But the interesting bit of this is that I then tried to update Craft from 3.1.5 to 3.1.6 using the control panel button on the Updates page. That worked. It successfully updated to 3.1.6. I thought that this button was only a way to run the same command as the command line did. Whatever the case is, it worked. The update of Guest Entries did not successfully update this way though. It still threw the same error. |
We got the same error after updating this plugin. We just updated the latest Craft version (3.1.6.1) |
Me too. Please fix it. I have a website that is suspended. |
Sam, I was able to roll back to the previous version and it still works though. Can you roll back to the previous version? If not, I can tell you how I did that. Just let me know. -John |
I rolled back, but now i am stuck and can't install or update anything, cuz the composer updates the guest entries and it crashes again T_T |
@Sam-Black-0013 So you rolled back and did a new |
We just released 2.2.1 with a fix for this. |
Nope Mr. john i just rolled back and stopped and waited for the fix to come up. the website is already on production stage so i can't really risk it at this point. |
I have a site (running Craft 3.1.5) that already uses v2.1.3 with a form successfully submitting guest entries. After upgrading the site is brought down by an Undefined index error.
Here is a screenshot of the error:
http://share.jmx2.com/wPyM8X
Here is the Stack trace from my error log:
The text was updated successfully, but these errors were encountered: