AbleCommerce Shopping Cart Software

I need to know where all the page settings are stored? I dont see any of this in the database.

Page settings are stored using binary data with a customized version of the .Net shared personalization provider. The only code example is available in ~/Admin/Website/CustomizedPages.aspx.

The actual code functionality is part of the core CommerceBuilder API - you'll have to own the full source code to see how Able interacts with the binary data.

I have the source, where is it being stored? Why would it be binary? There is a sql data source on that page, but that looks like i handles the delete, so where is this information being stored?

webhead wrote:I have the source, where is it being stored? Why would it be binary? There is a sql data source on that page, but that looks like i handles the delete, so where is this information being stored?

I believe it's being stored in ac_Personalizations.

The page I mentioned references the data class, so I would start digging there.

I have no idea why it's binary - I'm sure there's a good reason for it.

I need someone from able to step in here, the reset on the page does not work, and I can't change the scriptlet content, as when you move into edit mode, the page bombs, so how do you force this to change. I tried uploading over it, and that is not working either. I have to know where the settings for pages are stored so I can go in and change this.

Just submit a trouble ticket with Able - they're usually pretty quick to respond. Able doesn't usually provide tech support via the forums.

Custom scriptlets are stored in ~\App_Data\Scriptlets\Custom. You might be able to unbreak the page by renaming the custom scriptlets one-by-one until the page works. Then you know the last scriptlet you renamed was the culprit.

I was able to reset the page, but had to do that thru the admin section, that reset button on the page did not work. I still would like to know where all these settings are stored. I just read the new post thanks.

I did find an answer the other day to why they are binary - it's a .net personalization thing. Only I don't remember where I read it, but it did explain it.