I was unable to reproduce this problem. Can you supply more details -
what path did you take through the UI to get that URL? Is that
restricted to just some workflows or do all workflows have this
problem as far as you can tell?

I guess ultimately the reason that workflow isn't downloading is that
it doesn't seem to have a user associated with it. The route should be
 /u/<username>/w/<workflow_slug>/json-download.
/u/w/myworkflow/json-download doesn't appear to have a user name. Any
clue how that happened? Do all newly created workflows have that same
issue with your Galaxy instance?

Sorry I have not been of more help.
-John

On Sun, Oct 12, 2014 at 10:50 AM, Wolfgang Maier
<wolfgang.ma...@biologie.uni-freiburg.de> wrote:
> Dear all,
>
> our local Galaxy does not seem to be able to export workflows anymore,
> instead fails with, for example:
>
> Not Found
>
> The resource could not be found.
> No route for /u/w/myworkflow/json-download
>
> We are running latest_2014.10.06 .
> Has anyone else experienced this ?
>
> Thanks,
> Wolfgang
>
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
>  http://lists.bx.psu.edu/
>
> To search Galaxy mailing lists use the unified search at:
>  http://galaxyproject.org/search/mailinglists/
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to