Login page - How do I disable "Sign Up" function (and remove the button from login page)?

Author Message

Christopher Thorjussen

Monday 05 January 2004 2:04:38 am

I'm trying to make a customer webpage with eZp 3.3-1 and the first page they shall see is the login page. For this to happened I've added this to site.ini.append:

[SiteAccessSettings]
RequireUserLogin=true

Now I (my customers realy) have to log in to see the Index page and other stuff.

BUT - the login page also shows the "Sign Up" button, and this leads to "Register User" page. I only want users added by the admin in the eZp admin page.

How do I disable the "sign up" button and function? Should/Could I make my own login page (template override?)?

Also strange: I tried the Sign Up button just to test, and after entering my details and clicking the register button I got this error:

Fatal error: eZ publish did not finish it's request

The execution of eZ publish was abruptly ended, the debug output is present below.

eZ debug gave this (relevant) info:

Warning: PHP
Undefined index: EditLanguage in /home/httpd/vhosts/kunde.domain.no/www-443/kernel/content/attribute_edit.php on line 60

Warning: PHP
Undefined variable: userID in /home/httpd/vhosts/kunde.domain.no/www-443/kernel/classes/datatypes/ezuser/ezuser.php on line 183

Warning: eZModuleOperationInfo::execute
Missing main operation memento for key: 382b5aa3ea629647b89672d065ec89f1

laurent le cadet

Monday 05 January 2004 8:57:18 am

Hi,

Maybe you can use the same page (login.tpl) and just remove the button from the template.
Make it as a comment {*....*} if you want to re-use it easilly later.

Hope this help.

Laurent

Christopher Thorjussen

Tuesday 06 January 2004 3:52:19 am

I guess this will remove the button, but wouldn't the function still be available? What about my error?

Balazs Halasy

Tuesday 06 January 2004 4:05:09 am

The function will still be available, yes. In other words: people could still reach it by doing a "/user/register" in the URL. This is because policy checking is omitted for the register function within the user module (.../user/register). However, policy checking can be turned on again by commenting out the following line in "site.ini":

PolicyOmitList[]=user/register

Regarding the error message: seems weird. I just tested this with a fresh 3.3-1 installation and it works here.

Balazs

Shurbann Martes

Tuesday 06 January 2004 4:08:50 pm

Hi Balazs,

Could you please explain more about the User Registration function, because I dont understand it.

If I comment out user/register:

# PolicyOmitList[]=user/register

Then I could turn off the register function? But how?

-Shurbann

Christopher Thorjussen

Wednesday 07 January 2004 8:59:52 am

I should have thought of that Balazs, silly me. Thanks for pointing that out. One question though, will it be available for a user that is logged in? (I'm not at my desk so I can't check it myself..)

Shurbann, if you comment out as Balazs said, you will not be able to open that page when you are not logged in. The rule said that all access to /user/register shouldn't be checked against the rules, so it's a kind of "allow everybody" setting..

Paul Borgermans

Wednesday 07 January 2004 9:13:09 am

See also

http://ez.no/developer/ez_publish_3/forum/developer/disable_register_user_in_login/re_disable_register_user_in_login_its_in_the_ini_files

You can disable entire modules or a specific function in a module.

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Guttorm Flatabø

Thursday 17 June 2004 1:01:40 pm

The above link is broken but this one is not:

http://ez.no/community/forum/developer/disable_register_user_in_login/re_disable_register_user_in_login_its_in_the_ini_files

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 19 2025 01:03:12
Script start
Timing: Jan 19 2025 01:03:12
Module start 'layout'
Timing: Jan 19 2025 01:03:12
Module start 'content'
Timing: Jan 19 2025 01:03:12
Module end 'content'
Timing: Jan 19 2025 01:03:12
Script end

Main resources:

Total runtime0.0173 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0077 589.6484152.6875
Module start 'layout' 0.00770.0031 742.335939.5547
Module start 'content' 0.01080.0045 781.890697.4609
Module end 'content' 0.01530.0020 879.351638.3047
Script end 0.0173  917.6563 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002715.8463140.0002
Check MTime0.00126.8001140.0001
Mysql Total
Database connection0.002413.925710.0024
Mysqli_queries0.002614.933530.0009
Looping result0.00000.092410.0000
Template Total0.00169.310.0016
Template load0.00084.811910.0008
Template processing0.00084.417610.0008
Override
Cache load0.00053.173910.0005
General
dbfile0.00021.428480.0000
String conversion0.00000.044140.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs