In chapter 11 p 410 readers are alerted to the problem that when you make changes by using Dreamweaver's server behaviours in ASP pages you might get the error message that.. You have made changes to code that is not marked as editable. If you ........ until then? Yes /No

Authors advise that this error message is wrong and hopefully the problem will be fixed in a future service release of Dreamweaver.
However this message and loss of changes occurs frequently as you progress thru' Chapters 11 on. In addition another error message when using server behaviours in ASP pages also pops up frequently with the message.

Making this change would require changing code that is locked in a template or translator. The change will be discarded

The result is all your changes as the message states vanish. Saving and closing then re-opening files after each minor change in anticipation that you are going to get the discard message does not solve the problem- as even if you do this the problem still occurs. As the authors already note the modifications trying to be made are in regions of the template that you are allowed to edit.

Would find it difficult to believe that I am alone with this problem- anyone any advice please?

Hi Hothers,

Like I said in the book, this is a very disturbing problem with Dreamweaver MX. At times, it makes it almost impossible to apply the required behaviors. Often the only way to get it to work correctly, is to know in advance exactly what you need to do, and create the page in one single action, not opening any of the SB dialogs more than once.
However, when developing things, this is of course not a very good solution.

Did you upgrade your version of Dreamweaver to 7.01? The service releases fixes a lot of, but not all, problems in this area.

Frustrating as it might be: you can be assured you're not alone.... ;)

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: Here In My Room by Incubus (Track 13 from the album: A Crow Left To The Murder) What's This?

Hi Imar
Thanks for the quick response. Yes I have updated to 7.01 but as you know the problem is still there. As you say though not much we can do at the moment - though it is very annoying to keep losing the changes you have made. Thanks again for the info.
Regards
Hothers

Yeah, it's a pain.

If I had to choose between the Server Behaviors or the Template feature, I think I would drop templates. In bigger Web sites, using include files for a generic look and feel may be a better solution anyway, so if you drop templates in favor of includes, you may get things to work again.

It's a pity, as the idea behind the templates feature is really great....

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Gurrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr rrr

“Making this change would require changing code that is locked by a template or a translator. The change will be discarded.”

Right being extremely annoyed at this problem I done what I usually do and got really frustrated and kept playing with the saving combinations so I could preview my site.

And I think I may have a sort of solution

Go back to your template and validate your code make sure it is working there first. Save all changes and update offspring files. If it will not allow you to change the code........
Copy and past into a new document
Save as html
Validate this
And save over your template thus recreating it
*make sure you have a copy of the code somewhere*

Check your files now it sometime works at this stage.

For the especially stubberin versions of DW you may need to do the same with the offspring files as well. A process which will make taking a sick day very promising.

Can anybody please tell me if this error has been fixed in the new DW 8 as I was considering upgrading?

ilikecake
www.ilikecake.net


www.ilikecake.net

Hi there,

Some of the problems with templates and server behaviors have been fixed in DW 8, but not all of them.

Probably the best thing to do is download a trial version and see for yourself. Many of the other improvements in DW 8 make it a worthwhile upgrade....

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: Ronnie Gaat Naar Huis by Spinvis (Track 5 from the album: Spinvis) What's This?

I am now in the same boat on this. I have a region that is editable and does not allow me to make my change. Very disturbing grrrrr. I will try another include file

When you create the template, do you leave the text 'EditRegion1' in?
Try removing it in the template

Version 8 still has the problem and as far as I can see has little to recommend it.

I've experienced the same problem not being able to edit the code of my documents based on templates using Dreamweaver 8(Mac). I have tried the various recommended fixes without success. I figured that something specific must have changed, because I've used templates successfully in the past with dreamweaver MX 2004. The first thing I tried was to just 'detach' the document from the template and was able to edit the code. Ok, that was not really a solution, but at least I was able to make the code modifications I needed. So, back to trying other things.

I then noticed that I was able to make modifications in the 'design' view, but not in code view. I could copy elements from another page in design view and paste them into the template-based document, and not get the uneditable region error. I could also make modifications in the preferences panel without inducing the error. But, I still needed to be able to edit the code directly. One other thing I noticed was that when I did edit the code directly in code view, and then induced the error, after cancelling the error, when I tried to select some of the code in code view, there seems to be a bug that is highlighting the wrong portion of the text. So it seems that Dreamweaver might having a problem identifying what portion of the code is within the editable region, and what isn't. Finally I just started altering anything within Dreamweaver that might be having some effect on how things are displayed in each view. The first thing I tried was to turn off the display of CSS styles: "View > Style Rendering > Display Styles". I tried editing the code, and voilà, it worked! I turn of CSS styles, edit the code, turn styles back on, and no error.

My conclusion is that Dreamweaver has a bug somewhere relating to the displaying of CSS styles. It's a little bit of a pain to toggle back and forth. But it works for now. If anyone comes up with any other permanent fixes, I'd appreciate the info.

PeterD
info@integralww.com