Big problem trying to install a self-registering form

GuyVerville · 2011-10-10 13:17:55

So your Install Wizard link is trying to go to http://site.com/textpattern/index.php?event=self-reg&step=preinstall&area=admin and failing?

Exactly.

Bloke · 2011-10-10 13:22:09

And you have Publisher privs? And you haven’t altered the mem_self_reg privs through smd_user_manager? (In fact, it might pay to temporarily switch off smd_um just to make sure it’s not getting in the way).

If it’s not that, I’m stumped. Hope someone else can see what I can’t.

GuyVerville · 2011-10-10 13:27:06

I have administrator’s rights (I am the only one with myself :-) ) I did switched off and even removed everything regarding users (was a little fed up!), then I gave it a try and nope. I see that the plugin author seem to look at problems. Maybe I should just try to contact him.

Bloke · 2011-10-10 13:34:28

Yeah, raise a ticket over at BitBucket and see if Manfre has any ideas. Sorry I couldn’t get to the bottom of it this time.

GuyVerville · 2011-10-10 13:35:24

No need to be sorry. You were very helpful!

aslsw66 · 2011-10-10 15:03:36

Pretty sure I’ve had the same problem. I set the default user privs to 1 initially, and couldn’t change after that. I could the see the preference there, and change all of the mem_self_register preferences except for that one. But I might not be running the latest version any more…

By the way, it took me ages to get my head around the way privileges escalate from 0 to 6 to 1 ie. 0 > 6 > 5 > 4 > 3 > 2 > 1. Sure a strictly linear escalation would make more sense?! It still catches me out from time to time. I have discretely added it to the page so I can always check that the right person is getting the right access.

Bloke · 2011-10-10 15:31:58

aslsw66 wrote:

By the way, it took me ages to get my head around the way privileges escalate from 0 to 6

You count from zero? :-P

Meh, history. To be totally accurate though, a Designer isn’t ‘lower than’ a Freelancer; they just have different capabilities. And ‘zero’ is just that: zero access, so I suppose it makes sense in that regard. Uhhh, sort of.

I have discretely added it to the page so I can always check that the right person is getting the right access.

You could always use smd_faux_role and set the plugin up to always display the user dropdown so testing of other privs is just a click away.

Last edited by Bloke (2011-10-10 15:32:21)

aslsw66 · 2011-10-10 20:38:08

Yeah, I get that the privileges is really about different roles but I also think that there is also a natural escalation of roles in lots of systems. It might be easier if we could mix-and-match privileges.

Your shameless plugs will fall on deaf ears unless there is a public side tag. You see, I am continuing to build a customised front-end admin console. This is mainly because our officers are older, tech-fearing guys; if it looks to complicated, they won’t use it but then complain that the site is out-of-date and too hard. By customising those bits they will actually regularly use, I can try to design it in the easiest way for them (while still maintaining full control myself at the real back-end). At the moment, all I need them to do is simple article management (add, edit, delete with restricted categories) and user management.

Bloke · 2011-10-10 21:04:44

aslsw66 wrote:

It might be easier if we could mix-and-match privileges.

You can make your own rules with smd_user_manager and set an assumed hierarchy (damn, another plug).

I am continuing to build a customised front-end admin console

Any reason you haven’t considered an admin-side dashboard or three? smd_um to make a new role for the tech-fearing guys, with no privs to see any tabs except a few that you create with smd_tabber. On those tabs you put whatever custom simplified workflow you want with Page templates and Stylesheets, etc. You then use rvm_privileged to wrap Edit links on the pulic side to the dashboard tabs so anyone logged in as this new role can make changes. They use the standard Txp login screen to log in (therefore no ign_pw_protect required) and the dashboard has convenient links back to the public side to see the results. Skin the admin side to match the public side as close as possible and your user base will hardly know they’re jumping between the two.

Oh, and smd_um gives you the ability for people to alter their own profiles out of the box. I’m considering allowing you to open up the permissions for smd_um itself too; at the moment they are fixed to Publishers. Easy change: requires three lines removing. And maybe a pref to govern whether it’s allowed or not. If you need that now, just yell and I’ll shift it up the priority tree.

Last edited by Bloke (2011-10-10 21:06:25)

aslsw66 · 2011-10-11 11:45:06

I could list my ‘reasons’, but somehow I expect that each of them will be met by a response that includes reference to smd_something_or_other.

If I’m honest, then I would say because I’ve alway found it easier to work up from a blank page, rather than take the default out of the box and try to adapt it – it’s how I do everything from web design to landscape gardening. Also, I am building some custom functionality which doesn’t seem to ‘naturally’ fit at the back end; for example:

a new table with training qualifications and then keep track of which member has which qualification, and when that qualification expired,
crews and rosters so that people know when they are rostered on.

I guess that if smd_tabber can take any custom content, then those are easy enough. I know just need to learn customise the admin side (skins, remove content, re-arrange content, etc).

I’ll play around with smd_tabber first and post questions/issues over on it’s support thread.

Bloke · 2011-10-11 14:13:32

aslsw66 wrote:

I could list my ‘reasons’, but somehow I expect that each of them will be met by a response that includes reference to smd_something_or_other.

OK, point taken, I’ll back off the self-promotion. Your approach of building up from scratch is perfectly valid. I was just offering counterpoint to potentially save you some headaches because of the occasional ign_pw_protect issue that can crop up in later Txp versions. rvm_privileged is more reliable because it uses Txp’s login mechanism. The downside being it uses Txp’s login mechanism and not a layout-controllable public-side login form.

But the advantage to using a tab is that you don’t have to code the rest of the access logic by hand. You create the tab, write txp:tags exactly like you would on a front-facing-page and use something like smd_um or bot_privs to determine who can see the tab. Txp does the rest. You can then hop visitors between front and admin-side to suit your desired workflow. The major potential downside is that if you need to publicly display the training qualifications table or roster then you’ll need to write that bit out on a public-facing page and also write some of the same code on the admin-side for those privileged few that can edit the details. That may be desirable from a workflow perspective but if you strive for the ‘wiki-ish’ approach of editing in-place, coding it entirely on the public side may well suit you better as you only need to write stuff once. Of course Forms can help with reuse :-)

As one further adjunct to this, you can still use rvm_privileged and Txp’s login mechanism even if you go completely front-side-loco. You just have to bounce any login links to /textpattern and then on the dashboard page that is shown to such techs on first login, either automatically redirect them back to the front-end, or offer a few “what do you want to do now” options on that dashboard, one of which may be a link back to the front of house.

Is this waaaay off topic now or what?

admi · 2014-01-23 12:33:57

Bloke wrote #253457:

Hmmm, have you got the latest version from Manfre’s BitBucket site?

Hi Bloke!

Let me clarify some points. May be, I misunderstood something.

I have been struggling with mem_self_register:

1. I need bcc to be sent to admin when a new user is registered (txp:mem_self_register_form admin_bcc=“1” does not work)
2. I need freelancer priviledge confered on newly registered user by default (As far as I know this one is set up in Admin – Preferences – Advanced but I also see nothing there)

I am using txp 4.5.5 and mem_self_register 0.9.11 + mem_form 0.8.4

Is there anything I do in a wrong way?

Textpattern CMS

Textpattern CMS support forum

#16 2011-10-10 13:17:55

Re: Big problem trying to install a self-registering form

#17 2011-10-10 13:22:09

Re: Big problem trying to install a self-registering form

#18 2011-10-10 13:27:06

Re: Big problem trying to install a self-registering form

#19 2011-10-10 13:34:28

Re: Big problem trying to install a self-registering form

#20 2011-10-10 13:35:24

Re: Big problem trying to install a self-registering form

#21 2011-10-10 15:03:36

Re: Big problem trying to install a self-registering form

#22 2011-10-10 15:31:58

Re: Big problem trying to install a self-registering form

#23 2011-10-10 20:38:08

Re: Big problem trying to install a self-registering form

#24 2011-10-10 21:04:44

Re: Big problem trying to install a self-registering form

#25 2011-10-11 11:45:06

Re: Big problem trying to install a self-registering form

#26 2011-10-11 14:13:32

Re: Big problem trying to install a self-registering form

#27 2014-01-23 12:33:57

Re: Big problem trying to install a self-registering form

Bloke wrote #253457:

Board footer