<div dir="ltr">Hi Guillermo,<div><br></div><div>Thanks for spotting this. The issue is fixed in ensembl-vep 88.9 (<a href="https://github.com/Ensembl/ensembl-vep/commit/21069f158e4081ffc44d5389852a0e3da71fd7ff">https://github.com/Ensembl/ensembl-vep/commit/21069f158e4081ffc44d5389852a0e3da71fd7ff</a>).</div><div><br></div><div>Regards</div><div><br></div><div>Will McLaren</div><div>Ensembl Variation</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 17 May 2017 at 07:45, Guillermo Marco Puche <span dir="ltr"><<a href="mailto:guillermo.marco@sistemasgenomicos.com" target="_blank">guillermo.marco@sistemasgenomicos.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000066">
<p>Dear devs,</p>
<p>I've noticed a bug in latest VEP 88 version. If you activate more
than one plugin, one in the config file and other directly in
command line all the annotation fields produced by plugins are
rendered empty. See the example below (my.conf would be the config
file containing a line activating plugin):<br>
</p>
<pre><b>vep -i input.vcf -o output.vcf -config my.conf -dir_plugins dir_plugins -dir_cache .vep -plugin Test</b><b>
</b></pre>
<p>I've managed to make this work "calling" all the plugins from
command line.</p>
<p>Regards,<br>
Guillermo<br>
</p>
<p><br>
</p>
</div>
<br>______________________________<wbr>_________________<br>
Dev mailing list <a href="mailto:Dev@ensembl.org">Dev@ensembl.org</a><br>
Posting guidelines and subscribe/unsubscribe info: <a href="http://lists.ensembl.org/mailman/listinfo/dev" rel="noreferrer" target="_blank">http://lists.ensembl.org/<wbr>mailman/listinfo/dev</a><br>
Ensembl Blog: <a href="http://www.ensembl.info/" rel="noreferrer" target="_blank">http://www.ensembl.info/</a><br>
<br></blockquote></div><br></div>