Errors galore in DW CS3

Question

I have been developing with DW since 1.0 and have upgraded
through every version. I have been trying to use CS3 since its
release, however I find that due to so many issues I revert back to
DW8.
CS3 - Crashes continuously - Yes I deleted the appropriate
file and restarted. It is better but still crashes.
CS3 - I open an existing webpage and try to apply a new
behavior, any behavior - Sorry making this change would require
changing code that is locked by a template or translator. This
change will be discarded.
CS3 - Tried to implement the highly touted Spry assets - a
ton of extra work for an extremley boring effect.
CS3 - Yep, just crashed again.
CS3 - Never imported all of my site definitions and ended up
having to re-set them up - about 40 thats a lot of time.
CS3 - In design view when you select a table or element it
places a HUGE measuring tool over the top of the box which blocks
your view and does not allow for you to select anything in that
region.
Honestly, since the move to Adobe this product has quickly
gone down hill. Multiple upgrades with absolutely no reasonable
improvements, yet a less stable application. Not to mention our
complete history of purchases for Macromedia DW purchases and Adobe
purchases have never come together in our online account making
setting up a new computer difficult.
Is this a B$tch session and a rant, yes, absolutely it is.
Its just so dissappointing to have to pay for upgrades that are
totally un-usable. I wonder how many other developers are suffering
these same issues, how many have reverted back to DW 8, how many
have found real value in the last few "upgrades".
I know there are little to no alternatives to DW, or Adobe
products in general.... perhaps this is the problem.
Discovery

Answer 1

> With previous versions it mattered not where you sat an
> html site.
Most likely your previous versions didn't have testing
servers defined.
> If you need to change a server behaviour at all, best to
delete all the
> old
> behaviour code from the page before trying to make any
modifications.
If you are speaking of changing a legacy server behavior,
yes, that's a good
suggestion. If you are speaking of changing a CS3 SB, then I
have not found
this to be the case.
> You need some coding experience to use it properly.
Indeed.
> Adobe could make lots more profit if gave that a bit of
thought.
This is a matter of opinion. I tend to disagree. Publishing a
document
like that is a huge drain on resources.
> Selecting the content of input fields is best done in
code view, as if you
> try
> to do it in design view you have a fifty fifty chance
that any insert will
> be
> in the WRONG place - which often accounts for the
message regarding
> templates
> and translators.
I can't say this has ever happened to me.
> Some browsers will not work in F12 test mode
How bizarre. Which?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"whatalotofrubbish" <[email protected]>
wrote in message
news:[email protected]...
>I also have been using Dreamweaver since around 2002. The
most stable
>version
> was version 3, but then it was a html only program.
>
> Overall, Cs3 is about as stable as MX but it does come
up with lots of
> strange
> errors, such as "Please move this file to your defined
site" - this on a
> file
> created within and saved to the site. Fixed by moving
the html site into
> my IIS
> webserver folder root. With previous versions it
mattered not where you
> sat an
> html site.
>
> If you need to change a server behaviour at all, best to
delete all the
> old
> behaviour code from the page before trying to make any
modifications.
> Then check the code, because as sure as eggs are eggs
there will be
> remnants
> in the page which will cause problems. Not good for
people who have not
> much
> coding experience.
>
> However, I now think that CS3 has moved on so that it is
no longer
> suitable
> for designers to use. You need some coding experience to
use it properly.
> After
> returning to 8 for a while, I bought the Dreamweaver CS3
Bible to read
> while on
> holiday, and found that there was a bit more to CS3 than
met the eye.
> There is
> a lot to say for a proper works manual at a sensible
price. Adobe could
> make
> lots more profit if gave that a bit of thought. After a
long day at the
> keyboard, it is a pain to have to read Acrobat files to
learn about your
> software. Much better with a good book.
>
> Selecting the content of input fields is best done in
code view, as if you
> try
> to do it in design view you have a fifty fifty chance
that any insert will
> be
> in the WRONG place - which often accounts for the
message regarding
> templates
> and translators.
>
> Spry menus are to say the least a little touchy and
unreliable - 1.6
> included.
> I gave up with them and bought a third party extension
from PVII which
> works
> every time with no problems.
>
> The best part of DW CS3 is the CSS and the results pane.
For the first
> time I
> can get a sticker from the CSS people to say my code is
correct css. It is
> also
> compatible with most browsers - according to
Dreamweaver. Some browsers
> will
> not work in F12 test mode, so I have to upload to the
web before I can
> test in
> Opera for instance.
>
> But when the price in the UK is more than double what it
is in the states,
> I
> will be trying a free download very thoroughly before
purchasing the next
> version.
>
> Howard Walker
>