Locked

Dreamweaver migrating to newer versions

New Here ,
Jul 03, 2021 Jul 03, 2021

Copy link to clipboard

Copied

Is there any special procedure, generally, for updating the code to a newer version, say from Dw 2017 to 2018?

In the Site manager the correct ste-file has been imported and the internal styling from <style> and media queries work properly. However, the external, linked CSS-file sitting in the same root directory is no longer working when checked in a browser, although in Code-Live view it does. Any idea?

 

 

Views

207

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 5 Correct answers

Adobe Community Professional , Jul 06, 2021 Jul 06, 2021

There's no point in troubleshooting style issues until you resolve ALL code errors and warnings. Then upload new pages to your server.  Refresh your browser or use a different one to test.

https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.saevfors.se%2FContact.html

 

MISSING IMAGES:  the ones that don't display are 404 NOT FOUND on server.  Try uploading them again.

http://www.saevfors.se/Images/Solar_canopy.jpg
http://www.saevfors.se/Images/Bamboo_structure_solar_panels.jpg

 

Likes

Translate

Translate
Adobe Community Professional , Jul 06, 2021 Jul 06, 2021

Right now, you have a direct link to your hard drive for your CSS file...

"F:\Soft\Web__July_2021/Ing_June2021.css"

 

That will only ever work if the viewer also has that file, set inside those same folders, on their F drive (ie. it will never work). 

When making updates, was a Site Definition created or imported into the newer version of the program first, or did someone just go in and make modifications to pages?

Without creating a Site Definiton, or selecting an already created one from the File

...

Likes

Translate

Translate
Adobe Community Professional , Jul 13, 2021 Jul 13, 2021
quote

Only the Media Query is still failing, on my Sony Xperia 4L it’s till on two columns.

 

Did you add the viewport meta to your document's <head> tag?

 

The first few lines of your document should resemble this with a viewport meta for smartphones.

<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Unique Page Title</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">

 

Likes

Translate

Translate
Adobe Community Professional , Jul 13, 2021 Jul 13, 2021
quote

Did you add the viewport meta to your document's <head> tag?

By @Nancy OShea

 

yes the line is present but contains error

 

<meta http-equiv="Content-Type" content="text/html; charset=utf-8"; name="viewport"; content="width=device-width,initial-scale=1"/>

 

 

look all the semicolons are in error

the first one is located outside the double quote it should be inside, near the caracter 8

the second one, the one after viewport, should be removed

Likes

Translate

Translate
Adobe Community Professional , Jul 18, 2021 Jul 18, 2021

This file is 404 Not Found on Server.

https://www.saevfors.se/Images/Home_page_bckgr.jpg

Upload it again.  Also check the case and path to ensure they are both correct. 

 

 

 

Likes

Translate

Translate
Adobe Community Professional ,
Jul 03, 2021 Jul 03, 2021

Copy link to clipboard

Copied

There's nothing special to migrate to newer versions, but 2017 to 2018 is now moving to 3 year old software. Dreamweaver at its core is just a text editor so you could use any HTML editor to be able to modify your site.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 03, 2021 Jul 03, 2021

Copy link to clipboard

Copied

Hi @ingo9,

1. The current version of DW CC is 2021, not 2018. 😉 

 

2. If the CSS isn't displaying, there is a code error somewhere or the stylesheet isn't where it needs to be according to the path contained in your code.

EXAMPLE: 
<link href="folder/stylesheet_name.css" rel="stylesheet" media="screen">

 

We can tell you exactly what the problem is if you post a URL to your problem page for us to see.

 

3.  Use the W3C Code Validation Service to check your code for errors:

============

HTML - https://validator.w3.org/

CSS - https://jigsaw.w3.org/css-validator/

 

Nancy O'Shea, Adobe Product User & Community Professional
Alt-Web Design & Publishing ~ Web : Print : Graphics : Media

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 04, 2021 Jul 04, 2021

Copy link to clipboard

Copied

Hi and thanks for quick response,

I did W3C validation but cannot figure out why the Parse Errors at lines 9, 129.

Please have a look at  this 

http://www.saevfors.se/Contact.html

The CSS seem to work now but layout  of right side still a trouble, not lining up in desk screen mode.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 06, 2021 Jul 06, 2021

Copy link to clipboard

Copied

You have no selector on line 7-9. If you want to affect all items in your html with the box-sizing property, you'll need to add a * before the opening bracket as the selector for that property/value set.

Going from...

{
box-sizing:border-box;
}


to...

*{
box-sizing:border-box;
}

 

On line 129, you are missing a closing curly bracket for your media query. Adding } to line 129 should fix that error.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 06, 2021 Jul 06, 2021

Copy link to clipboard

Copied

Thanks a lot. We are getting there with your comments. Remaining problems:

Still the external CSS in the Root folder does not deliver properly. (images not floating left/right as designed)

And the images don’t always show up, although the Site manager path to Images has been set properly.

 

http://www.saevfors.se/Contact.html

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 06, 2021 Jul 06, 2021

Copy link to clipboard

Copied

There's no point in troubleshooting style issues until you resolve ALL code errors and warnings. Then upload new pages to your server.  Refresh your browser or use a different one to test.

https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.saevfors.se%2FContact.html

 

MISSING IMAGES:  the ones that don't display are 404 NOT FOUND on server.  Try uploading them again.

http://www.saevfors.se/Images/Solar_canopy.jpg
http://www.saevfors.se/Images/Bamboo_structure_solar_panels.jpg

 

Nancy O'Shea, Adobe Product User & Community Professional
Alt-Web Design & Publishing ~ Web : Print : Graphics : Media

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 06, 2021 Jul 06, 2021

Copy link to clipboard

Copied

Right now, you have a direct link to your hard drive for your CSS file...

"F:\Soft\Web__July_2021/Ing_June2021.css"

 

That will only ever work if the viewer also has that file, set inside those same folders, on their F drive (ie. it will never work). 

When making updates, was a Site Definition created or imported into the newer version of the program first, or did someone just go in and make modifications to pages?

Without creating a Site Definiton, or selecting an already created one from the Files window dropdown menu, many errors like this will occur because DW has no means of understanding what you want it to do.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 08, 2021 Jul 08, 2021

Copy link to clipboard

Copied

Dear Dw community,

I just wanted to thank you all for useful support all along. It seems that now my revamped website is up and running, the remaining problem with a Red Hat Linus blockage when going out live on internet is with my service provider to sort out. However, they do say that knowing the PHP version is important!

If you’d like to know about the CSS mystery I had, it turned out that the contents had completely vaporized somehow! I just wrote a new CSS-file and this was enough. As often with computer problems it helps to start again from scratch, remake and restart with a new filename.

Most of you as professionals probably find us amateurs extremely ignorant, but with your help we also learn and perhaps later on we can help others in this community!

/Ingemar

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 08, 2021 Jul 08, 2021

Copy link to clipboard

Copied

Ingemar,

I can't think of any reputable Linux hosts that don't support PHP code.  Pretty much all Linux/Apache web servers are configured with PHP & MySQL support whether they are Red Hat OS or not.   

 

Exactly what kinds of problems are you having with PHP? 

 

To find out which version of PHP your server supports, copy & paste the following code into a new PHP file and saveAs test.php, then upload it to your server.  Browse to the test.php file on your server to run the script.

 

<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>PHP Info</title>
</head>
<body>
<?php phpinfo() ?>
</body>
</html>

 

Nancy O'Shea, Adobe Product User & Community Professional
Alt-Web Design & Publishing ~ Web : Print : Graphics : Media

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 08, 2021 Jul 08, 2021

Copy link to clipboard

Copied

Thanks,

With Dw v. 2018 i got the PHP info version 7.1 xposed, so ISP knows and can adapt. I just wait and see what they figure out.

Cheers, Ingemar

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 08, 2021 Jul 08, 2021

Copy link to clipboard

Copied

DW does not have PHP installed.  That is a misconception.  It's your local testing server that has PHP. 

 

Ideally, whichever local server you use (Xampp, Mamp, Wamp, etc...) should use the same PHP version & configuration as your remote server's.  You'll have fewer surprises that way. 🙂

 

Nancy O'Shea, Adobe Product User & Community Professional
Alt-Web Design & Publishing ~ Web : Print : Graphics : Media

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 13, 2021 Jul 13, 2021

Copy link to clipboard

Copied

Adobe Support Community

The RED HAT problem was magically resolved. Somewhere down the road my original index.html was turned into capitals. As Linux is case sensitive everything turned RED HAT. The Web Hotel service provider just changed back to index.html and everything works fine.

Only the Media Query is still a bit failing: It is supposed to stack two columns vertically into one at 768px. In Dw code-live it works fine, but when checked on my smart phone Sony Xperia 4L it’s till on two columns.

Anyway I’m glad the website is open again. Thanks, Ingemar

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 13, 2021 Jul 13, 2021

Copy link to clipboard

Copied

quote

Only the Media Query is still failing, on my Sony Xperia 4L it’s till on two columns.

 

Did you add the viewport meta to your document's <head> tag?

 

The first few lines of your document should resemble this with a viewport meta for smartphones.

<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Unique Page Title</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">

 

Nancy O'Shea, Adobe Product User & Community Professional
Alt-Web Design & Publishing ~ Web : Print : Graphics : Media

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 13, 2021 Jul 13, 2021

Copy link to clipboard

Copied

quote

Did you add the viewport meta to your document's <head> tag?

By @Nancy OShea

 

yes the line is present but contains error

 

<meta http-equiv="Content-Type" content="text/html; charset=utf-8"; name="viewport"; content="width=device-width,initial-scale=1"/>

 

 

look all the semicolons are in error

the first one is located outside the double quote it should be inside, near the caracter 8

the second one, the one after viewport, should be removed

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 17, 2021 Jul 17, 2021

Copy link to clipboard

Copied

Hi, thanks Nancy for very useful code for 1 column stacking in smartphones.

I have practically no more problems with my updated website now.

Only the missing background image in the index.html. Maybe due to remaining caches in Chrome which seem very difficult to get rid of. (The Chrome forum is not as productive as this one) If you have an idea also about this, I send you the index.html. The said bckgr image resides in /Images in the site folder.

Dw shows it correctly in the Real time preview for Chrome, whereas in live internet the image is dropped. The same story in Firefox.

When I picked CSS chunks from previous index files that did work properly I noticed that the body{…} lack the preceding period and is blue. However, I tried both with/without a period. No way, please have a look , Greetings Ingemar

https://www.saevfors.se/index.html

 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Jul 18, 2021 Jul 18, 2021

Copy link to clipboard

Copied

This file is 404 Not Found on Server.

https://www.saevfors.se/Images/Home_page_bckgr.jpg

Upload it again.  Also check the case and path to ensure they are both correct. 

 

 

 

Nancy O'Shea, Adobe Product User & Community Professional
Alt-Web Design & Publishing ~ Web : Print : Graphics : Media

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 05, 2021 Aug 05, 2021

Copy link to clipboard

Copied

LATEST

Thanks all of you! Everything works perfectly now...

Just some mess with accents, so I start a new thread.

Ingear

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines