Answered Property Set Not Found

Hi Guys

I upgraded a site to modx 2.4.2.

When I save templates I get this error message: "Property set not found with ID 0."

What does this mean and should I ignore?

Thanks

Well I was looking it up and find its pretty straightforward, can we have your code? An element in your template evidently is running afoul of...something. Doesn't look like the template itself has a set.

When a snippet is called with a tag, MODx gets the default properties of the snippet and places them in the $scriptProperties array. Then it merges in any properties in any attached property set (specified with @propertySetName in the tag), then it merges in the individual parameters sent in the snippet tag (if any). As each successive set of values comes in, they will overwrite ones with the same name that are already there.

From BobRay: https://forums.modx.com/index.php?action=thread&thread=54924&i=1

Looks like this is pretty deep stuff, not hard so much as a somewhat hidden tool. Pretty cool Not sure what could be done with it tho. [ed. note: nuan88 last edited this post 9 years, 2 months ago.]

How did you upgrade the site? Did you move the new files into place yourself, or did you use the UpgradeMODX extra?

Have you tried manually deleting the core/cache/ directories?

What's the full error message.

I'm getting this error since upgrading my site with UpgradeMODX extra.

Error message:
"Property set not found with ID Default."

The happens when I save any TV and was ok with 2.3.1pl and not since upgrading to 2.5.0pl

I've found that an element without a property set returns this error. So if I have a TV and save it will report "Property set not found with ID 0."

If I add a property and then save I don't get an error.

Just need to figure out why it's grumbling about not finding a property set if it doesn't have one to find. [ed. note: dave-b last edited this post 8 years, 7 months ago.]

Have you tried upgrading to 2.5.1?

That looks like a bug in MODX 2.5.0 since no MODX object ever has an ID of 0.

Hi Bob, Yes. That testing was with 2.5.1pl, I found it came in when I upgraded to 2.4.2pl. Can you think of any way to fix it? [ed. note: dave-b last edited this post 8 years, 7 months ago.]

Did you upgrade to 2.5.0 first? There are some DB changes that were made in that version, though usually the error messages caused by that take a different form.

http://bobsguides.com/blog.html/2016/06/27/missing-db-fields-(unknown-column)/