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

Upgrading from 3.2.10 to 3.3.01 created a Undefined index: siteId issue #4886

Closed
zizther opened this issue Sep 4, 2019 · 6 comments
Closed

Comments

@zizther
Copy link

zizther commented Sep 4, 2019

Description

After upgrading from 3.2.10 to 3.3.01 the site is now not working on the frontend, with the error showing Undefined index: siteId in in /Users/nathanreed/Documents/Sites/motm/vendor/craftcms/cms/src/elements/db/ElementQuery.php line 1699

This site was developed in C2 before upgrading to C3.0.* +

Steps to reproduce

  1. Have a Craft 3.2.10
  2. Upgrade to 3.3.01 via composer

Additional info

  • Craft version: 3.3.01
  • PHP version: 7.2.20
  • Database driver & version: MYSQL 5.7.26
  • Plugins & versions:
@zizther
Copy link
Author

zizther commented Sep 4, 2019

This ended up being an issue with Solspace Calendar and the search param.

@zizther zizther closed this as completed Sep 4, 2019
@jacotijssen
Copy link

This ended up being an issue with Solspace Calendar and the search param.

Running into the same issue (also using Solspace Calendar). How did you fix it?

@zizther
Copy link
Author

zizther commented Sep 5, 2019

The issue for me was to do with the search param in the events query.
I have submitted a bug report to Solspace, they were able to replicate and are working on releasing a fix.

I am able to remove the search param for the query for now to solve the issue, if you are able to, this should solve the problem temporarily until the update is release from Solspace

@brandonkelly
Copy link
Member

We ran into this in some of our own code as well, when the select clause was being overridden. I’ll go ahead and reopen this and fix it.

@brandonkelly
Copy link
Member

And fixed for the next release.

To get the fix early, change your craftcms/cms requirement in composer.json to:

"require": {
  "craftcms/cms": "dev-develop#cd3c3e5c48aecdb22c1f373184e88785cc1a5dc6 as 3.3.0.1",
  "...": "..."
}

Then run composer update.

@zizther
Copy link
Author

zizther commented Sep 6, 2019

I can confirm this has fixed the issue I was experiencing.
Thanks for sorting so quickly!

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

No branches or pull requests

3 participants