While updating a few of my pages to use SS-Pro, I have run across a problem with broken scripts. In SS and WE, a select list was given an id name based on the SS object name and a name attribute matching the Name field of the Select List tab.

In SS-Pro, the select list is now wrapped in a <div> block named with a SS-Pro derived object name, the select object is given an id name derived from the geometry name, and a name attribute matching the Name field of the Select List tab.

Scripts based on using the getElementByID() function will no longer work since the change in the naming convention, most significant of which is the change in the prefixing character (from an "O" to a "G").

Hi Larry,

The problem was actually is SS and WE. The selection list is really a geometry in the IMS way of doing things. So SSP now correctly uses 'Ggeoname' instead of 'Oobjname' as the ID and wraps the geometry with a div object.

Sorry if this created problems for you. Is there anything that doesn't work in yor script once you adjust for this?

Once I make some adjustments, the scripts will work in both SS/WE and SS-Pro. I just need to run thru my scripts to make sure they work in both versions and if not, make a few tweaks.

I'm assuming that you will be "fixing" the SS naming conventions in the next update release. Will it also be able to read SS-Pro project files or will that be put off for an even later release?

Yes, the next release of SiteSpinner will generate code the same way SiteSpinner Pro does.

It will be able to load SiteSpinner Pro projects but will not have access to any Pro specific features in a project (like mobile layout or animations).