It shouldn't happen. What happens if you press F12 (preview) can you see the changes?
When you say saved and uploaded, do you mean uploaded to a remote server?
Are you referring to Design View in DW or Preview in a Browser?
Yes, I uploaded to the server, but the radio buttons still didn't work. Note: In order to test it, I had to upload to the server, because the server side of the php process was necessary in order for me to receive an e-mail when visitors to my site clicked the 'Submit' button. Ultimately, that is what I was trying to accomplish (i.e. to receive an e-mail when users clicked on the 'Submit' button). I do have it working now, but only after I made some changes in the code. And, believe me, that was very lucky for me, because code is not a strength of mine. Basically, I had one radio button that was working, and one that wasn't, so I compared the code of each, and altered the one that wasn't working. But, the part of the code that I changed didn't seem to have a Design View counterpart (i.e. I couldn't find where in the Property Inspector to make the change).
I hope I've made sense here. I was wondering if, perhaps, Design View has shortcomings; people on this forum have told me I should/need to get used to working with code. I figure that's because Design View doesn't always allow you to do what you need/want to do... ??? Just wondering.
Design View isn't 100% perfect. That said, when things go wrong in Design View, it's almost always caused by malformed code. In Code View, if you see code inside blocks of Yellow, that's DW's way of telling you your code is malformed (missing an opening or closing tag, for example).
Use the code validation tools below to help identify errors.
HTML Validator - http://validator.w3.org
CSS Validator - http://jigsaw.w3.org/css-validator/
Thanks, Nancy. I will try out the validators. In the meantime, you mentioned that when Design View doesn't work properly, it's almost always because of malformed code. But, I did not write one word of code; all my code was created by Dreamweaver in Design View. Is it possible that, because of much juggling/changing/inserting and deleting etc. (within Design View), that the code generated by Dreamweaver itself could have become corrupted/flawed?
I did not write one word of code; all my code was created by Dreamweaver in Design View. Is it possible that, because of much juggling/changing/inserting and deleting etc. (within Design View), that the code generated by Dreamweaver itself could have become corrupted/flawed?
DW isn't a mind reader. It uses a basic logic to write code for you based on what you tell it to do. If your workflow is helter-skelter, the resulitng code could be too. Use Split View and pay attention to what DW does to your code when you delete something from a page. Often it does it correctly, but sometimes it leaves stuff behind that needs to be removed manually. That's why being able to work with code is essential.