Hi Ryan,

I still think it's a javascript problem (most of the fancy DHTML tricks in 
galaxy, like expanding/collapsing datasets, are done in javascript - so when 
something like that doesn't work, it's a good place to start).

First indication:
If you go to your galaxy server with Firefox and open the "JavaScript error 
console", you'll see the following error:
=====
Error: $.jStore is undefined
Source File: http://XXXXXXXXX.XXXXX.edu/galaxy/static/scripts/galaxy.base.js?v=8
Line: 1
=====

Just to be sure, this is not a real galaxy bug, this is a mismatch between what 
should be the correct javascript and the actual javascript that you are using.

So the next step is to see if there are real differences: compare the 
javascript you have with the one you're supposed to have (if you've updated to 
the latest galaxy-dist):

====
## Download your version:
$ wget -O galaxy.base.js 
'http://XXXXXXXXX.XXXXX.edu/galaxy/static/scripts/galaxy.base.js?v=8'

## Download galaxy's version:
$ hg clone http://www.bx.psu.edu/hg/galaxy galaxy-dist

## compare them:
$ ls -l galaxy.base.js  galaxy-dist/static/scripts/packed/galaxy.base.js
-rw-r--r-- 1 gordon hannon 8787 Apr 11 16:11 
galaxy-dist/static/scripts/packed/galaxy.base.js
-rw-r--r-- 1 gordon hannon 9020 Feb 21 13:48 galaxy.base.js
=====

# Obviously, they are not the same.
# Assuming "wget" maintains the file's actual date (Yours is from Feb. 21st), 
then I can assume you're still using an older version of the javascript file.

Perhaps you've pulled but didn't update ?
Or merged and took the wrong version ?

Check the actual file on your disk to continue and debug it,
but IMHO it's definitely a javascript mismatch problem.

Hope it helps,
 -gordon




Ryan Golhar wrote, On 04/11/2011 03:13 PM:
> I restarted the galaxy daemon, apache, and cleared my cache.  Still didn't 
> help.  I'd be happy to share the URL of my instance via private email if 
> it'll help.
> 
> 
> On 4/11/11 3:05 PM, Assaf Gordon wrote:
>> Couple of voodoo things to try:
>> 1. Manually clean the cache of your web browser
>> 2. Restart your apache/nginx
>>
>> Depending on your last update revision, it's possible that some of your 
>> javascripts were updated by the latest pull, but your webbrowser maintains a 
>> cached older version.
>>
>> Those are the two things I'd try first.
>>
>>

___________________________________________________________
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/

Reply via email to