DW 2015 & 2017 On Same Machine - Installing Extensions

[Paul-M]

I have installed DW 2015 and 2017 on the same machine (Windows 10 64bit). I can't install extension into DW 2017. Tried through adobe add-ons site and with third part extension managers (the P7 and DMXZone ones). Extensions only install in DW 2015 which ever way I try.

[ALsp]

Both DMX Zone and we have issued updated extension managers, both of which seem to be working fine according to our tests. If you are using the latest EM version and still have problems it would indicate a problem originating with your computer or your Adobe installation. You can check to see if you have the latest PVII EM installed by opening your current one, opening the Window menu, and clicking "About PVII Extension Manager".

[Paul-M]

No option is working for me

Adobe Addons - Just automatically installs extensions to DW CC 2015, nothing gets installed to DW CC 2017

The same behaviour in both DMXZone and P7 Extension managers:

1. Both extension managers show DW CC 2015 & DW CC 2017 versions in the UI
2. If I select DW CC 2015 and install an extension it installs in DW CC 2015 but in both extension managers (P7 and DMXZone) it shows the extension under both DW CC 2105 and DW CC 2017 although it's definitely does NOT get installed in in DW 2017
3. If I select DW CC 2017 in either extension manager (P7 and DMXZone) and install an extension, it shows up under both versions of DW again but for some reason just installs in DW CC 2015 again and NOT in DW CC 2017.

[ALsp]

As I replied on our forum thread you started, we cannot duplicate your issue on several similarly configured machines. This could also be a file permissions issue if you happen to have installed different versions using different logons. Could be a lot of things, but all computer based. What is the language of the version you have installed? If it is not EN_US you will not be able to install anything into 2017 as per Adobe.

[Paul-M]

When I install via Adobe Cloud there are no languange/locale options offered during installation of Dreamweaver, however when I look in DW 2017 config folder I have both an en_US and en_GB folder so I'm assuming this is the issue. I don't see any option  to change this?

[BenPleysier]

This is what the PVII EM shows

And this is what DMXZone EM shows

The former shows 2 and the latter shows 3 of my in total 5 (not including Beta) Dreamweaver installations.

[Paul-M]

I found locale options in cloud > preference. POssibly installed DW 2015 in en_US and later chnage the settings to English International. I'll try installing again with different setting

[ALsp]

Energize wrote:

I found locale options in cloud > preference. POssibly installed DW 2015 in en_US and later chnage the settings to English International. I'll try installing again with different setting

Unable to install Dreamweaver extensions in non-English locales

Adobe is vague on this but they are referring to versions other than en_US

[Paul-M]

Ok here's what happens with DW CC 2017, if someone can tell me why it's happening and how to change this behaviour.

When I install DW CC 2017 it creates en_US folder on first launch.

When I try to install an extension for DW CC 2017 a second folder is created inside config en_GB and the extension is installed in there by the looks of things.

This happens regardless of how I install the extension, Adobe add-on site, P7 or DMXZone ext manager

[ALsp]

Energize wrote:

Ok here's what happens with DW CC 2017, if someone can tell me why it's happening and how to change this behaviour.

When I install DW CC 2017 it creates en_US folder on first launch.

When I try to install an extension for DW CC 2017 a second folder is created inside config en_GB and the extension is installed in there by the looks of things.

This happens regardless of how I install the extension, Adobe add-on site, P7 or DMXZone ext manager

You apparently did not read the article I posted for your entertainment earlier :

Unable to install Dreamweaver extensions in non-English locales

Now, I know GB English is English, better than US English in many ways, but Adobe even has bugs in its bug reports because by English, they actually are referring to en_US ONLY.

It. Is. A. Bug...

A known bug.

That said, there is absolutely nothing of real importance in Dreamweaver 2017, so you should simply revert back to CC 2015 until Adobe fixes CC 2017.

Now that I know you are installing an en_GB version, that is your only solution. It is not a problem with the extension manager or the extension. It is one of many bugs that shipped with Dreamweaver 2017.

[Paul-M]

Yes I did read it,  but I don't want to manually copy extension files/folders each time I install an extension into the correct locale folder if that's what your suggesting

.... And is this a DW 2017 specific bug? ...Because it isn't happened with my DW CC 2015 installation.

...My settings in Adobe Cloud app are set to English (North America), so I don't get why the en_GB folder is created when I install an extension.

[Paul-M]

In short how do I make sure my DW CC 2017 installation is en_US ?? Presumably I shouldn't have this issue then?

[ALsp]

Energize wrote:

In short how do I make sure my DW CC 2017 installation is en_US ?? Presumably I shouldn't have this issue then?

Change the language setting of your Creative Cloud apps

Again, Adobe is not consistent and to show en_US in your configuration files you need to select English (North American). Perhaps the Canadians complained

[Paul-M]

Well here lies the problem, because I already changed the language to English (North American) in Adobe Cloud App preferences, removed Dreamweaver CC 2017 and manually tried to clean up DW 2017 remnants (registry and config folder). I reinstalled DW 2017 and still when I install an extension it creates an en_GB folder .....

[ALsp]

That would be an Adobe issue beyond my ability to help you with. But I still do not understand why you are simply not reverting back to using CC 2015. There is absolutely no reason to use CC 2017. None. Zilch. Naught. Nan.

[ajatix_com]

It seems the locale info is stored in ExMan.db file. The file is in SQLite format. The locale for each version of Dreamweaver is stored in Tb_ProductInfoV2 table. You may want try correcting it.

Not only British users have problems installing extensions with Adobe tools. This happens to users in Switzerland (de_CH and de_DE locales), Austria (de_AT and de_DE), etc.

[ALsp]

ajatix.com wrote:

It seems the locale info is stored in ExMan.db file. The file is in SQLite format. The locale for each version of Dreamweaver is stored in Tb_ProductInfoV2 table. You may want try correcting it

I wouldn't do that. Could become another problem when Adobe fixes the bug.

[ajatix_com]

It is just a text value specifying the locale that the Extension Manager is using when installing extensions. If you want it to install into en_US, this value should be en_US. If it is set to en_GB, the Extension Manager will install into en_GB. It can be changed back and forth.

ExMan.db is related to extension managers based on Adobe Extension Manager command line tool (like yours).

DMXZone Extension Manager, however (as far as I know) does not use ExMan.db settings. It simply installs into the first locale folder it finds. Which alphabetically happens to be en_GB, de_CH, etc. If you don't have secondary locale folders, you should be fine with DMXZone Extension Manager.

[Paul-M]

I wanted to run both 2015 and 2017 Al, so in my spare time I can have a play with the 2017 version although not using 2017 for working purposes,  I still want to see if extensions still work as desired and discover what other mess the Adobe engineers have made in the 2017 release.

Aside from all the glitches, the biggest disappoint for me is ripping out the existing code editor which was a sound feature that just needed tweaking. It's just another nail in the coffin for long-time DW users. Soon design view will be ripped out I'm guessing as it's never been updated, instead they added a crappy live view and since they removed design time style sheets from the UI I'm sure as sure as eggs are eggs they will in a future update rip out design view. Absolutely clueless!!

Aside from a few sycophants on this forums who will always come on and try to put a positive spin on things, all I see is what was a great all round tool being ripped apart with changes for changes sake and no idea or direction what Dreamweaver was all about in the first place.

[ALsp]

We released a Command that adds bac Design Time CSS... in a better UI.

I guess what I've been tryin to say is that there are no new features in DW 2017 worthy of consideration. None. So the prudent thing would be to wait until Adobe fixes the known bugs. We may even get lucky and Adobe might even make a proper code editor.

Our extensions work perfectly in 2017. The problem is that a Adobe bug with non US installations prevents extensions or app store purchases from ever installing because Dreamweaver's configuration folder structure is corrupt.

I don't know how to explain myself any better.

[Paul-M]

I understand what your saying Al. I know ho to set design-time without the UI but your extension would be useful to make life a bit easier.

[BenPleysier]

Energize wrote:

Aside from a few sycophants on this forums who will always come on and try to put a positive spin on things

I guess there will always be 'sycophants' and 'whingers', Sorry, couldn't resist.

[Preran]

I apologize for your frustration. The whole point of having an open forum is to discuss what's not working and to get it fixed. It would be easy to go name calling, or to look for solutions, which is slightly harder.

I suggest writing to the product team with your issues Feature Request/Bug Report Form  They monitor the feedback religiously and use that feedback to log bugs after testing.

Thanks,

Preran

[Paul-M]

Adobe don't listen

ADDT (MX Kollection) - Buried - Bring It Back, update it.

Sever Behaviours > Left to rot and then removed - Bring back built-in MySQLi extensions so we can speed up our workflow

Design View - Left to rot  - Start updating it, Live View sucks!!

Live View - Horrible as already mentioned, jumpy/twitchy with some performance issues

Brackets Integration - A mess/limited, only for Brackets fans, sacrificed some very solid and familiar DW features for this ... WTH !!

New Find A Replace - What The Hell is this - the old find a replace was a great tool, this new one is a poor replacement !!

New Code Colouring Options - Limited - no language specific colouring - See: Brackets mode-aware code colouring - where is it in Dreamweaver?

Wrap Option removed from Snippets UI - Really, this defies common sense!!

See the forum for quite a few more gripes and issues from users.

Some of the other so called features added in recent years or latest 2017 release are

Emmet - Good to have it in there already but there was already a FREE Emmet extension that worked well in DW anyway.

Bootstrap Integration - Its missing features and needed more work - DMXZone offer a more comprehensive solution via paid extensions

Preprocessors -  DMXZone already offered a FREE extension that auto compiles LESS inside Dreamweaver and is a handy little tool

It's very frustrating - we're losing more and more good, familiar features so Adobe can plough on making more strange choices in what they do with Dreamweaver (presumably plans/roadmap laid out made years ago).