Dreamweaver CC and PHP / MySql

[Rick Gerard]

So what has happened to the database connections, bindings and server behaviors options. There are no DATA options in the insert bar.

I hope this is not going away.

Max OSX 10.8

[Nancy OShea · Accepted solution]

Deprecated in CC.

Use the legacy extension to bring them back.

http://forums.adobe.com/thread/1231011?tstart=0

Nancy O.

[Rick Gerard]

Whose brilliant idea was it to deprecate (remove) these features. PHP is the highest paid most in demand web programing specialty today. It's crazy to remove this feature from Dreamweaver and religate Dreamweaver users to other solutions or hand coding of 100% of database functionality. Secure user back end web development depends heavily on server behaviors and database access. Not everybody wants to use Wordpress.

[Nancy OShea]

Unfortunately, the use of antiquated server behaviors have not been recommended in the PHP specs for quite some time because they're not secure.

David Powers posted this several months ago both here and in the Apps Development forum.

"You should be aware Dreamweaver server behaviors are being removed from the next version of Dreamweaver because they use outdated code that is scheduled for removal from PHP."

PHP 5 is all about PDO (php data objects) and MySQLi (improved).  Some of the better hosting companies have already upgraded to new PHP & MySql.  Many others, however, have not.  So we're all in limbo at the moment.

Nancy O.

[Rick Gerard]

That just means that the Dreamweaver team should be spending time on the PDO and MySQLi tools. I don't mind missing the server behaviors as much as loosing the code hinting and access to the database by a control panel.

[pziecina]

Hi Rick

I am not promising anything here, as with the removal of the server behaviours and database connections, I am not even certain if it will be possible.

I do know that getting both the MySQL and MSSQL database schemas to show, was relatively simple when the old database panel was available. So over the weekend I will look into if showing the schema in a panel, can be restored without the rest of the functionality.

PZ

[Preran]

Hi Rick,

We are hearing you. Rest assured, every concern that we see here is being routed to the appropriate channels. We are definitely not going in the way of making Dreamweaver a HTML and CSS only software. We are waiting for all the queries to come in before we provide a comprehensive reply. I will post the message as soon as it is out.

We appreciate your patronage, and will ensure that we have as many people covered as possible as we move forward.

Thanks,

Preran

[Andoyo Andoyo]

Hi Mr. Peran,

You always say that you are hearing to your customer, but there is no change or update from 2013 to 2014 from Adobe for the database & PHP features (Server Behaviors, Databases and Binding).

Its look like that Adobe just hearing from your left ear and then pass away from your right ear. Nothing change...

Thanks

[allenw92860638]

The Dreamweaver team should definitely not remove the server behaviors.  Dreamweaver is a fantastic tool and basically getting rid of the server behaviors is akin to just scripting all the good stuff out of the tool.

[Nancy OShea]

You came late to the party.  DW removed (deprecated) server behaviors because they are woefully outdated and soon to be obsolete.  As of  PHP 7 (due out this fall), the MySQL connections will no longer work.  Legacy web sites that relied on outdated SBs will fail to operate.   Why would you want to cling to outdated code?

Learn to code manually in MySQLi (improved) or PDO.

http://code.tutsplus.com/tutorials/pdo-vs-mysqli-which-should-you-use--net-24059

Or, replace Deprecated Server Behaviors with a commercial extension (MySQLi or PDO):

http://www.webassist.com/dreamweaver-extensions/mysqli

http://www.dmxzone.com/go/22096/updated-replacing-dreamweaver-server-behaviors-with-dmxzone-extensio...

Nancy O.

[allenw92860638]

Thanks for the reply - I've manually written the mysqli connection.

Thanks for the information on where to find the new extensions. I promise

not to hold on kicking and screaming to old technology but I do still

want to have the ability to have good functionality.

[PmPhotographic]

HI,

Thanks for the links, but isn't the point of the original poster, that this facility, albeit modernised, should be part of dreamweaver, in order to maintain it as a stand alone, all in product.  I've just looked at the DMX link you provided, and if I understand correctly, their tool is £103, quite a lot to replace something that was included in Dreamweaver when I originally purchased it

Another part of the attraction for some of Dreamweaver is precisely that of not learning the code, I suspect quite a few users are not power users, but use it to create or manage small commercial, or non commercial sites.  These people will now be wondering if their sites will not function and they need to learn new skills, or spend more (and learn new skills?) simply to stand still, while seeing the product they invested in, apparently telling its user base to find other ways

[JORGE JR]

That's the point! Adobe should update the whole thing and keep it in DW.

But at this point, we all should move along and choose a framework to speed

up our projects.

Em 26/08/2015 17:42, "PmPhotographic" <forums_noreply@adobe.com> escreveu:

Dreamweaver CC and PHP / MySql created by PmPhotographic

<https://forums.adobe.com/people/PmPhotographic> in *Dreamweaver support

forum* - View the full discussion

<https://forums.adobe.com/message/7902047#7902047>

[Paul-M]

Dont really see you logic Nancy .... They ware woefully out of date because Adobe chose not to update them for several years - the writing was on the wall when they pulled the plug on ADDT ......

They should have either removed them all together early on or updated them with MySQLi or PDO support

.... Adobe does pretty much what they want with little transparency. Was there ever a clear message early on that server behaviours are finished?? .... when you are a dominate force and pretty much a monopoly you can do what ever you like!! .....

The lesson for everyone is don't have your entire workflow dependant on Adobe products, look at alternatives, look at open source projects and protect yourself!!

[Nancy OShea]

I don't make policy decisions anymore than you do.  Adobe made the decision to let 3rd party extension developers worry about Server Behaviors.  That's it!  Perhaps the logic was calculated on the number of people who use SBs.  It's certainly not the majority of their user base.

Advanced coders don't need SBs. Static site designers don't use SBs because they don't develop dynamic web apps. So why should Adobe throw more programming resources at  overhauling a feature that few people need, want or use?  That's what optional extensions are for.

Nancy O.

[hassan_c]

Well, who knows which majority is using php / mysql?
Fact is, most cms software is using php / mysql server models: Joomla, Wordpress, Drupal, Typo3 .. you name it. If Adobe wants clients not to move towards those platforms (wordpress still shows extraordinary growth) it has to do something. At w3techs.com you can read: "WordPress is used by 58.7% of all the websites whose content management system we know. This is 24.6% of all websites.)

So, why should Adobe care about server behaviours supporting php / mysql? This question sounds like a joke to me.

What shakes me is Adobe's total ignorance and unwillingness to learn the new fast and modern developments of php (mysqli) and update Dreamweaver accordingly.

If they don't - lets all switch to Wordpress & Co. - It is totally free. Everything Adobe does is totally fee and it is constantly spying on us as soon as we get online,

So, either change, dear ADOBE or RIP.

[osgood_]

Nancy O. wrote:

I don't make policy decisions anymore than you do.  Adobe made the decision to let 3rd party extension developers worry about Server Behaviors.  That's it!  Perhaps the logic was calculated on the number of people who use SBs.  It's certainly not the majority of their user base.

Advanced coders don't need SBs. Static site designers don't use SBs because they don't develop dynamic web apps. So why should Adobe throw more programming resources at  overhauling a feature that few people need, want or use?  That's what optional extensions are for.

Nancy O.

You say advanced users don't need SB's - they actually don't need DW at all so isnt it the not so advanced users that DW should be primarily aiming at, those that would appreciate and depend on something useful like solid up-to-date SB's. A good sofware progam is built on solid foundations (which DW once was until it was snatched away by Adobe). Personally I think DW has been rocking badly over the last few releases including nothing remotely worthwhile - there is really no where else for it to go but sideways.

You really only upgrade now because the current version you're running doesn't work anymore with your OS rather than upgrading because the current release offers something innovative, which is strange because there is more innovation being incorporated into their open source editor, Brackets. Why do you think there is CC because the not so duumb people in Adobe saw the possibilities to entice people to upgrade running out so they now take your payment annually to keep the party going without offering much for your ticket.

[Nancy OShea]

@osgood,

I feel like DW is aimed at different users now than it was 5-10 years ago.  I guess I still use it because I'm very comfortable with it.  But as you know, it's not the only tool in my chest. 

@hassan_c,

If you develop Themes for WordPress, etc... you already know that good coding skills are a necessity.  Relying on Server Behaviors to build  backend code is not going to make you a better developer.  If anything it will only hold you back.  Time is much better spent on independently learning PHP & MySQLi (improved) or PDO.  You certainly don't need Adobe's permission to do that.

Nancy O.

[hassan_c]

Well. it depends!

Imagine to first create a wonderful layout with all the tools you have - with dummy texts and elements, if you wish. In a second steps you connect all these elements with the backend data of your database application. So, it does not make you better coder - right. But you will create more powerful websites where you still know what you do.

So, the whole question boils down to a simple fact: A great tool does not make you a good webdesigner. But a good webdesigner who knows how to use those tools, will accomplish his tasks faster and more efficently.

DW CC simply misses the mark to improve this arsenal of tools.

We woodcutters complain why Adobe stopped to improve its chainsaws.

Just to remove the old ones does not feels right or very clever.

[osgood_]

allenw92860638 wrote:

The Dreamweaver team should definitely not remove the server behaviors.  Dreamweaver is a fantastic tool and basically getting rid of the server behaviors is akin to just scripting all the good stuff out of the tool.

Removed for a reason - sooner or later they would not have worked any longer. I do agree however I think instead of investing time in useless projects like Fluid Grids - now defuncted it would have been better to have invested that wasted time in updating the server behaviours.

Having said that any feature, like server behaviours, can only provide a limited amount of options - you would be wiser to invest a few hours in learning how to connect, insert, update, delete etc by writing the code yourself.

[Last_Webmaster]

Ok.

Adobe removed Server Behaviors, Bindings, Databases & Components from Dreamweaver CC.

What can I use for my older sites to maintain all of them now? 

Can we move this discussion forward?  I need a solution. 

Thanks.

[BenPleysier]

Install the extension found at http://www.dmxzone.com/go/21842/enable-server-behaviors-and-data-bindings-panel-support-for-dreamwea... , using http://www.dmxzone.com/go/22670/dmxzone-extension-manager-for-dreamweaver?utm_source=Extensions&utm_... to install.

Then make sure that you are not running a PHP7 server.

Also note that this is not a future proof method.

[Nancy OShea]

Because the deprecated SB panels generate obsolete code, you will also need to hide warnings in your local server's php.ini file. 

PHP.INI -- hide deprecated warnings

https://forums.adobe.com/message/8493981#8493981

A better long-term solution.

Replace Deprecated Server Behaviors with a modern commercial extension:

• http://www.webassist.com/dreamweaver-extensions/mysqli
• http://www.dmxzone.com/go/22096/updated-replacing-dreamweaver-server-behaviors-with-dmxzone-extensio...

Nancy O.

[raynestorm]

Just to be clear, the problem is not "the use of antiquated server behaviors is not recommended..". The problem is Adobe chose not to update the behaviors. Dreamweaver seems to be moving toward being a CSS Designer and away from being a Coldfusion or PHP developer environment.

[Nancy OShea]

Changing the underlying programming from countless JS server behavior files to a radically new approach is a Herculean task.  I certainly wouldn't want to write this code.  Would you?

I'm confident that Adobe's  DW team knows perfectly well WHAT they need to do.  It remains to be seen if they'll deliver it  in DW or through collaborative efforts with 3rd party extension developers.  I don't really care how it's delivered just so long as it arrives and works as promised!

Nancy O.