Scriplet Assignments and Deployment to a Different Server

[marbesman]

Hello,

I am running development on one server and deploying our updates to a production server. Currently, I can't seem to figure out how to maintain the scriplet assignments to each page I've made on our dev server.

I saw a table called ac_Sharedpersonalization. There is a binary data field that I guessed may save all the assignments made throught the EditScriplet user control. But migrating the table data does not seem work.

I looked in the user control, EditScriplet, to see where the assignments were being save and could not figure out what the following code does or where it saves this data.

_Scriptlet.ScriptletData = ScriptletData.Text;

So as of now, after a new deployment is made, we have to run through the entire site and manually make the scriplet assignments.

Any help would be much appreciated.

(BTW I've worked on estore software from Commercial products from large corporations to open source...and Ablecommerce is the best hands down...thank you for making it so developer friendly.)

[jmestep]

I'm not sure exactly what you mean, but there is also a table ac_PersonalizationPaths. That is in addition to what is stored in the App_Data/Scriplets folders.

[marbesman]

Hi Judy,

Thank you for the quick reply. Let me back up and explain in more detail what I am trying to do.

When you log in as an administrator, you can modify the layout of the pages of the store. You can then select the layout scriplets and save them for each page. I want to be able to frequently update our production server with these selections.

What is the best way to do this? I have tried migrating the data in the database tables ac_PersonalizationPaths and ac_SharedPersonalization. But that does apply the scriplet selections.

Does that help?

Thanks,

Marc

[marbesman]

Ok I figured this one out. I just had to migrate the data in the tables ac_PersonalizationPaths and ac_SharedPersonalization with the Identity field in tact. I removed all rows on production, and reset the identity field in the ac_PersonalizationPaths table. I then used the Import/Export wizard in SQL Server 2005 to migrate the data.

I had to first run an export on ac_PersonalizationPaths before running it on ac_SharedPersonalization. It was more a lesson in SQL Server data manipulation than AbleCommerce. But simplicity like this makes working on this store fantastic.