You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgraded from 2.8.3 per the instructions to 3.0.0. The getResources custom Property Sets did not work, were not displayed the Property Sets. I created a new Property Set with the same name and got an error stating that it already exists.
So I cleared the cache, logged out, logged in, clicked on the property sets and only the default Property Set displayed. I created a new Property Set and got the same error: it already exists.
Here's the Screenshot:
I forgot that I can look at all Property Sets, so I opened them up and there was my original Property Set WindsorArticles:
Note all of the triangles in that screenshot. It showed the associated Element for the new Property Set WindsorArticles3. I opened them all and only the new Property Sets I created after upgrading to 3.0.0 display the associated Element:
Is it possible that this error was caused by the 2.8.3 install not having Collections installed prior to the upgrade? I installed it and within the element getResources, those prior Property Sets do not display. I clicked on the Versions (VersionX) tab and see that I have versions go back 10 years ago.
If you need to poke around in my Cloud, or need further clarifications, just let me know.
Peter
The text was updated successfully, but these errors were encountered:
PeterBcreates
changed the title
Custom Property Sets do not display
MODX 3.0.0 Custom Property Sets do not display
Apr 11, 2022
So I cleared the cache, logged out, logged in, clicked on the property sets and only the default Property Set displayed. I created a new Property Set and got the same error: it already exists.
Here's the Screenshot:
Note all of the triangles in that screenshot. It showed the associated Element for the new Property Set WindsorArticles3. I opened them all and only the new Property Sets I created after upgrading to 3.0.0 display the associated Element:
If you need to poke around in my Cloud, or need further clarifications, just let me know.
Peter
The text was updated successfully, but these errors were encountered: