close ad
 
Important WebAssist Announcement
open ad
View Menu

Technical Support Forums

Free, outstanding support from WebAssist and your colleagues

rating

some edits to .css files don't "take"

Thread begun 8/04/2009 12:32 pm by rpttrsn300655 | Last modified 8/05/2009 8:02 am by rpttrsn300655 | 1915 views | 3 replies |

rpttrsn300655

some edits to .css files don't "take"

I have made several changes to the .css files, most of which show up without problem.

However, I have made one change to the template and some of the new css rules necessary to make that change work will not update when files are viewed in a browser.

I moved the searchbox from the #topnavigation div to the #footer div, copying the code from one place to another. I then copied the css rules pertinent to the searchbox in the topnavigation location, and pasted those css rules at the bottom of the mystyles.css file.

I changed the css from the default:

#outerWrapper #topNavigation #searchBox {
float: right;
margin: 6px 7px 0 0;
overflow: hidden;
width: 300px;
}

#outerWrapper #topNavigation #searchBox #S_ProductName {
float: right;
width: 200px;
}

#outerWrapper #topNavigation #searchBox #Search {
float: right;
margin-left: 7px;
width:62px;
height:29px;
}


TO:

#outerWrapper #footer #searchBox {
float: right;
margin: 6px 7px 0 0;
overflow: hidden;
width: 300px;
}

#outerWrapper #footer #searchBox #S_ProductName {
float: right;
width: 200px;
}

#outerWrapper #footer #searchBox #Search {
float: right;
margin-left: 7px;
width:62px;
height:29px;
}

This addition works in design view and live view. However, on previewing in a browser, none of that "new" css is included, leaving the #searchbox in the footer misplaced. It's in the footer, but not positioned as indicated by the css that should be there. The new css rules are actually not in the .css files that are styling the browser views (according to firebug and "web developer tools").

It occurs to me that all of the changes to the .css files that I have implemented so far have only been to change values for existing declarations, this is the only time that I have actually added new css rules to a stylesheet. I know that the new rules are actually addressing the proper element (#searchbox) because design view proves it, but the browser preview doesn't have access to that new css.

Am I missing something? I understand that the index.php file is the only one not governed by the main template, and that the rest of the pages are under the rule of this template. However, I've made this change on both the index.php and main.dwt.php files (and updated all the "linked" pages), and the #searchbox is sort of where I want it, but the styles are not updated. What's stopping this updating, and why only on browser preview, not design view and liveview?

Thanks in advance for any help,

Robert

Sign in to reply to this post

Jason ByrnesWebAssist

Only thing I can think is that the mystyles.css file is not uploaded.

can you post a link where I could see the page in a browser to investigate?

Sign in to reply to this post

rpttrsn300655

powerstore is on local testing server

Jason:

This powerstore is in its early stages, and is on a local testing server, so the files are the files. I'm working directly on the site files, aren't I?

There is no uploading, which makes the whole thing so hard to figure.

The source code reflects the change by moving the #searchbox from the topnavigation to the footer, but the accompanying css changes are not applied, even though the files are in the same folder on the local testing server.

I guess I'm not getting how design view and liveview can show the changes (source code and css), and a local browser accessing a local server does not show all the changes.

I'll see if I can upload the site to a test location tomorrow.

Thanks,
Robert

Sign in to reply to this post

rpttrsn300655

solution update

Well, caches must have been reset, testing servers restarted, or something, because this morning everything is where it should be. I could swear that I had restarted everything yesterday when the css wouldn't update, but today we are good. So, I guess it's encouraging that it's okay, but I've never had to go to such lengths for what seems like a routine operation.

Jason, thanks for your time,

Robert

Sign in to reply to this post

Build websites with a little help from your friends

Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.

Build websites from already-built web applications

These out-of-the-box solutions provide you proven, tested applications that can be up and running now.  Build a store, a gallery, or a web-based email solution.

Want your website pre-built and hosted?

Close Windowclose

Rate your experience or provide feedback on this page

Account or customer service questions?
Please user our contact form.

Need technical support?
Please visit support to ask a question

Content

rating

Layout

rating

Ease of use

rating

security code refresh image

We do not respond to comments submitted from this page directly, but we do read and analyze any feedback and will use it to help make your experience better in the future.

Close Windowclose

We were unable to retrieve the attached file

Close Windowclose

Attach and remove files

add attachmentAdd attachment
Close Windowclose

Enter the URL you would like to link to in your post

Close Windowclose

This is how you use right click RTF editing

Enable right click RTF editing option allows you to add html markup into your tutorial such as images, bulleted lists, files and more...

-- click to close --

Uploading file...