SharedPersonalization
Posted: Mon Jan 31, 2011 10:35 am
Hey all;
We have some customized pages (ie Default.aspx, CategoryList.aspx, etc) that we want to be able to easily promote from our dev box, to a stage server, then to production.
We are making the customizations via the AbleCommerce UI, so it looks like the customizations are stored in the database (ie in PersonalizationPaths and SharedPersonalizations), right?
DataPort seems to successfully export both PersonalizationPaths and SharedPersonalization when performing a store download (xml).
However, when I try to import the personalizations into another instance of AbleCommerce, it seems to pull in the PersonalizationPaths, but NOT the SharedPersonalizations.
Am I missing something? Is there an easy way to migrate custom pages from one instance of AbleCommerce to another?
I can obviously manually edit the aspx files int the root directory, then copy files from dev to stage then to prod. But that would bypass the cool web based method of customization, and would obviously get messed up if someone accidentally used the web interface (and thus saved customizations into the database).
Many thanks,
We have some customized pages (ie Default.aspx, CategoryList.aspx, etc) that we want to be able to easily promote from our dev box, to a stage server, then to production.
We are making the customizations via the AbleCommerce UI, so it looks like the customizations are stored in the database (ie in PersonalizationPaths and SharedPersonalizations), right?
DataPort seems to successfully export both PersonalizationPaths and SharedPersonalization when performing a store download (xml).
However, when I try to import the personalizations into another instance of AbleCommerce, it seems to pull in the PersonalizationPaths, but NOT the SharedPersonalizations.
Am I missing something? Is there an easy way to migrate custom pages from one instance of AbleCommerce to another?
I can obviously manually edit the aspx files int the root directory, then copy files from dev to stage then to prod. But that would bypass the cool web based method of customization, and would obviously get messed up if someone accidentally used the web interface (and thus saved customizations into the database).
Many thanks,