It's also fixed in stable - the release right before the community
conference includes a bug fix for that fixes the URL generated for that
link.
--nate
Kanwei Li wrote:
Fixed on trunk by setting a default cntrller when there isn't one.
-K
On Thu, May 26, 2011 at 2:16 PM, Dave Walton
Hello Dave,
Can you clarify how your users are accessing the following URL
http://galaxy.jax.org/user/create
I originally assumed they were using the Galaxy UI to register by clicking the
Register link on the User popup menu. However, perhaps they are just
pointing their browser to the
I just checked,
Using the User-Register menu works, however we require our users to log in so
when they go to galaxy.jax.orghttp://galaxy.jax.org they are redirected to a
login page if they are not already logged in. That page has the text This
installation of Galaxy has been configured such
Hi Glen,
I've never seen this before, but perhaps your user controller is using an old
version ( I'm just grasping here, because this is pretty obscure behavior ).
Try deleting the following file - make sure it is the .pyc file.
~/lib/galaxy/web/controllers/user.pyc
The user controller
Just removed user.pyc and restarted the server. Did not resolve the problem.
Dave
On 5/26/11 8:09 AM, Greg Von Kuster g...@bx.psu.edu wrote:
Hi Glen,
I've never seen this before, but perhaps your user controller is using an old
version ( I'm just grasping here, because this is pretty
Greg.
We do not use the template_cache_path in our config. I deleted all the
files in ~/database/compiled_templates and restarted my server. I still get
the error (even with a shift reload of my browser). I've tried it (on the
Mac) with Firefox 3.5.2, Safari 5.0.5 and Google Chrome 11.0.696.71
Greg,
We've tried just reloading the browser and that didn't do anything.
As for deleting the cached templates, on our development server I tried
deleting everything under the database/compiled_templates directory (I even
restarted my server) and it appeared to have no affect. We still get the
Hi Dave,
If you do not have a template_cache_path config setting in universe_wsgi.ini,
then your cached templates are stored in the default directory of
~/database/compiled_templates.
Deleting your cached templates in ~/database/compiled_templates should have
corrected the problem, assuming
