Braniac

Answered

Issue with using Extensions and Add-Ons in DW

Forum|Forum|7 years ago
October 15, 2018
11 replies
9933 views

If you rely on extensions or add-ons, DO NOT allow the Dreamweaver 19 update to occur.

This topic has been closed for replies.

Correct answer Nayan_Kankariya

Hello,

If you have run into an issue that the extensions installed from older versions of Dreamweaver do not show up after uninstall and re-install of Dreamweaver CC 2019, here are a set of steps that will help make the acquired extensions available in Dreamweaver 2019.

Note:

This will work only for the extensions that support Dreamweaver CC 2019 and were installed via the Adobe Exchange platform or using the ExManCMD tool.
If you are using a Third party extension installer that does not use ExManCmd, this fix will not apply.

Steps:

Download the appropriate zip package using these links:

For macOS

For Windows

Quit all Adobe applications.
Unzip the package and run the file
1. For macOS: InstallExtensions.command
2. For Windows: InstallExtensions.bat
If prompted by macOS or Windows, provide your password to proceed.
Wait for the process to be complete.
Launch Dreamweaver CC 2019 and check if the extensions are visible.

Report any errors that you run into. And we’d appreciate hearing back from you that this solution worked.

P.S. : This script internally only disables and enables the acquired extensions so that they show up in Dreamweaver CC 2019. After performing the above steps, if the extensions are not visible in Dreamweaver CC 2019, navigate to this page, click Uninstall, wait for 20-30 seconds for the extension to be removed, and then click Install.

Thanks,

The Adobe Dreamweaver Team

Nayan_Kankariya

Correct answer

Community Manager

Hello,

If you have run into an issue that the extensions installed from older versions of Dreamweaver do not show up after uninstall and re-install of Dreamweaver CC 2019, here are a set of steps that will help make the acquired extensions available in Dreamweaver 2019.

Note:

This will work only for the extensions that support Dreamweaver CC 2019 and were installed via the Adobe Exchange platform or using the ExManCMD tool.
If you are using a Third party extension installer that does not use ExManCmd, this fix will not apply.

Steps:

Download the appropriate zip package using these links:

For macOS

For Windows

Quit all Adobe applications.
Unzip the package and run the file
1. For macOS: InstallExtensions.command
2. For Windows: InstallExtensions.bat
If prompted by macOS or Windows, provide your password to proceed.
Wait for the process to be complete.
Launch Dreamweaver CC 2019 and check if the extensions are visible.

Report any errors that you run into. And we’d appreciate hearing back from you that this solution worked.

P.S. : This script internally only disables and enables the acquired extensions so that they show up in Dreamweaver CC 2019. After performing the above steps, if the extensions are not visible in Dreamweaver CC 2019, navigate to this page, click Uninstall, wait for 20-30 seconds for the extension to be removed, and then click Install.

Thanks,

The Adobe Dreamweaver Team

BenPleysier

Braniac

With due respect, this is a retro step. Why should I have to go through that process just to get the an extension into Dreamweaver. This used to be the flagship web editing program because of its extensibilty. Why can't we have our trusted Extension Manager back again, or better still, incorporated within Dreamweaver so that, with a click, we can install an extension.

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!

ALspAuthor

Braniac

By the way, Nayan's post is most definitely NOT the correct answer... not even close.

W

W_J_T

Inspiring

Thanks for confirming that its not the answer. I thought your initial follow up showed it was not, even at the time it was presented. But with over 1500 views of this thread I guess Adobe wanted to slow the conversation and proven disconnect of them as seen in this thread.

ALspAuthor

Braniac

You know what? Let's try a metaphorical approach.

The Exchange is the cart and Extension Developers are the horses. The cart right now has broken wheels.

Fix the problems, throw in a few creative solutions that are designed to make your customers happy, and I can almost guarantee that we will help pull the cart for you. But you cannot possibly think, given the lack of volume and bugs on the Exchange (at least as far as Dreamweaver is concerned) for people like us to invest the time and effort to hitch our products to your post. There is absolutely no potential for ROI.

Please, Jonathan. Fix it.

pziecina

Braniac

ALsp wrote
Fix the problems, throw in a few creative solutions that are designed to make your customers happy, and I can almost guarantee that we will help pull the cart for you.

Quite honestly AL, I don't think Adobe is interested in Dw, or that the Dw team can do anything about Adobes way of thinking anymore.

They have spent so much time, (not money) trying to ignore a web that they know they cannot control, failed in trying to make individual programs that get rid of web developers, and shown contempt for anything that came after 2008, that they cannot change now.

The necessity to create the Edge apps and the very public statement the CEO made to 'apologise' about ignoring html5/css3, has I think turned Adobe against serious web development.

ALspAuthor

Braniac

I have not yet given up hope. I've talked with Jonathan, who manages the Exchange, and he is a reasonable fellow. If I can somehow broker a discussion among the Exchange team, the Dreamweaver team, and me, perhaps we can hammer out a solution. The bottom line is that I want this to work. We have too much invested in Dreamweaver and I have no problem with the Exchange, if it works. Right now, it doesn't. The problems with installing DW extensions through either our Extension Manager, Anasasi's, or the Exchange are the same, because try as they may to hide it, Adobe is in fact using the code behind its dearly departed extension manager to … um … install extensions. They just removed the front end.

P

Paul-M

Braniac

I encountered the same problem as stated here in this thread: installing CC 2019 reset everything back to default In CC 18.2, lost extensions, prefs reset etc in CC 18.2

I was able to reinstall my extensions in CC 2019 with DMXZone's extension manager without any issues.

Another issue is I still have to have my settings in Creative Cloud app set to English (North America) despite the fact I'm the UK. if I set to English (International) it causes other issues with extensions installed via the Adobe Add-ons website, this particular issue is a few years old now and has never been addressed/fixed to my knowledge.

Adobe are too big, $7-$8 billion turnover and totally disconnected from its customers, should never have been allowed to buy Macromedia its all been downhill for us since then, can't rely on Adobe, can't trust them to build our workflow and critical work around their software & then if you switch to alternative software Adobe may end up buying them out and EOLing or ruining the software anyway.

Paul-M - Community Expert

ALspAuthor

Braniac

Another issue is I still have to have my settings in Creative Cloud app set to English (North America) despite the fact I'm the UK. if I set to English (International) it causes other issues with extensions installed via the Adobe Add-ons website, this particular issue is a few years old now and has never been addressed/fixed to my knowledge.

That issue has been repeatedly brought to Adobe's attention... by me, for one... for a few years now. I think there is a disconnect between the Exchange and the Dreamweaver team. I also firmly believe that Adobe either doesn't know, or perhaps does not want to know, that the Exchange, with respect to Dreamweaver, is dead as my grandmother's front door knob. Your best bet, as you probably know, is to acquire your extensions directly from the developer... if possible.

Impressive_play01AC

Inspiring

Sometimes I think that Adobe has moved the entire Dreamweaver department in India just to not hear about it anymore.

W

W_J_T

Inspiring

Its too bad the post by Staff was so quickly removed after being posted here. Telling ALsp , that one fix is to instead upload and offer extensions through Adobe's Exchange. I would of loved to see the response to that idea for resolution.

It seems ...

ALspAuthor

Braniac

You will. Refresh your browser. It seems serendipity smiled on me and I happened to see Nayan's post before it was deleted. Perhaps she simply wanted to edit it, though...

Nayan_Kankariya

Community Manager

Hi AL, W_J_T,

Yes, the intention was to edit the reply with the solution of local zxp installation.

Will revert back shortly.

Thanks,

Nayan

pziecina

Braniac

Hi AL,

I don't know if you have read the latest Brackets release notes, but it looks like Brackets is adding one of the main functions that Dw users often give for its use, namely drag and drop of files in the file tree structure -

https://github.com/adobe/brackets/pull/13546

https://github.com/adobe/brackets/wiki/Release-Notes:-1.13

Maybe its time for you to at least consider converting your extensions for Brackets use.

O

osgood_

Braniac

pziecina wrote
Hi AL,
I don't know if you have read the latest Brackets release notes, but it looks like Brackets is adding one of the main functions that Dw users often give for its use, namely drag and drop of files in the file tree structure -
https://github.com/adobe/brackets/pull/13546
https://github.com/adobe/brackets/wiki/Release-Notes:-1.13

I dont see any use of that functionality unless it updates the links as well and I don't think it does that, at least it doesnt appear to say it does. A lot of editors have the ability to shift folders/files from one location to another but not update the links.....which in the case for a static site would be useful..........thats if anyone actually builds static websites any longer........... so it might not be a feature any longer that is even worth considering as it once was.

pziecina

Braniac

osgood_ wrote
I dont see any use of that functionality unless it updates the links as well and I don't think it does that, at least it doesnt appear to say it does. A lot of editors have the ability to shift folders/files from one location to another but not update the links.....which in the case for a static site would be useful..........thats if anyone actually builds static websites any longer........... so it might not be a feature any longer that is even worth considering as it once was.

The point is that free code editors are catching up and adding many of the features that can make Dw a choice for some. link updating is not a feature that many dynamic sites require.

Nayan_Kankariya

Community Manager

All,

Thank you for reporting this issue. We understand that this issue is observed specifically for the following set of users:

Users on Dreamweaver prerelease, who uninstalled a prerelease build and installed Dreamweaver CC 2019 by removing preferences
Users who’ve reinstalled Dreamweaver CC 2019 (install > uninstall > install CC 2019) by removing preferences

Following these steps should allow you to successfully load and run your favorite extensions. If you still run into issues, please do contact Adobe Tech Support.

Open this link in a browser.
Click on Uninstall for each of the already installed extensions.
IMPORTANT: Once done, wait for notifications from the Adobe Creative Cloud desktop app indicating that the extensions have been successfully uninstalled.
Switch-back to Adobe Exchange portal, and click on Install for all extensions you want to use.
IMPORTANT: Once done, wait for notifications from the Adobe Creative Cloud desktop app indicating that the extensions have been successfully installed.

The issue occurs when uninstalling Dreamweaver CC 2019 and with the option of clearing preferences. This is due to the extensions database not being in sync with uninstall information. Hence on reinstall, the extensions are not automatically installed back.

Thanks,

The Adobe Dreamweaver Team

ALspAuthor

Braniac

Nayan_Kankariya wrote
The issue occurs when uninstalling Dreamweaver CC 2019 and with the option of clearing preferences. This is due to the extensions database not being in sync with uninstall information. Hence on reinstall, the extensions are not automatically installed back.
Thanks,
The Adobe Dreamweaver Team

Hi Nayal,

I see from your signature that you are part of the Adobe team. Since most Dreamweaver extensions are not downloaded from the Exchange, I was wondering if you would be willing to disclose whether the Extension manager being discontinued was a decision you are familiar with, whether you were part of that decision, whether it came from "above", or whether the Exchange team called the shots on that decision.

Would you be so kind as to tell us?

Nayan_Kankariya

Community Manager

Hi ALsp,

Ben also conveyed his concern earlier about the deprecation of Adobe Extension Manager. With regard to this, we have notified the same to the concerned team here and working towards what best can be done. Will keep the thread updated on the outcome in coming days.

Thanks,

Nayan

Nayan_Kankariya

Community Manager

Thanks for bringing this issue to our attention. We are able to see this issue occur intermittently.

The issue we are noticing is that add-ons are not getting automatically migrated upon installation of Dreamweaver CC 2019.

We are working to isolate the issue, identify the root cause, and fix it as soon as possible or provide a workaround that will help you come unstuck.

Thanks,

The Adobe Dreamweaver Team

BenPleysier

Braniac

Nayan_Kawa, many moons ago, Al (PVII), George (DMXzone) and Ray (Webassist) were all having a problem because adobe suddenly discontinued the Extensions Manager, it was left up to the individual extension suppliers to create their own. Then all of a sudden there were huge changes in the Dreamweaver program that caused Ray's extensions to mal-function.

On many an occasion I said that Dreamweaver is a good product only because of its extensiblity. If these estensions do not work, Dreamweaver is no more than many other (much cheaper) solutions.

I was part of the pre-release program when Teodor of DMXzone was continually pleading with the Development Team to get his extensions to work on Dreamweaver. This continual battle without bi-partisan support has forced DMXzone to create their own solution, one that does not require Dreamweaver. Webassist have been reduced to a small clan of enthousiasts that are using outdated versions of Dreamweaver while Al of PVII now has a new battle on his hands. When will Adobe learn from past mistakes. When will Adobe approach the extension makers before make these irrational changes.

End of my rant and I did not even mention ........!

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!

BenPleysier

Braniac

W_J_T wrote
Astoundingly, Dreamweaver was not even mentioned in yesterdays news release about Adobe products regarding Adobe Max. I guess the new features are so underwhelming they chose to completely omit it entirely. I see the Wappler crowd is having a laugh.

In some ways I feel sorry for the members of the Dw team and the support staff, as they can only do what adobe allows or says. The ones I do not feel sorry for are the adobe and Dw managment, as they should know why Dw is so behind even the free tools, they are responsible for what they have, (or have not) done, demonstrate constantly that they have no interest in finding out why Dw is so behind what is required for modern web development. They obviously do not have the managment skills required to find out what is wrong or do something about it, one way or another, (fix it, or put it out of its missery).

pziecina, I totally agree with your sentiment, I too feel that it is the management at fault. I have held off for a long time in my criticisms of Dreamweaver, all the while hoping that they (the Team) would be able to pull it together.

Even at my age I prefer to look forward rather than in the past. This does not mean that we should not learn from the lessons of the past. The turning point of Dreamweaver's demise was its removal of the Server Behaviours panels, instead of updating the code. Despite numerous promises, the functions have not returned. I fondly think back to your PDO extension as a warning to Dreamweaver to follow suit.

I favoured getting rid of Spry for jQuery, and Fluid Grids for of Bootstrap. At least we were assured that the open source frameworks would be maintained. Ok, not everyone is in favour of frameworks but it does remain a choice.

Another criticism I had, even in the days of CS, was the lack of speed when using Dreamweaver. Quite often I was typing three or four characters ahead of what was showing on screen and I am no speed typist. After opening Dreamweaver I often wander off to the coffee machine. I made a calculation which showed that it takes Dreamweaver 85 seconds to start up. At an average of 10 startups a week (kept low) and at my hourly rate of $60 (kept low), this works out to be $370. Compare that to the other program that I use which takes 5 seconds at a total cost of $22. Even if Dreamweaver was free of charge (which it isn't) and even if the extensions were free of charge (which they're not), we still have about $350 left to pay for a program that includes all of these extensions. I'm sorry to say that it is a no brainer.

In conclusion and putting it simplistically:

Dreamweaver needs to be leaner
Dreamweaver should include Server Behaviours.
Dreamweaver should remain extensible (without the intervention of Adobe)

Is it all too late? Is Adobe fighting against the eight ball? For Al Sparber et al, I hope not.

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!

williamj312762442949201

Participating Frequently

I've never had any issue with DMXzone extension manager. It works flawlessly with CC2019 as with any other update before that.

Also I have 38 dmxzone extensions installed in CC2018 which are also working perfectly after the installation of CC2019.

ALspAuthor

Braniac

Thanks, William, we know that, but it's not relevant to the issue DMX Zone built a thoroughly proprietary EM. We, use Adobe's ExMan library. That said, DMX Zone has had other issues, similar to ours, which is why they opted to create Wappler.

pziecina

Braniac

The question is AL, has Dw completely stopped the instalation of 3rd party extensions, or is this just a temporary glitch whilst you work out how to get your extension manager to work with Dw 2019?

ALspAuthor

Braniac

Of course we can get an Extension Manager working. The problem is that even the App Store is affected. Despite their ineptitude I'm fairly certain the Dreamweaver team could not get away with screwing up the App Store connection. This is just another in a series of blunders, and it's getting really old. It's like the management of the Dreamweaver team is a ghost, a mute, or simply doesn't care enough about her customers to communicate.