Hi

Third post in about as many minutes

In this post I talk about different access levels. I am not sure if this question ties into it or not. It does for me.

Due to legal requirements we must validate a person's registration request by ensuring they are a resident in our neighbourhood before allowing them access to private pages. This can be done by not sending the verification email after registration, but some other thank_you.php mail. We do our validation check and all is good. What now?

The verification email can now be sent, but this seems to require some serious fiddling.
Alternatively, once the validation is done, the user can be changed to a 'full user' with access to private pages in the Admin Dashboard -> User Panel. Also sounds like serious chopping and changing.

I don't know enough to know if either of these options are good or elegant. The whole registration process also becomes messy. Any suggestions/solutions are welcome.

Thanks
Pierre

Hi

I would like to have a dropdown list in a form in US 4.2.9. How can I create this? Is it as simple as using HTML select? Keep in mind I don't have any PHP knowledge.

Thanks
Pierre

Hi

I'm quite new to US, so please be patient. Using 4.2.9 for a web site and things are working out quite well. To the point where I am now stuck. US provides for 2 levels of access to pages - public or private. To view private pages you need to be logged in.

I require a third level - call it most private if you want - that requires even further registration. The registration is not the issue, but the more restrictive level of page access is.

The scene: This is a website for the community I live in, approx 300 households. There is information on the site that anybody (public) should be able to view, say prospective property buyers, etc. Then there is information should only be available to residents (private) because it does not concern the general public. Lastly we have a neighbourhood watch and these pages contain information that only members of the neighbourhood watch may access - most private.

Keeping in mind I know fairly little about the inner workings of US, and I have no prior knowledge/experience with PHP, how can I go about creating this more restrictive level of access?

Thanks
Pierre

Just to mention what I have been able to do with US as "evidence" of my complete lack of knowledge re PHP:
1. Some customization, e.g. a require_once carousel below the menu. This was very basic and easy to do.
2. Added 3 fields to the registration form to write additional data to MySQL. Also basic and easy.

No matter what I put, I'm getting some sort of "already exists or cannot be created" error.

http://puu.sh/xnpxj/7c77cdf950.png

One thing that we might want to consider is that the backup function allows any admin to download the full source code and db of a project that might be closed source. I had to take away several people's admin privileges on my own projects because of this. What are your thoughts on making backups master only? Or maybe if we take away some of the messages, all admins could hit the backup button, but not see any of the logging or download backups?

These were all Brandin's fixes. Cron manager updates and permission fixes primarily. Thanks Brandin!

I had hoped to add more to this myself, but Brandin carried the load on this one. His Cron Job tool is available at the top of the dashboard as well as the stuff from this post...
https://userspice.com/forums/topic/statu...#post-5604

My main contribution was changing a <? to a <?php in admin_page.php

Is there a way to only allow people with a specific domain in their email to be able to register?
I cant seem to find any documentation on that?

Thanks

I would love to add a field for the phone number in my join.php. Maybe somebody can help me.

Feel free to tackle something or let me know that I'm missing something.

https://docs.google.com/spreadsheets/d/1...TVArlqrmZA