Action plug-in URL settings, such as url and the icon URLs (like icon16Url) can be defined relative to the URL (or the base URL) of the plug-in. This makes it possible to create a plug-in which can run directly in any Assets Server installation without having to change the URL setting.
Note. All URL's are without a trailing slash.
There are variables that can be used to create these relative URL's. Let's assume Assets Server runs under.
http.//www.myassetsserver.com
- ${pluginUrl}. plug-in folder URL.
http.//www.myassetsserver.com/plugins/<plugin_group>/<plugin_name>
- {pluginBaseUrl}. Base plug-in folder URL.
http.//www.myassetsserver.com/plugins/plugins_base/<plugin_group>/<plugin_name>
The following variables are also available and do not depend on your plug-in name.
- ${serverUrl}. Assets Server URL.
http.//www.myassetsserver.com
- ${pluginsRootUrl}. Active plug-ins folder URL.
http.//www.myassetsserver.com/plugins
- ${pluginsBaseRootUrl}. Base plug-ins folder URL.
http.//www.myassetsserver.com/plugins/plugins_base
- ${externalServerUrl}. Explicit base URL for web client e-mail links. See Access for external users.
http.//www.myexternalelvisserver.com
- ${externalAirClientServerUrl}. Explicit base URL for Pro client e-mail links. See Access for external users.
http.//www.myexternalelvisserver.com
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
0 comments
Please sign in to leave a comment.