Skip to main content
Known Participant
June 19, 2006
Question

DW8.02 bugs - found the problem, it's safari

  • June 19, 2006
  • 8 replies
  • 591 views
Ok, I have to appologize for my rant about Dreamweaver 8.02 killing my apps.
It actually does all work fine just not using the Safari Browser on Mac. Firefox works perfectly.
Safari cannot deal with Dreamweaver's new code.
This topic is closed to new replies. Start a new post to keep the conversation going.

8 replies

riprod7Author
Known Participant
June 19, 2006
WAIT guys!
Forget the extension completly. Remove it from the equation.
Just create a form that inserts a record and have it have one fiel field in it.
IT DOES NOT WORK ON SAFARI.

There is no Javascript on the page, so it is something to do with the File Field, insert record and Safari.

Works fine in Firefox.
Inspiring
June 19, 2006
Let the finger pointing begin.


"riprod7" <webforumsuser@macromedia.com> wrote in message
news:e76tp8$mm5$1@forums.macromedia.com...
> Ok, I have to appologize for my rant about Dreamweaver 8.02 killing my
> apps.
> It actually does all work fine just not using the Safari Browser on Mac.
> Firefox works perfectly.
> Safari cannot deal with Dreamweaver's new code.
>


Inspiring
June 19, 2006
> DW 8.02 changes all the ASP code that it has always used to insert or
> update
> records when you use the behaviours.
> So if you had a page that was working fine and you open it in 8.02 and
> double
> click the insert record extension, then close it without changing
> anything, all
> the code on the page changes.

OK, but that shouldn't affect Safari at all, since that's all server-side
code.

I think the full story is that DW updated some code that wasn't communicated
to all of the extension developers.

As such, a lot of extensions weren't compatible with what DW was doing.

In the end, this is just another argument to not depend on some other
software writing your code for you ;o)

-Darrel


Inspiring
June 19, 2006
> I think he's talking about the server side code which was updated to
> prevent Sql injection attacks.

Then that shouldn't affect Safari.

-Darrel


riprod7Author
Known Participant
June 19, 2006
DW 8.02 changes all the ASP code that it has always used to insert or update records when you use the behaviours.
So if you had a page that was working fine and you open it in 8.02 and double click the insert record extension, then close it without changing anything, all the code on the page changes.
Inspiring
June 19, 2006
> What 'new code'?


I think he's talking about the server side code which was updated to prevent
Sql injection attacks.


--
Nancy Gill
Adobe Community Expert
BLOG: http://www.dmxwishes.com/blog.asp
Author: Dreamweaver 8 e-book for the DMX Zone
Co-Author: Dreamweaver MX: Instant Troubleshooter (August, 2003)
Technical Editor: DMX 2004: The Complete Reference, DMX 2004: A Beginner's
Guide, Mastering Macromedia Contribute
Technical Reviewer: Dynamic Dreamweaver MX/DMX: Advanced PHP Web Development



Inspiring
June 19, 2006
> Ok, I have to appologize for my rant about Dreamweaver 8.02 killing my
> apps.
> It actually does all work fine just not using the Safari Browser on Mac.
> Firefox works perfectly.
> Safari cannot deal with Dreamweaver's new code.

What 'new code'?

-Darrel