I’m using the Twenty Twenty-Two theme to redesign my site (and practice using Cwicly). I can make changes to the templates by selecting the “Edit” option, but when I go to set the “Visibility” options, nothing happens. I can click on the drop-downs and select an option, but nothing gets changed/saved (although “Saved” does show at the bottom of the page).
I have disabled all of my plugins, except for Cwicly.
In the Admin Area, select “Cwicly, Themer”
Select “Visibility” option for any of the templates.
(Note: “Saved” shows at the bottom of the page before any selections are made)
Try to select a condition (Show/Don’t Show)
No selection is saved.
In looking at the console, the following error is produced (for any of the changes I try to make):
react-dom.min.js?ver=17.0.1:9 Uncaught TypeError: Cannot read properties of undefined (reading ‘0’)
at Ye (index.js?ver=1.2.8.7.3:1:190504)
at Object.onChange (index.js?ver=1.2.8.7.3:1:140784)
at onChange (index.js?ver=1.2.8.7.3:1:93987)
at index.js?ver=1.2.8.7.3:1:88543
at i.onChange (index.js?ver=1.2.8.7.3:1:67042)
at i.setValue (index.js?ver=1.2.8.7.3:1:67304)
at i.selectOption (index.js?ver=1.2.8.7.3:1:67754)
at J.y (index.js?ver=1.2.8.7.3:1:83353)
at Object.ha (react-dom.min.js?ver=17.0.1:9:95935)
at B (react-dom.min.js?ver=17.0.1:9:9748)
So sorry to see you’re having trouble with the Themer.
Could you try removing all the conditions from the templates and see if you can add new conditions and apply modifications?
I went back and deactivated all of my plugins and reset all of the Twenty Twenty-Two templates and template parts.
I then brought everything up in Themer and attempted to make a change in “Visability”, but received the same error message as before.
I reactivated the Cwicly theme with no changes and attempted to “Reset” the Index template, and received the following error message:
Uncaught (in promise) {code: 'rest_invalid_template', message: "Templates based on theme files can't be removed.", data: {…}}code: "rest_invalid_template"data: {status: 400}message: "Templates based on theme files can't be removed."[[Prototype]]: Object
Promise.then (async)
onClick @ index.js?ver=1.2.8.7.3:1
vf @ components.min.js?ver=4b876f1ff2e5c93b8fb1:38
(anonymous) @ components.min.js?ver=4b876f1ff2e5c93b8fb1:38
ha @ react-dom.min.js?ver=17.0.1:9
B @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
He @ react-dom.min.js?ver=17.0.1:9
je @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
sa @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
Xe @ react-dom.min.js?ver=17.0.1:9
ge @ react-dom.min.js?ver=17.0.1:9
me @ react-dom.min.js?ver=17.0.1:9
unstable_runWithPriority @ react.min.js?ver=17.0.1:9
xn @ react-dom.min.js?ver=17.0.1:9
ua @ react-dom.min.js?ver=17.0.1:9
pe @ react-dom.min.js?ver=17.0.1:9
When I went in to try and set any “Visability” settings, I received the same error message as before:
Uncaught TypeError: Cannot read properties of undefined (reading '0')
at Ye (index.js?ver=1.2.8.7.3:1:190504)
at Object.onChange (index.js?ver=1.2.8.7.3:1:140784)
at onChange (index.js?ver=1.2.8.7.3:1:93987)
at index.js?ver=1.2.8.7.3:1:88543
at i.onChange (index.js?ver=1.2.8.7.3:1:67042)
at i.setValue (index.js?ver=1.2.8.7.3:1:67304)
at i.selectOption (index.js?ver=1.2.8.7.3:1:67754)
at J.y (index.js?ver=1.2.8.7.3:1:83353)
at Object.ha (react-dom.min.js?ver=17.0.1:9:95935)
at B (react-dom.min.js?ver=17.0.1:9:9748)
Ye @ index.js?ver=1.2.8.7.3:1
onChange @ index.js?ver=1.2.8.7.3:1
onChange @ index.js?ver=1.2.8.7.3:1
(anonymous) @ index.js?ver=1.2.8.7.3:1
i.onChange @ index.js?ver=1.2.8.7.3:1
i.setValue @ index.js?ver=1.2.8.7.3:1
i.selectOption @ index.js?ver=1.2.8.7.3:1
J.y @ index.js?ver=1.2.8.7.3:1
ha @ react-dom.min.js?ver=17.0.1:9
B @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
He @ react-dom.min.js?ver=17.0.1:9
je @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
sa @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
Xe @ react-dom.min.js?ver=17.0.1:9
ge @ react-dom.min.js?ver=17.0.1:9
me @ react-dom.min.js?ver=17.0.1:9
unstable_runWithPriority @ react.min.js?ver=17.0.1:9
xn @ react-dom.min.js?ver=17.0.1:9
ua @ react-dom.min.js?ver=17.0.1:9
pe @ react-dom.min.js?ver=17.0.1:9
I’m sorry for not getting back on this one.
Could we possibly check this out with temporary access if it’s on a live installation?
If yes, would be great if you could send the details to support@cwicly.com
Thanks for the access once again, I won’t need it again for the moment
I took a look at the conditions option and saw a considerable amount of null values… Not quite sure how they got there. Is this a clean install that’s never been imported/exported or had its database modified in some way?
In any case, I deleted the conditions option and everything seems to be working on my side now.
I’ll try and reproduce this error on my side and update on the situation here if I find anything.
I’d be grateful if you could let me know if everything is good on your end.
This is an export from our live site at https://redeemersatx.com. It was imported into LocalWP, and I cleared out the old theme (Blocksy), installed Cwicly, installed the Tewenty Twenty-Two theme, then the Cwicly theme.
I can go in and edit the templates from the Themer, and I can reset them back to their original content, but I can’t set any conditions as to when a template is used.
Please let me know if you need access or if you need additional information. Thank you!
I’m not sure what happened this weekend (there wasn’t an update or anything), but I can now set the conditions in the Themer.
I had originally disabled all plugins, turned off any cache, and cleared out old drafts, etc. Doesn’t make any sense, but it’s working, and I guess that’s the important thing at this point.
Sorry for not getting back on this one, when you gave me access I removed the conditions option in the database and was able to add them myself from the Cwicly Themer.
Glad to hear that you can finally add conditions, although I’m not quite certain why you couldn’t before. But the null conditions that I saw in the conditions options before did seem unusual.
