Hi Steve,

You are on the right track, but something in the WAV file has
triggered one of Galaxy's security protections to try to block
uploading of potentially dangerous files. There may be some
settings here you can relax - I've not had to deal with this


On Fri, Oct 21, 2016 at 8:55 PM, Steve Cassidy <steve.cass...@mq.edu.au> wrote:
> Thanks all,
>   it seems that my real problem is that the audio file (.wav) is not being
> identified as a valid datatype and ending up as a zero length text file. So,
> I need to start to explore the world of datatypes.
> Following the docs
> (https://wiki.galaxyproject.org/Admin/Datatypes/Adding%20Datatypes) I can
> modify datatypes_conf.xml in my Galaxy sources and add a new datatype for
> wav files:
>     <datatype extension="wav" type="galaxy.datatypes.binary:Binary"
> display_in_upload="true" mimetype="audio/wav" subclass="True”/>
> but, I get a message "The uploaded binary file contains inappropriate
> content” and a zero length file just as I did before adding this - although
> the datatype is now set to ‘wav’.
> I didn’t add a sniffer for this and set the datatype explicitly on upload.
> Also, this doesn’t seem like a modular way to add datatypes - how do I
> include datatypes in my tool definition?  I can see from some other tools
> that I include a datatypes_conf.xml in my tool folder.   When I try that and
> test with planemo the new type isn’t found.
> Pointers welcome.
> Thanks,
> Steve
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:

To search Galaxy mailing lists use the unified search at:

Reply via email to