Modify

#10307 closed defect (invalid)

Trac 1.0 compatibility

Reported by: syu@… Owned by: hasienda
Priority: normal Component: AccountManagerPlugin
Severity: normal Keywords: regression admin
Cc: Trac Release: 1.0

Description

This plugin doesn't seem to work with 1.0. The admin contributions are no longer there. I think maybe some of the contribution API got changed.

Attachments (0)

Change History (4)

comment:1 Changed 22 months ago by hasienda

  • Keywords regression admin added

First and foremost I do love early adopters, so new issues pop up within hours and days, not weeks or months. Thanks for taking care.

It would have been sensible to declare your AccountManagerPlugin revision, but likely you've checked-out trunk after on 10-Sep-2012 or later to update an existing Trac application. If I'm right you'll find [11959] very enlightening on your reported issue.

Short to get you going again:

 [components]
-acct_mgr.admin.AccountManagerAdminPanels = enabled
+acct_mgr.admin.AccountManagerAdminPanel = enabled

Hint: read changelog, README.update or recent commit history as I tend to be quite verbose about what I'm doing.

This is in no way related to Trac API (changes) as you suspected. Even more, with that assertion you should rather have commented and reopend #10241, right? Btw, I'm developing against Trac 0.11 and 1.0dev in parallel here, so such a severe regression would come out as a big surprise, but to err is human, of course.

comment:2 Changed 22 months ago by hasienda

PS: As a matter of fact, I did instantly alter available wiki documentation here to reflect the current component name (as well as the upgrade notes as mentioned above). Assuming, that I'm guessing right about the root cause of your issue, it would be another case of RTFM.

Maybe I'm just a bit exhausted. At occasions like this time for doing documentation seems like wasted time, so don't take this rant of mine too personal, please.

comment:3 follow-up: Changed 22 months ago by syu@…

Thanks for the quick response. Wow you read my mind, yes I'm using trunk from yesterday. I currently have this in my trac.conf

[account-manager]
htpasswd_file = /data/trac/.htpasswd
htpasswd_hash_type = md5
password_store = HtPasswdStore
user_lock_max_time = 0

[components]
acct_mgr.admin.* = enabled
acct_mgr.htfile.htpasswdstore = enabled

I turned up the logging level to DEBUG. I don't see anything unusual except the last part.

2012-09-11 14:48:04,161 Trac[loader] DEBUG: Loading acct_mgr.admin from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,165 Trac[loader] DEBUG: Loading acct_mgr.api from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,165 Trac[loader] DEBUG: Loading acct_mgr.db from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,165 Trac[loader] DEBUG: Loading acct_mgr.htfile from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,165 Trac[loader] DEBUG: Loading acct_mgr.http from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,166 Trac[loader] DEBUG: Loading acct_mgr.macros from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,166 Trac[loader] DEBUG: Loading acct_mgr.notification from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,167 Trac[loader] DEBUG: Loading acct_mgr.pwhash from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,167 Trac[loader] DEBUG: Loading acct_mgr.svnserve from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
2012-09-11 14:48:04,167 Trac[loader] DEBUG: Loading acct_mgr.web_ui from /usr/lib/python2.6/site-packages/TracAccountManager-0.4dev_r11963-py2.6.egg
....
<abbreviated>
....
2012-09-11 14:48:04,284 Trac[authz_policy] DEBUG: Checking ACCTMGR_CONFIG_ADMIN on *:*@*
2012-09-11 14:48:04,284 Trac[perm] DEBUG: No policy allowed syu performing ACCTMGR_CONFIG_ADMIN on None
2012-09-11 14:48:04,284 Trac[authz_policy] DEBUG: Checking ACCTMGR_USER_ADMIN on *:*@*
2012-09-11 14:48:04,284 Trac[perm] DEBUG: No policy allowed syu performing ACCTMGR_USER_ADMIN on None

Also I don't see the ACCTMGR permissions in trac-admin permission list

comment:4 in reply to: ↑ 3 Changed 22 months ago by hasienda

  • Resolution set to invalid
  • Status changed from new to closed
  • Summary changed from Trac 1.0 compatiability to Trac 1.0 compatibility

Replying to syu@brightedge.com:

Thanks for the quick response. Wow you read my mind, yes I'm using trunk from yesterday. I currently have this in my trac.conf

[account-manager]
htpasswd_file = /data/trac/.htpasswd
htpasswd_hash_type = md5
password_store = HtPasswdStore
user_lock_max_time = 0

[components]
acct_mgr.admin.* = enabled
acct_mgr.htfile.htpasswdstore = enabled

...

Also I don't see the ACCTMGR permissions in trac-admin permission list

Obviously I was only close, not at the spot. The behavior described by you is for a reason: You didn't enable the core component yet. It's acct_mgr.api.AccountManager, that is providing plugin's permissions as well. Makes sense?

Take a look at the wiki documentation please, to see what functionality you want and what components you'll need to get it. Documentation might not explain everything, but it would have easily answered all your questions until now. You can hardly expect to have the form-based login without enabling acct_mgr.web_ui.LoginModule, just to speak of another possible upcoming hurdle.

I hope, that by now you've spotted the general patter. For more questions search the MailingList, trac-hacks.org one's as well as Trac's (see t:wiki:MailingList) and ask, if you can't find the answer there. Developers read these lists and won't let you down, no need to try forcing support here, ok? Contact me or another trac developer/user on IRC channel #trac at irc.freenode.net, if you get totally stuck. See you there, and good luck.

This ticket system is dedicated to development, not support, again for good reasons: List threads have much better visibility than closed tickets.

Add Comment

Modify Ticket

Action
as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from hasienda. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.