Outdated links to https://code.djangoproject.com/login

[googol]

Hi,

On https://code.djangoproject.com there are links which refer to https://code.djangoproject.com/login but that doesn’t work (e.g. "file a bug!": No handler matched request to /login

Also in the footer on: https://docs.djangoproject.com

If you notice errors with this documentation, please open a ticket and let us know! Please only use the ticket tracker for criticisms and improvements on the docs. For tech support, use the resources above.

links to https://code.djangoproject.com/newticket?component=Documentation which is broken.

Philipp

[Russell Keith-Magee]

Hi Philipp,

I'm not sure if someone has corrected something since you posted this, but in both cases, I don't get the behaviour you describe.

 * "File a bug" on the code.djangoproject.com homepage links to /newticket, not /login

 * "open a ticket" on the docs.djangoproject.com footer links to /newticket/?component=Documentation

In both cases, you get an "Error:Forbidden" if you're not logged in.

Can you confirm that this is what you're seeing now, or have I misunderstood your report?

That said, the error page also contains a "You are currently not logged in. You may want to do so now", with a link to the wrong login page (the Trac native login one, rather than the Github one). I'll look into this.

Yours,

Russ Magee %-)

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/1cd93a2c-9d76-4631-84c3-14c187cd8400%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Russell Keith-Magee]

Hi Philipp,

My apologies - it appears that the problem was fixed after you reported it, but before I saw your report. The problem was caused by a recent change to the way we handle authentication on our Trac instance; we're still sorting out some of the bugs.

Yours,

Russ Magee %-)