I have a zxp file but it will not load into CS6 13.01. The extension manager goes through the mtions but it is simply not unpacking itself into the applications/adobe photoshop cs6/plugins/panels folders.
I am under the impression that this is a known issue after upgrading to 13.01.
Is is possible to unpack a ZXP file so I can manually copy the files into the Panels Folder ?
I have the same issue.
Extension Manager reports that my Extension itself is installed, but it is not located at the ../Plug-ins/Panels folder (where other Panels which I have installed directly from the Exchange are located). So resources my Panel needs to use are not found. A simple manual installation works OK.
I am using Configurator 3.1.1 - PS CS6 fully up-to-date for Windows.
Is there a fix?
If you have the original gpc file and associated .assets folder, and with Configurator 3.1.1 installed, you can open the gpc file with Configurator 3.1.1 and export it again as CS Extension, and to install with Extension Manager again by overwriting the installed extension.
As I wrote, I have used Configurator 3.1.1. And the manual installation from what is called "Exporting a panel for a direct install" in the Configurator User Guide is NOT a problem. The problem is with installing a panel via Extension Manager from what is exported as a ZXP package and then as a CS Extension. Where is the installation that Extension Manager performs? The User Guide states: "You can test the package by opening the target application and installing the Panel with Extension Manager." The fact that this doesn't work raised the original question in this thread (12 September) ....
Please refer to http://forums.adobe.com/thread/1016919
How do you find resources from your panel. If you access the resources via ExtendScript, new Folder(assetsPath) will point to the assets folder of your panel. If you access the resources via absolute path,
Please find the "assets" folder at:
Mac: /Library/Application Support/Adobe/CS6ServiceManager/extensions/
Windows: C:\Program Files (x86)\Common Files\Adobe\CS6ServiceManager\extensions
You are correct - the installation with Windows with Extension Manager has put my beta files at: C:\Program Files (x86)\Common Files\Adobe\CS6ServiceManager\extensions. That location is not mentioned at all within the Configurator User Guide.
I am NOT using the ESTK for my Extensions. So now, how should the author of an Extension write a relative path, good for the assets for both Windows and Mac, and test it, prior to submitting the Extension to Adobe for approval?
Below is the only script my Extension contains (it is the Open Script component I use in Configurator 3.1.1).
/* will unload any previous installation of the Actions Set */
var desc = new ActionDescriptor();
var ref = new ActionReference();
ref.putName( charIDToTypeID( "ASet" ), decodeURI(actionSet));
desc.putReference( charIDToTypeID( "null" ), ref );
executeAction( charIDToTypeID( "Dlt " ), desc, DialogModes.NO );
/* correctly loads or reloads the Actions file in the local option via Export Panel */
/* app.load(new File(" ../../Plug-ins/Panels/MyPanel/content/MyPanel.assets/MyExtension.atn" )); */
/* needs to load or reload the Actions file in the ZXP output option via Export Panel As CS Extension */
app.load(new File(" ../../Common Files/Adobe/CS6ServiceManager/extensions/MyPanel/content/Configurator -Panel.assets/MyExtension.atn"));
I simply need to know how to correct (or replace?) the last line so as to have this Extension work correctly from a properly installed ZXP file.
As I said before, you can refer to http://forums.adobe.com/thread/1016919
A global variable "assetsPath" is a string which points to the assets folder, and you need not to consider it is " ../../Plug-ins/Panels/MyPanel/content/MyPanel.assets/" or " ../../Common Files/Adobe/CS6ServiceManager/extensions/MyPanel/content/Configurator -Panel.assets/".
You can try
app.load(new File(assetsPath + "/MyExtension.atn"));
Thanks. I will try that. And post the result.
I did read through the earlier thread, several times - it was difficult for me to follow.
I think you (that is Adobe) will have to come to terms with the fact that there are lots of CS users out here who have long-time experience with the applications - especially Photoshop - but have no upfront knowledge of scripting. Their ambition will now be to share some of the features, innovations and workflows they have developed, with other users, via Configurator and Extensions and the new Exchange. So, it would be good if someone on your side could produce a set of useful, sample, and representative scripts for Configurator. (There was one opening for this in the recently published book "Power, Speed and Automation with Adobe Photoshop", by Geoff Scott and Jeff Tranberry. But it seems that there are no downloadable scripts made available via that effort at all - which is a shame IMHO.)
I like your idea and it's actually really easy to do. Just package up any scripts say for Photoshop with Adobe Exchnage Packager and submit them to Exchnage as a free or paid product. Details on Packager are here:
Hope that helps. Certainly we can get people submitting to exchange more regularly than we can do updates to Configurator.
hi Yanwen and Jonathan,
This is good news. Thanks. I'm sure that a lot of potential authors will find that helpful. There are some resources now being made available this way (as MXP packages) from the scripting community: http://sourceforge.net/projects/ps-scripts/files/ContactSheetX/v2.0_be tas/
Europe, Middle East and Africa