Dreamweaver CC and PHP / MySql

You might as well face facts that the old Macromedia community were abandoned by Adobe a long time ago, Adobe had their own agenda with the Macromedia range and will not listen.

Freehand - Great alternative to Illustrator - killed off ... OK I suppose it doesn't make sense to have Freehand alongside Illustrator but it had a lot of loyal users I'm told.

Fireworks - In the process of being killed off by Adobe, by far the best program for creating web mockups, ux design, web graphics etc ... a fast, intuitive, brilliant piece of software, Adobe announced they will be looking at new products to fill the gap left by Fireworks as the landscape changes.... Nothing has happened and no new product has been introduced that can replace Fireworks, it still remains by a million miles the best software for web mockups/graphics of all kinds .....

Dreamweaver - The old Macromedia Dreamweaver community have been abandoned in favour of what appears to be turning Dreamweaver into more of a WYSWIG for graphic designers with features like the CSS designer and live edit .... I have NOT come across a single experienced web designer/developer who likes the CSS designer feature and I would be interested to know  how they have built a roadmap for the development of Dreamweaver. The fact that Adobe did very little with the server side features in Dreamweaver from CS4 onwards tells the story that they had decided early on to phase out all the server side features ...

Adobe doesn't listen to the original loyal Macromedia community that's for sure, pretty much from day one they have been ignored ......

Not only is all the functionality removed in CC (rendering all my classes and tutorials useless), but you are still SELLING the PHP extensions in Ext Manager!!  I thought it was me, so purchased a $60 ext and still cannot use it.

THEN when people posted a solution you made the link forbidden!!  Good Grief, I just want to use a PHP cart manager without paying $200+

Come on. 

Just adding another voice on the discussion, I am a Dreamweaver CC ACI, and been planning the CC syllabus update for my ATC. It came to my attention that now we have Muse for graphic web creation, Edge Animate to create HTML5 animations, Edge Reflow to create responsive websites and even Edge Code just for coding. Where does Dreamweaver fit in here?! I mean, it does all the same thing those other new tool do, but ... differently?! In my humble opinion, in this scenario, we should be seeing Dreamweaver moving in to the backend direction, not frontend! Therefore, support to PHP and server behaviors SHOULD be the main goal here.

Adobe dont care about coders. They killed Kollection, ADDT and now php basics.
Anyone knows that all of deprecated code could be updated.

Aaaaah! Macromedia times....
I think it's time to force us to leave this app, sooner or later we must find a better IDE.
Sooner or later Adobe will have only one star, photoshop. XD

Another whinge at Adobe's knee-jerk decision to remove Server Behaviors, Bindings, Databases & Components from Dreamweaver CC!

I have been in the creative advertising world since the early eighties and developing websites since the early nineties. I have seen many changes in technologies over that time and started using Dreamweaver when it was first born. I have been a fan of Adobe products for along time and recall one of the first Adobe products I bought was Illustrator'88 (take a guess when that was released!).

A few weeks ago I decided to 'upgrade' from CS4 to Creative Cloud. I looked long and hard at the pros and cons but did not come across the issue of the removed behavious panels. I have had a hard time recently (without going into any detail) and decided to commit once again to working freelance in an area of the business that I love - dynamic communication. This means combining databases, html front-end (and associated technologies) and my marketing skills. The core technology therefore is Dreamweeaver combining front-end design with back-end structure. Now I have lost that vital link.

At the same time as upgrading to CC I gained two very large pieces of work, one was to redesign and re-engineer an existing and quite complex intranet site that I developed and few years ago and another is to create a whole new database driven site. Now I am stuck as to where to go.

I have read alot about this issue and my understanding is that PHP have decided to remove the Mysql extension from PHP and replace it with the more secure mysqli or PDO_MySQL extensions. Fair enough, technologies move on, I can understand that. What I can't understand is Adobe's reluctance to keep their change in product from it's 'everyday' users like myself. We, the users, don't always keep up-to-date with these changes in technlogy. We have our heads firmly fixed on doing our jobs and earning an honest crust. We rely on the likes of Adobe to keep up-to-date with these changes and make the tools available for us to use without any interuption to our workflow.

Why therefore have Adobe not put a notice on the existing Server Behaviors, Bindings, Databases & Components stating that they recommend not to use these functions as they are being replaced, rather than simply removing them and leaving us with nothing. It's as if we had a rusty but usable shovel, Adobe comes along and takes takes the head of the shovel away and says we will give you something better to replace it with sometime in the future, but for now we just have to stab at the ground.

Is there an alternative way of working built into Dreamweaver CC or indeed any other Adobe CC product to help me achieve what I (and many others) want?

Is Adobe building in a new mysqli or PDO_MySQL functionality that will be similar to the Server Behaviors, Bindings, Databases & Components panels that we are used to?

When will this new functionality be available as an update?

Extension "Deprecated Panel Support v.1.0.0" doesn't work for me and I don't know why. I cannot connect to any of my existing MySQL databases and therefore further development or changes to existing sites comes to an abrupt halt.

All we want are some simple, clear answers, otherwise we will have to make some clear and simple commercial decisions as our livelyhood depends on it. Here's hoping...

Regards

Neil

Deprecating the server behaviors is a horrifying development indeed.  I've been with Dreamweaver since 1999 when Macromedia aquired Drumbeat and incorporated it's features, eagerly purchasing every new release since.  This is the sole reason I use Dreamweaver and have built my career on building applications this way.  It's far easier, effective, and efficient for most jobs than tools like VisualStudio or any others, and I've used a lot of them.

I am temporarily relieved that you can hack Dreamweaver into supporting server behaviors, but how long will that last?!  Probably not long. 

The word "deprecate" means "To declare something obsolescent; to recommend against a function ... that still works but has been replaced."  Well, what is the replacement?

Adobe, I am begging you to keep this feature ( and develop it further, for that matter)!!!

This whole thing is stressing me out - I use both PHP and Classic ASP with DW, and have a ton of purchased extensions.

I agree - Adobe should have been updating their behaviors - not just saying "the code is old".

In addition to that, I'm not a fan of subscription based software - so this big change to CC may just be my time for looking for another programming platform - lots of open source options.

Sad too - I've been with Dreamweaver since before it was Dreamweaver - if any "old school" folks out there remember "Drumbeat" by Elemental Software - that's where it all started - then Macromedia, then Adobe.