permission denied messages when approving account request

weird. I tried and it worked. I can't dive too deep right now, but I'll try to figure out why you got that error. Let me know if you see it again.

--Ethan McCutchen.....2014-10-12 03:32:59 +0000

I've been getting this also, for the past week or so I haven't been able to invite any new members...

--Lake Watkins.....2014-11-11 09:21:55 +0000

This particular site has some very old legacy problems. Most permissions seem to be set to "Administrative User", but that was replaced by "Administrator" when Eisenhower was president.

But there does appear to be a more general problem here that you need *read permissions on +*account cards to get this to work. On most sites you should be able to assign enough permissions to get around that, but the idea was that we were going to simplify this so that only permissions on Sign up and User cards were needed. Will ticket.

--Ethan McCutchen.....2014-12-02 20:14:32 +0000

Ok, so as of the last update users can be invited but they still can't verify their accounts. The link in the automated email sends them to a 404 (it should be "/update/user+*account"). I tried changing permissions on account cards to allow anyone to read/update (just temporarily), but the permissions keep defaulting back to administrator only. This is quite frustrating! There must have been a bad update or something, because I wasn't touching the accounts or other permissions before this block came up.

--Lake Watkins.....2015-02-13 09:56:14 +0000

OK, so if I understand correctly:

1. the verification email is going out

2. the card named "verification email" (type: "email template") includes a link to something like {{_|verify url}}

3. that url is getting a not found error.

That's already rough, and from there it gets more confusing to me. The url is bad, but there was something else that suggested there was a permissions issue? And then you're editing permissions and it's somehow reverting on its own??

I'd really like to help you fix this. Can you send me:

1. an example of the verification url that is getting sent out

2. the relative root path of your wagn (is it running on the root, like http://whatever.com/ or within a path like http://whatever.com/mywagn)?

3. some detail about what exactly you're changing permission from and to

4. where you're seeing it default back to administrator, and

5. the exact version of Wagn that you're running?

If you prefer, you can send any/all of this to support@wagn.org.

--Ethan McCutchen.....2015-02-13 16:46:08 +0000