- **status**: open --> code-review
- **Comment**:
Closed #583. `je/42cc_7372`
---
** [tickets:#7372] Allow users to disable their own accounts**
**Status:** code-review
**Milestone:** forge-backlog
**Labels:** 42cc
**Created:** Wed May 07, 2014 04:12 PM UTC by Dave Brondsema
**Last Updated:*
While working on this I've discovered that `user_prefs.html` and relevant
controller does checks like this:
{% if tg.config.get('auth.method', 'local') == 'local' %}
Because of them `/auth/preferences/` is almost empty, when using LDAP auth
provider. I.e. you can't set display name,
- **status**: code-review --> in-progress
- **QA**: Dave Brondsema
- **Comment**:
I've used https://sourceforge.net/p/coils/code/ as a test case of a large
real-world hg repo. After cloning it locally and pushing into allura with the
latest forgehg & mercurial, I've found:
* The log view does
- **Size**: --> 2
---
** [tickets:#7381] Google code importer should handle Apache-Extras/EclipseLabs
projects**
**Status:** open
**Milestone:** forge-may-30
**Labels:** google-code import
**Created:** Mon May 12, 2014 02:12 PM UTC by Dave Brondsema
**Last Updated:** Mon May 12, 2014 02:12
---
** [tickets:#7399] JS errors on ticket bulk edit prevent submission**
**Status:** in-progress
**Milestone:** forge-may-30
**Created:** Fri May 16, 2014 04:44 PM UTC by Dave Brondsema
**Last Updated:** Fri May 16, 2014 04:44 PM UTC
**Owner:** Dave Brondsema
Errors about `multiselect` and `
- **status**: in-progress --> code-review
- **Comment**:
allura:db/7399
(Note, 2nd error was cascade effect from first)
Review Instructions:
* Edit production.ini and change build_key value and restart webserver. This
will ensure you don't get any cached resources
* Go to a ticket list and cl
- **status**: open --> closed
- **Comment**:
https://sourceforge.net/p/forge/documentation/SourceForge%20MediaWiki%20Importer/
---
** [tickets:#5190] No documentation on importing from MediaWiki into Allura
Wiki**
**Status:** closed
**Milestone:** forge-backlog
**Labels:** hostedapps support
Good catch. I think we'll need deeper updates to make it really work well with
LDAP though. LDAP will often provide names and email addresses, and may or may
not let users change those within Allura (e.g. have to change it somewhere else
in LDAP directly). So this will probably have to be con
