I have updated my site. The frontend site looks good with the new content but on the backend it still the old content. If I republishing the content from the backend the new one will be replaced with the old stuff....
The new content was in the umbraco.config but not in the DB. If I republished the content from the content node the old content appears from the DB and in the umbraco.config file.
So I loose my new conent. I worked 4h on different nodes with different content (text & media)...
We use the SqlServerCE... <add name="umbracoDbDSN" connectionString="Data Source=|DataDirectory|\Umbraco.sdf;Flush Interval=1;" providerName="System.Data.SqlServerCe.4.0" />
The website is in dev. No backups or anything else is appearing....
Now I wanted to migrate it to the SQL prod server and I had seen the issue :(
XML Cache not persists to DB
Hi everybody!
I have updated my site. The frontend site looks good with the new content but on the backend it still the old content. If I republishing the content from the backend the new one will be replaced with the old stuff....
What can I do now?
Thanks for your help!
BR Manuel
Have you accidentally deployed your local AppData folder to your staging site? Or is this all on your local machine / live?
Hi Manuel,
Looks like your new content didn't save in the db. Can you check data in the app_data/umbraco.config ? Is it old there ?
Thanks
The new content was in the umbraco.config but not in the DB. If I republished the content from the content node the old content appears from the DB and in the umbraco.config file.
So I loose my new conent. I worked 4h on different nodes with different content (text & media)...
It's really strange, where is your db storing ? maybe some backup appears ?
We use the SqlServerCE...
<add name="umbracoDbDSN" connectionString="Data Source=|DataDirectory|\Umbraco.sdf;Flush Interval=1;" providerName="System.Data.SqlServerCe.4.0" />
The website is in dev. No backups or anything else is appearing....
Now I wanted to migrate it to the SQL prod server and I had seen the issue :(
is working on a reply...