Dreamweaver CC and MYSQL

[redlilac78]

I have been using Dreamweaver for the past 7 years CS5 on a Mac and just recently updated to Adobe Cloud and my entire site broke. I am currently using localhost because I don't even dare wanna see what it does to a live site if it's breaking local host at the moment. I use MAMP for this localhost process. It's come to my attention that server behaviors and stuff like that have been removed here because they "recommend" you use something else or some other way. Pages show up completely fine until it's asking for any information from my localhost MYSQL sever. No coding has changed at all, yet once I remove all of the recordset code (which yes was used from the server behavior tabs and stuff but I know how to write myself) the page shows completely fine yet now I have a broken page. I'm unsure if I'm just overlooking something completely obvious or if I'm pretty much at the point to find a new program to use or a new way to do it. Thing is, I don't know WHAT I should even do next. My live site (which hasn't touched adobe cloud at all yet) still runs completely fine, so I'm unsure what the problem completely is, but would love some feedback or even someone I can put my head together with to figure this out because I've gone 2 days completely stumped.

[redlilac78]

Yes ma'am Everything here is exactly the same as it was before updating dreamweaver.

[pziecina]

redlilac78  wrote

Yes ma'am Everything here is exactly the same as it was before updating dreamweaver.

What version of Dw are you using?

Are you getting any error codes when viewed in a browser via your localhost server?

[redlilac78]

I am using Dreamweaver CC 2017 - was using Dreamweaver Cs5.5

No error, just a blank page

[pziecina]

Have you set up your site definition?

[redlilac78]

What do you mean by that?

by the way really appreciate the help, I cannot think of why this is just blanking on me.

[pziecina]

If you look at Nancys post, (no5) that shows an example of a site definition, but it is possible for the paths to be incorrect when using mamp, as sometimes it is pointing to the server and not the htdocs folder.

It is also worth following Bens advice in his reply, by downloading Dw 2015, and installing the server behaviours, as that way you can check if you have a valid connection script, are using the correct site definition and if the queries are correct.

[redlilac78]

I'll try the downloading old version but what I ultimately want to do is be able to use CC 17 version with mysqli and PHP 7

[pziecina]

The extensions, (paid for) using mysqli do not work in Dw 2017, but the pdo extensions from dmxzone, (see Bens post) do.

If you do not wish to pay for extensions, then your only option is to code by hand.

[Nancy OShea]

PHP 7 would be no benefit to you until your remote server switches to PHP 7.

Version CC 2015 will work with the WebAssist MySQLi extension.

MySQLi Server Behaviors | Dreamweaver extension | WebAssist

NOTE: WebAssist's extension piggy backs on top of the old Server-Behaviors panels.  However, you do not want to use the old  SBs to build your apps.   Instead, you would use the WebAssist menus.  See screenshot.

[Nancy OShea]

Under  Site > Manage Sites....  Is everything properly defined as it should be?

[redlilac78]

Yes it is.

[Luffy_D_Monkey]

I may have a silly question :

Still blank page when using MAMP? Running DW CC2017?

Have you tried to download and use DW CC 2015 (that's my current version for the few last months to come, may will need to pay for some extensions).

The thing i suspect is : CC2017 will try to turn on some localhost server for rendering... conflicting of course with your MAMP localhost.

At least, it did happen a few times to me, but: running Windows 10, Xampp, and CC 2017 yet installed, never opened in months)

[Nancy OShea]

Real-Time Preview doesn't play nice with my local testing (wamp) server.   To Preview locally, I use right click on document tab and select Open In Browser.

[Jon Fritz]

This has been changed somewhat in CC2019. You can now check a box under Edit > Preferences > Real Time Preview called "Default to Static Browser Preview" so the F12 key uses Open in Browser instead of having to right click and choose it from a menu.

[osgood_]

Have you tried downloading the version of the page you have on the remote server, where it works and testing that in your local site. As i recall it didnt take much to upset the fragile code that DW wrote. I was constantly having to redo the behaviours. Best move l ever made was learning how to code manually and ditching the crap DW dished out.

[redlilac78]

Everything on the remote server is the exact same code. The reason I have it separated is because I was about to start working on a new "version" of the site but made sure all the code was the same, only difference at the moment is that connection script you guys helped me fix

But no, I have not downloaded anything from the remote to test - if it's the same code I figured it would work the same

[osgood_]

It might not be the same code. In your first post you say you removed the php sql code and then somehow put it back, this may have caused errors. Its worth downloading a working version of the page and retesting it.