Menu

#196 Improve how urls to resources get stored in a pipeline file

HEAD
closed-fixed
None
5
2015-06-19
2015-05-15
No

Currently, a pipeline stored in the root plugin directory, loading that plugin refers to the plugin directory using the URL string "$relpath$../PluginDir/". This can cause problems, e.g. if the plugin is extracted under a different name.

The correct way to refer to the plugin directory would be "$relpath$"

Another problem is that symbolic links do get resolved when the URL relative to $relpath" is calculated. For example if a pipline refers to a directory "dir" that is in the same directory that also contains the pipeline file, then the URL string should be "$relpath$dir". If dir is a symbolic link to a directory "otherdir" stored two levels up, this currently gets resolved to "$relpath$../../otherdir" but keeping "$relpath$dir" would be preferable.

Discussion

  • Johann Petrak

    Johann Petrak - 2015-06-19

    This has been fixed with the fix for issue #201

     
  • Johann Petrak

    Johann Petrak - 2015-06-19
    • status: open --> closed-fixed
     

Log in to post a comment.