VG se följande FAQ-artikel som tar upp det mesta kring system.css och system_template.css: http://www.episerver.com/templates/faq.aspx?id=4112

Skulle vara jätteintressant att läsa...... om bara länken fungerade, och inte svarade med Access denied!!!

Hittade igentligen ingen lösning på problemet. Hjälpte varken med att ta bort/lägga till system.css och dessutom se till att Not Found pekade rätt. Min lösning på problemet blev att ta bort instansen av EpiServer från IIS och göra en nyinstallation. Nu fungerar css-filerna som det ska, men... En extern användare (alltå någon som surfar in på min maskin och EPiServer instanser är igång) får inte upp webplatsen (explorer svarar med sidan kan inte visas). Pekar jag om Standardwebplatsen i IIS mot EpiServer directoryt och startar den instansen i stället för EPiServers egna, kan den externa användaren surfa på webplatsen editera m.m. men nu funkar åter igen inte stylesheet. Har kontrollerat inställningar i både den nya IIS-instansen och StandardInstansen. (De är identiska) Någon som har en idé varför det blir såhär?

Jag hade samma problem när jag gjorde en manuell upgradering. css:en hittades inte. Felet låg i att jag missat att sätta "Anpassade felmedelande" till rätt. 404:an skall sättas till URL /epi/Util/NotFound.aspx

Hmm.. ok, det var det där med URL jag missade... Pekade ut filen istället... Nu fungerar det att köra standardwebplatsen med styleSheet! TACK för hjälpen Tobias!

Ni som inte kan komma åt FAQ-artikeln jag postade länk till tidigare, nedan är hela innehållet i artikeln. (Obs, FAQ-artiklarna blir inom kort tillgängliga för alla i forumen) EPiServer 4.50 and later includes some changes in the Util/styles directory: system.css has been replaced by system_template.css linkeditor.css has been replaced by linkeditor_template.css * What is the reason for these changes? EPiServer 4.50 introduced a feature called relocation that allows administrators to relocate virtual directories. For example, the previously hard-coded "edit" directory in EPiServer can now be changed to any location, such as "some/other/unkown/directory/4711". Relocation requires that all URLs are dynamic (the addresses are solved runtime), including URLs in CSS files. However, the CSS standard does not support dynamic content, so EPiServer uses a custom solution that does not break any standards to accomplish this. A part of the solution is to rename CSS files that have dynamic content to "_template.css". * Should I download system.css from somewhere? No, the system_template.css is actually system.css, so you do not need a separate system.css. * What happens if there is a system.css and a system_template.css? The system.css file is always loaded first, if it exists. This is to ensure backward compatibility. If no system.css can be found, system_template.css will be loaded. * What happens when the browser requests system.css? The dynamic CSS technology in EPiServer is totally transparent to IIS and the browser; they are completely unaware of what is going on behind the scenes. When the browser makes a request for system.css, it is system.css that is returned, from the browser's point of view, even if it really was system_template.css that was loaded on the server. * Which one should I refer to in code, system.css or system_template.css? Always refer to system.css. Never refer directly to system_template.css. If you refer to system_template.css directly, IIS will load system_template.css and send the content unmodified back to the browser. EPiServer will not have a chance to intercept the request. Since _template.css files may contain dynamic content (which is not supported by the CSS standard), the page loading may crash in the browser. So, to avoid any problems, always refer to "/Util/styles/system.css". * Will it work if I rename system_template.css as system.css? No. You will get into trouble, for the same reasons mentioned above. * How does the dynamic CSS technology work? When the browser requests for a file and IIS looks for the file on the server, one of two things can happen; either IIS finds the requested file and sends it back to the browser or it finds nothing and the 404 HTTP error is raised. When the error occurs, EPiServer's SpiderSupport HTTP module analyzes the error. If it sees that a request for a "_template.css" file was made, it tries to load the CSS file. If the file is found, the 404 error is canceled, all dynamic content in the loaded file is replaced with runtime values and the content is sent back to the browser, disguised as the original CSS file that the browser requested. * Why do I get the HTTP error 404 - system.css cannot be found? If you get this error, the custom error 404 in IIS is not configured correctly.