Skip to main content
P
poorpaddy
Participating Frequently
March 9, 2013
Question

Directory path not working in CS6

  • March 9, 2013
  • 1 reply
  • 3848 views

I have an extension that I am updating for Dreamweaver CS6. Here's the link on Adobe: http://www.adobe.com/cfusion/exchange/index.cfm?event=extensionDetail&extid=2430523

The gist is during install it provides the user with the option select a custom save directory for KDF files (proprietary extension but is xml). This directory is referenced when creating template files (KTF) later on (proprietary extension but is html). It was working perfectly fine in Dreamweaver CS4-CS5.5 on OSX & Windows however in CS6 it doesn't remember the users directory selection.

<token name="KDF" prompt="Descriptor Files (Save all .KDF files here)" default="$dreamweaver/configuration/Blackbaud/Templates/KDF" />

I began by of course doing tons of research only to find Adobe removed support for the prompt & default attributes from tokens in the mxi file which I think isn't true since that portion actually still worked. Eitherway I listened and tried to change it accordingly as they suggested as seen below:

<token name="KDF" definition="$dreamweaver/configuration/Blackbaud/Templates/KDF" />

Turns out it can't find the directory either which I know should work or the plugin UI would fail because I have a few other tokens doing the same thing for assets.

My best guess is the error is within "Shared/CMS/Scripts/CMN/UI.js" since that is where the GetCustomPath function is located and also where the error message is defined. I have included a slink to the source files if someone would like to take a stab.

I define GetCustomPath() at the top and then call upon it starting on line 482 of UI.js.

http://truimage.biz/Sphere160.zip

Help in troubleshooting as to why this is no longer working in Cs6 would be very much appreciated.

This topic has been closed for replies.

1 reply

sudarshan.t
sudarshan.t
Inspiring
March 9, 2013

The extension you're talking about is not 'officially' supported by CS6. Look at the extension detail page in the URL you've given us. The last published date is also about 2 years ago - you may want to contact the developer to see if they have made it CS6 compatible yet.

P
poorpaddyAuthor
Participating Frequently
March 9, 2013

@Sudarshan,

If you read the first line one might be hinted that I am the developer. When more of the message is read someone might understand that the extension hasn't needed to be updated in 2 years because it simply worked. Adobe has changed something in CS6 and like usual the extension development documentation is lacking and thus I posted on this thread for help because I have no idea what changed.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices