Hey!

I was just curious about how to use the allowed/denied domains for new user registration in JomSocial site configuration settings.

So I am assuming that "allowed domains" means you can set the format domain for certain email types?

I am making a niche social networking website for college students and would like to be able to restrict new user registration to emails that end with a .edu only.

I am hoping this feature would allow me to only accept emails for example This email address is being protected from spambots. You need JavaScript enabled to view it. or This email address is being protected from spambots. You need JavaScript enabled to view it. etc.

Is my understanding correct or does "allowed domains" mean something completely different???

Thanks!

Hi, Alex.

You're close :) This settings allow to restrict members to use during registration emails ONLY in certain domain e.g test.eu.
It won't work with wildcard e.g *.eu.

Okay sounds perfect for my needs then :)

I am in the process of cloning my entire site into multiple instances of sub-domains for different colleges and universities.

The end goal is to migrate my entire site into multiple EC2 instances with different sub domains for different colleges and universities with each EC2 instance having an ss3 bucket and then use cloud front/flare CDN to communicate between EC2 instance and ss3 bucket.

For now I am just going to stick with the hosting I currently have or switch over to Linode, RackSpace, or DigitalOcean.

I remember reading an article you guys had about migrating to Digital Ocean for pretty cheap and awesome performance, do you guys have any recommendations?

I have also thought about just using cloudaccess.net since they are very strong Joomla! community supporters and I want to support the Joomla! community.

But anyway, so please let me know if my thought process for executing this next step to my website project sounds correct.

I am going to make a custom page in native JS registration with a custom field for selecting college/university.

After new user selects college/university I will then redirect the new user to the correct sub-domain for their school to continue the rest of the normal native JS registration process which would then be an instance of my current setup with domain restriction for ONE exact school such as This email address is being protected from spambots. You need JavaScript enabled to view it. with the sub-domain harvard.academia.rocks

At first I am only going to support a few schools that I am launching at and then later support more schools as my company grows.

So would it work to have a custom registration page in native JS registration that upon college selection redirects to the correct sub-domain and then each sub-domain would be a custom version of cloning my current website setup?

So if each sub-domain is a clone of current setup I could then implement restricting registration to just ONE school for that sub-domain correct?

Thank you for clarifying this for me :)

And please let me know if there are any other ways to have separate isolated clone sites for different colleges :P

I believe cloning site and making sub-domains and having each sub-domain be independent stand alone site from all other sub-domains with own users, newsfeed, and database etc is the easiest way and most scale-able.

I think that's how fb originally started and then later they found a way in back-end to connect everyone and make everything searchable and connected, but for now sub-domains and isolated non connected communities will work for now :P

Other method would be academia.rocks/school/JSfrontpage instead of school.academia.rocks/JSfrontpage

But this method would require setting up complicated database tables that branch off of one instance of website public.html rather than just cloning public.html and making that into a bunch of different sub-domains.

What do you think?

Thanks!

Hi, Alex.

As for hosting service - please ask in our Community if other member have recommendations for and experiences with popular providers.

Redirecting to correct subdomains during registration is rather bad idea. It's because first fields in JS registrations are obligatory Joomla! fields. Filling them will already create Joomla account. So I think that the best idea will be to create simple custom page - even in HTML with first question about college/university. Then user should be redirected to correct registration forum under domain.

I agree that separated system will give you better control, safety and performance. But merging them in one searchable system... this may be quite hard.