In a multisite, after updating from 3.0.5 to 3.0.6, I don't see anymore some values from some Global Sets, but I can see others values in other Global Sets.
I have a Global Set called contacts and inside there are some text input (address, phone, email).
With {{ contacts.phone }} or {{ contacts.email }} it return null.
I have another Global Set called academicYear with a text input (year)
{{ academicYear.year }} return the correct value.
The weird thing is that if I place the text input field year in the Global Set contact I can see the value.
If I create another field and place it in the Global Set contact I don't see the value.
Not esay to reproduce because the behaviour is illogic.
What happens if you clean Craft CMS cache, does that make all globals be null? Mine don't work either. Can't reproduce on a clean Craft installation.
Yes I've tried to clean cache and all kinds of stuff under storage but the globals not appear.
I can't replicate on a fresh installation mee too.
I don't understand why some globals have values return and others not 馃
@babau67, can you see if the globals work again when you are NOT signed into Craft?
I just noticed why my globals worked on one browser and not the other, it was my login session.
I have the same issue as @babau67.
Downgrading to 3.0.5 resolve the issue.
@Wiejeben I tried your suggested method of logging out from cp. The Globals start to work when you are logged out from cp and stop working if you log back in.
Can one of you please send a database backup to [email protected], and give us some template code we can use to reproduce the issue on 3.0.6?
Done @brandonkelly,
Sent via we transfer with a followup email with project details. Feel free to contact me directly with any questions. 馃憤馃徎
I can confirm that Globals work if I'm logged out.
Thanks @sergeifilippov! Fixed for the next release.
We just released 3.0.7 with the fix.