Cross-cancer queries not functioning

[Róisín-Ana Ní Chárthaigh]

Hi,

I have been trying to run some cross-cancer queries for single genes through the cBioPortal website.  However, searching across all cancers, or any more than one study, results in the following 'Modify query' page.

Also any links on the website (or other sites e.g. CTD2 Dashboard) to cross-cancer queries result in the same page, so I don't think it's an error on my part.

I am particularly keen to use the RNA-seq expression across cancers tool that was introduced in December.  Do you know when this might be fixed?

Many thanks.

[JianJiong Gao]

Hi,

Sorry for the problem. Unfortunately I could not reproduce the issue.
I have tried Chrome, Firefox, Safari and IE11. It might be due to some
caching issue in your browser. Could you try to clean your browser's
cache (http://www.wikihow.com/Clear-Your-Browser's-Cache) and try
again? If the problem persists, please let us know your browser
version and os version?

Thanks,
-JJ

On Fri, Mar 18, 2016 at 1:20 PM, Róisín-Ana Ní Chárthaigh
<ra.nich...@gmail.com> wrote:
>
> Hi,
>
> I have been trying to run some cross-cancer queries for single genes through the cBioPortal website. However, searching across all cancers, or any more than one study, results in the following 'Modify query' page.
>
>

> Also any links on the website (or other sites e.g. CTD2 Dashboard) to cross-cancer queries result in the same page, so I don't think it's an error on my part.
>
> I am particularly keen to use the RNA-seq expression across cancers tool that was introduced in December. Do you know when this might be fixed?
>
> Many thanks.
>
>
>

> --
> You received this message because you are subscribed to the Google Groups "cBioPortal for Cancer Genomics Discussion Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cbioportal+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[ra.nich...@gmail.com]

Hi,

Thanks very much for the tip.  Clearing the cache has solved the problem for Chrome.  I still can't get it to work on Firefox for some reason, but it's not a real problem if it works with Chrome. 

Thanks for the great resource!