Can anyone confirm that changes to css files on the filesystem aren't committed to the database?
So after I make a change to a css file on the filesystem, if i load it in the editor in the umbraco backend I don't see the changes i made seconds/minutes ago?
When you modify on disk it will not save to the database. You need to go /settings/StyleSheets/ then open there and press Save. This will save to the database.
Should work fine. I always edit my files in the filesystem, and almost never in the Umbraco backend (unless it's a small change). Are your file saved the right way.
And not something like "Read only" or are your files in source safe and edited outside the source safe?
In umbraco v3 there was a one-way sync from umbraco to the filesystem. If you edited the file directly umbraco would not 'notice' it and the next time you opened the file in umbraco it would not reflect the changes on disk. When you saved the file from inside umbraco it would over-write the file on disk.
But in umbraco v4 there is a two-way sync. You can edit the file in umbraco or on disk and the next time you open it any changes will be noticed automatically. The only time this wouldn't work is if, by editing the file on the filesystem directly, the file permissions or ownership changed and the website's application pool owner could no longer read/update it properly.
In umbraco v4 you should be able to do the following:
Create a CSS stylesheet file in umbraco
Save it in umbraco
Open the file in Visual Studio / Notepad++ / you-favorite-text-editor from the /css folder
Edit the file and save it
Click the Settings icon in umbraco, navigate to the Stylesheets section
Re-open the css file in umbraco by clicking on its name YOUR CHANGES SHOULD APPEAR HERE
Make more changes and save the css file in umbraco
Return to your text editor... it should notify you that the file has been changed and ask you to reload it YOUR CHANGES SHOULD APPEAR HERE AS WELL
That's how it should work for CSS, JS, XSLT, and MASTERPAGE TEMPLATES.
maybe not really a bug but it can be nasty when you encounter it:
if someone edits a css file in an external editor and adds css
classes below the /* EDITOR PROPERTIES - PLEASE DON'T DELETE THIS LINE
TO AVOID DUPLICATE PROPERTIES */ comment, all this content gets deleted
when you open this file in the umbraco css editor and save the file
again.
this can result in loss of the added css rules.
I propose an alteration of the message warning users not to edit any part below this line, nor add additional css below it.
Editing CSS files on the filesystem
Can anyone confirm that changes to css files on the filesystem aren't committed to the database?
So after I make a change to a css file on the filesystem, if i load it in the editor in the umbraco backend I don't see the changes i made seconds/minutes ago?
we seem to be loosing work this way...
Comment author was deleted
Just tried this on a v4.0.3 and it works fine here, it loads the changes made on filesystem.
Regards,
Tim
When you modify on disk it will not save to the database. You need to go /settings/StyleSheets/ then open there and press Save. This will save to the database.
Should work fine. I always edit my files in the filesystem, and almost never in the Umbraco backend (unless it's a small change). Are your file saved the right way.
And not something like "Read only" or are your files in source safe and edited outside the source safe?
In umbraco v3 there was a one-way sync from umbraco to the filesystem. If you edited the file directly umbraco would not 'notice' it and the next time you opened the file in umbraco it would not reflect the changes on disk. When you saved the file from inside umbraco it would over-write the file on disk.
But in umbraco v4 there is a two-way sync. You can edit the file in umbraco or on disk and the next time you open it any changes will be noticed automatically. The only time this wouldn't work is if, by editing the file on the filesystem directly, the file permissions or ownership changed and the website's application pool owner could no longer read/update it properly.
In umbraco v4 you should be able to do the following:
YOUR CHANGES SHOULD APPEAR HERE
YOUR CHANGES SHOULD APPEAR HERE AS WELL
That's how it should work for CSS, JS, XSLT, and MASTERPAGE TEMPLATES.
cheers,
doug.
maybe not really a bug but it can be nasty when you encounter it:
if someone edits a css file in an external editor and adds css classes below the /* EDITOR PROPERTIES - PLEASE DON'T DELETE THIS LINE TO AVOID DUPLICATE PROPERTIES */ comment, all this content gets deleted when you open this file in the umbraco css editor and save the file again.
this can result in loss of the added css rules.
I propose an alteration of the message warning users not to edit any part below this line, nor add additional css below it.
is working on a reply...