Skip to main content
TerumoCV
TerumoCV
Participant
September 6, 2018
Question

CSS

  • September 6, 2018
  • 1 reply
  • 318 views

I had a perfectly fine working website until that last two upgrades from Dreamweaver. All the pages where based on templates, which had the CSS links in them. Design preview worked great. Live preview worked great. Now, that is all gone.

I call up an existing page and it no longer previews correctly. CSS styles no longer appear in the properties dropdown. This has been an issue since the last to upgrades.

Now, the same site, with the same pages, will not find the CSS links. I've spent so much time trying to resolve this issue I'm ready to loose it. Does anyone know what when wrong with Dreamweaver?

Due to the nature of my website, I work directly from the server. It is then updated thru a version control system to the live server. This is a requirement of our quality system. I can not use the tools in DW to do this. I don't know if that is the issues, but Dreamweaver seems to want to force the use of their system.

Help!

This topic has been closed for replies.

1 reply

Jon Fritz
Community Expert
Jon FritzCommunity Expert
Community Expert
September 6, 2018

Newer versions of DW have become more and more dependent on clean and valid code. HTML errors that older versions of DW used to skip over and ignore are show stoppers now, however that shouldn't affect the actual browsers.

Chances are some small error the newer versions of DW couldn't reconcile in your Template file is stopping the program from updating your child pages correctly and you've uploaded them to your server.

It's all just guesswork without seeing the site though. Could you please post a link so we can take a look?

If not, make sure to run your Template pages through the validation tool under File > Validate > Current Document (W3C) and clean up any issues showing there. Hopefully cleaning the code of any error will bring it all back for you.

TerumoCV
TerumoCVAuthor
Participant
September 6, 2018

This is for the intranet, so I'm not able to make it public. The code was valid at the time of the 2017 upgrade, when this issue first occurred. I'll go back and validate a template and start with that.

I think I need to give up on my existing site and start with a complete new set of CSS. I was hoping to avoid that. This post was my last grasp at finding a solution.

Nancy OShea
Community Expert
Nancy OSheaCommunity Expert
Community Expert
September 6, 2018

1. Did you define your local site folder?  If not you must do that now by going to Site > New Site.

2.  Open the Template.dwt file.  Is the path to CSS file correct?

Assuming your CSS file is in a subfolder called styles, It should resemble this with 2 leading dots and a slash.

../styles/my_css_file.css

However child pages spawned from Templates and saved to the site's root will not contain the leading dots & slash.

styles/my_css_file.css

Nancy O'Shea— Product User & Community Expert
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices