It's in the ACP -> Configuration -> Users -> Registration. Set Force login (Visitors are required to log-in themselves to access the page.) to Yes.
EDIT: Oops, a little too slow 
Posts by TheSonic
-
-
I've never seen there being a public_shtml folder before, only a public_html
This is somerhinh you may configure in your webserver. You may configure your webserver how to handle http and https-connection. In his case, https seems to use a different DocumentRoot.
-
If you are using Apache as websever, create a .htaccess-file in the root of domain and add
Just change https://www.yoursite.com to what ever you want redirect.
NOTE: If your WSC is in the root, just add the line the .htaccess-file coming with your wsc.
-
-
Yes for creating/writting articles, no for comments.
-
Yes, there are
If you are interested in testing and not familar with github, SoftCreatR posted a package on his supportforum: https://support.softcreatr.com…2/?postID=29592#post29592
It's a "normal installation" - just check it out, if you want to.
-
They told May or June some time ago.... I have not seen any updates on this date yet.
I have installed the Alpha of the core build via GitHub... You may also do this, if you're interested in this (Only the Core (CMS), other Apps are not public on GitHub, so we have to wait for the Beta)
THere are still some issues, but i think we are getting closer
: https://github.com/WoltLab/WCF/milestone/6 -
This is something you have to configure on your server (or your host is doing this for you).
There are thousands of solutions and configurations
-
shtml and https are two different things.
Yes, but he is talking about directories, not about shtml-files.... The directory public_shtml is used for https-conections in his case... No matter, what files are in there (.php, .html, .shtml, and so on)
-
No, but clear your cache.
-
In your ACP, find the Profielfiedsmenu. You can set the position of the field by number for each profilefield in its options.
-
Geronimo You mentioned:
because of security reasons,
Experienced users will identify the software... a regular user don't cares about that.
The frontend doesn't matter, not even the styles (or the branding (removal) )... Just have a look at the (php)files on the server or check the site's source and you will identify the software....
-
… want to create an unique community without reference to WoltLab,
… want to hide the software used to create the community because of security reasons,
This is nonsense... It's no problem to identify the software used, if a user wants to... Doesn't matter if it's WSC, XenForo, IPS, vB, or what ever....Normal users may not know how to do this, but for experiecend users, it's definitly not a porblem.
-
I own licenses for all big, commercial forums/communities... Normally it"s always a languagevar, a templateedit or a fileedit. As long the code is read- and editable, it's not a big deal (i normally add a line under the (unmodified) copyright, so i checked that... I never bought brandingfree and never removed it).
The only secure way is to encode the phpfiles with ioncube or something like that (and even that could be "hacked")
-
I thought that I had done with this.
I have created a usergroup for 'bloggers' and am setting the permissions.
Where I have the options to set the permissions for things like Moderator or Admin access, is it restricted to this group, or whichever group I am working on at the time. Or do these permissions relate to access to the boardwide Moderator and Admin ?
it's in the same panel, but not in the tab genral permissions. There are extra tabs for moderative and administrative options for each usetgroup.
-
You have to set this for all groups you don't want to post articles or comments.
If they signup, they should be in Users, if they are Guests (not registered / logged-in), they are in the Group Guests.
You may want to create a new group called "Bloggers" or "Trusted Mebers" or what ever you like and give them the rights after you trust them, or
untill I feel safe with them.
-
Just set the right options in the desired Usergroups (registered, unregistered, etc)
ACP -> Users -> Usergroups -> <"unrusted" Usergroup> -> General Permissions -> Blog ->
Can create blog articles: No
Or:
Can create blog articles: Yes AND Can create blog articles without approval: No (So they are able create articles, but you have to approve them)
Maximum Blogs: 0 (They can not create own Blogs)
For comments:
Can create comments: No
Or:
Can create comments: Yes AND Can create comments without approval: No (So they are able create comments, but you have to approve them)
-
iIf you just only block a few addresses, it is fine. If you want to block big ranges, you should prefer another way not to stress your webserver and its performance
-
-
Have a look here: Migrating to WoltLab Suite 3
