Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#434 closed enhancement (wontfix)

Base1PluginExecuter option enhancements

Reported by: base Owned by: Johan Enell
Priority: minor Milestone: BASE 2.1.1
Component: coreplugins Version: 2.1
Keywords: Cc:


(using BASE 2.1 (2847) on Solaris 10 / Tomcat 5.5.17 / JDK 1.5.0_08)

Some of our BASE 1 plugins generate several files (images etc), all connected through an index html file generated by the plugin. Base1PluginExecuter by default moves these files to the flat namespace of the uploads directory, making it impossible for the index file to use these files. For use with these legacy plugins, it would be nice if Base1PluginExecuter:

  • offered an option to retain the ExecDirectory used (in db.uploads or elsewhere)
  • used a customizable directory instead of the system tmp.dir

i.e. something similar to the BASE 1 "jobs" directory hierarchy.


Change History (2)

comment:1 by Nicklas Nordborg, 17 years ago

Resolution: wontfix
Status: newclosed

The Base1PluginExecuter already keeps the directory structure as generated by the plugin on the BASE file system. The internal location of the files are not kept and that is intentional.

in reply to:  1 comment:2 by base, 17 years ago

I realise this - all I wanted was the option to retain the temporary files and directory structure (outside of $userfiles) and also specify the location (e.g. for use by other services).

Now, fixing ticket #433 removes our immediate need for this (the filemanager automagically rewrites relative links for internal objects - sweet!), so never mind... :-)


Note: See TracTickets for help on using tickets.