getOption()

It’s definitely not caching. I have it on more than one install and it survives upgrade to the latest SVN, clearing all caches, etc.

Try installing SPForm and see if the properties show in both places and new property sets can be attached properly after the install.

I’m thinking either it has something to do with package installation (which is still kind of hinky for me) or a problem with XAMPP 1.7.1.

I can’t reproduce this problem at all, but I wonder if we are just miscommunicating. When you call the chunk with the property set, i.e. [[$Chunk@propertyset]], the properties are not available as placeholders? If not, something is definitely wrong with your environment...

Quote from: OpenGeek at Jul 22, 2009, 12:52 PM

I can’t reproduce this problem at all, but I wonder if we are just miscommunicating. When you call the chunk with the property set, i.e. [[$Chunk@propertyset]], the properties are not available as placeholders? If not, something is definitely wrong with your environment...

"Pilot error" would be a better term than miscommunication.

The properties didn’t show on the properties tab of the element because the grid always shows the "Default" property set (which didn’t exist) until you select another one. They didn’t show in the "add property set" list because they were already attached. The placeholders didn’t work because I forgot @propertySet, thinking that if they were attached, it wouldn’t be necessary.

I’m trying to think of changes that would help others avoid similar confusion.

Showing the "Default" property set might not be a good idea since it seems unwise and confusing to have a bunch of property sets all called "Default." Showing the Default set seems especially confusing when there’s no Default set and there is another attached set that’s populated.