Hi Eric,

I'm not sure about this. Is this an action like creating the Back button that we did before? I see now that the underline did go away but you're right, it happened globally even though I selected an individual page (what good is the page selection if it only affects the site globally?).

Now I need to adjust the color. Several links on different pages need to be different colors.

I see on the Page Source that the colors are:

A:link { color:#400080; text-decoration:none; }

A:visited { color:#400080; text-decoration:none; }

A:active { color:#400080; text-decoration:none; }

A:hover { color:#3362b0; text-decoration:none; }

If I change the html on the page source will it only affect this page? How do I open this page in the HTML Editor and change it?

Thanks.

Here is the page with the button and text link. http://orphanpress.coffeecup.com/contest.html

Hi Eric,

I was hoping to find and alter the code in the html to change the color on the buttons but for some reason fussing around with it simply caused VSD to crash. I then took your second code, made a file, altered the color and font and stuck it in like I was supposed to (I'm a bit slow sometimes ).

It worked like a charm.

Thanks again.

Greg

You may already know this, but ANY changes that you make to the .html files that VSD creates WILL NOT be recognized by VSD. SO, the next time you open your site with VSD to make an update, it will pull info from the .vnu file and your changes that were "manually made" will be gone!!!

Not sure why VSD "crashed" on you, maybe it's related to the manual editing, but I've not heard that one before...

Just would hate to see you make changes manually, publish, decide to update via VSD and realize your "manual changes are nixed".

I did not know this.

I've been trying different parameters of messing with the html in VSD for a couple of weeks now. All resulting in frustration. Maybe CC should put this in the fine print somewhere.

Thanks for telling me.

Tell you what?

I thought it was pretty obvious that VISUAL Site Designer is meant to be WYSIWIG - geared towards non-coders. If someone wants to do more than what's available within VSD, it's best to use the HTML tool - write your html/css/javascript ...whatever, outside of VSD and use the tool to insert the code. But leave VSD's generated html alone

It has been pretty well discussed on the forums over the last few years (at least). There are users that do edit the .html files after they are done with the initial design with VSD. And for them, if they know this info going in, or if they don't really care (maybe they just use VSD to "jumpstart" their site design, and want to 'code' the site from there out), it works... BUT, for the few that don't know this going in, it can be a real bear if they go to make changes via VSD later. "Where the xxxxx did my widget go? I know I edited the code to put that in there..." Well, yes you did, but since VSD uses the .vnu file, and that was untouched... abracadabra your change disappeared. And then in a panic the user will probably come to the forums and post a message about the problem

Yep. That be me. I actually didn't know anything about web design before VSD and now that I am getting my feet wet and learning some html I just figured (wrongly) that it would work in VSD as well. No problem. All part of the learning curve, I say. Just glad to know now that I can't edit VSD in HTML going forward.

I'm new to the forums, too. You all are seriously helpful! Thank you!!!

Greg - don't get me wrong... you can use the HTML tool within VSD to do some custom coding. And I believe you'd be real surprised with the things you can implement using it. What I'm pointing out is starting with VSD then going to a "purely" HTML Editor to tweak on the code that VSD produces. Again, while that CAN be done as well... It can cause problems

You can edit the HTML code that VSD generates as Phil stated. If your going to take this approach the best thing to do is to name the pages something other then what you what at the end result in VSD that way if you publish the site by accident you don't over write the pages that you altered with the editor. The other way is to publish to a sub folder then tweak the pages with the editor and then save them to the root. I'm not recommending anybody do this but if your mind is set on trying it you might as well have some direction to avoid some frustrations done the road. You'll learn about coding structure and before long probably get the itch to build some pages completely with the editor.

The HTML tool in VSD can accomplish pretty much everything anybody might need as far as I can tell. If there's something that can't be done then the editor is there waiting.