Working with native EE forms like member login and member registration forms from extensions

Are you wanting to insert a hidden field? If so, there’s the form_declaration_modify_data hook. Just append to the hidden_fields key in the $data array and return it.

Kevin,

Thanks, but I am wanting to create a field named and styled per the extensions settings. Default is not hidden and simply absolutely positioned off screen in an attempt to deter bot logic.

The field is not seen and does not affect the user at all. When validating against it, I am just checking against either an empty value or one of the settings in the extension settings.

Is there not a way to hook into the member login like there is for channel_form or comment_form?

Also, I am looking at the Channel_form_lib.php file now, specifically @:1344. The only thing I have been able to obtain from hooking here is a huge object that doesn’t contain any $_POST data from the channel_form. Is this due to the conversion happening @:1514?

Or am I not calling it correctly?

public $hooks           = array(
  'channel_form_entry_form_tagdata_start'   => 'add_channel_form',
  'channel_form_submit_entry_start'        => 'check_channel_form'
 );

Then in my check_channel_form: (Just testing output now)

function check_channel_form($channel_form_obj)
 {
  echo "<pre>";
  print_r($channel_form_obj);
  echo "</pre>”;
  exit;
        }

When I go look at the rendered form prior to submission, I know the first half is working properly on channel_forms because the input is there…

<input type="text" class="my_field" name="my_field" id="my_field" tabindex="-1" >

In my check_channel_form I was able to get all of the data with the global $_POST var. I was making it harder on myself than I needed for channel_forms.

function check_channel_form($channel_form_obj)
        {
              echo "<pre>";
              print_r($_POST);
              echo "</pre>”;
              exit;
        }

This still doesn’t help with the others though. 😉

Is there not a way to hook into the member login like there is for channel_form or comment_form?

No, not in this way.

The only thing I have been able to obtain from hooking here is a huge object that doesn’t contain any $_POST data from the channel_form. Is this due to the conversion happening @:1514?

Shouldn’t be due to that, it looks like that’s a convenience to developers who are accessing things via POST to provide some consistency for fieldtype naming conventions. The Channel Form library object we send you in the hooks isn’t intended to contain POST data as it is available in the global $_POST variable. Is there a reason you cannot access your data through that?

Sorry, I edited the above instead of adding another comment. Yes, I already realized the second part. Thanks.

So essentially, I am left with either:

a) using the form_declaration_modify_data hook and appending the field I am using as a hidden field

or

b) recreating the wheel (which I am not going to do) 😉

One of those two is my option availability for member_login.

Am I left with abandoning the option for registration forms?

So essentially, I am left with either:

Yes, presently.

Am I left with abandoning the option for registration forms?

I would think the registration form would have the same options assuming the {exp:member:registration_form} tag is used.

What exactly are you trying to accomplish with an off-screen text field? We may be able to add some extra hooks but would like to understand the problem you’re trying to solve first.

No need for that. Thanks Kevin. I just want to make sure I cover as many bases as possible.

Kevin,

One thing though. I have noticed this morning that I am unable to catch the $_POST data from the

{exp:member:login_form}

using the ‘member_member_login_start’ hook. Is there a way to capture the $_POST data from this that I am missing?

😉

So if you var_dump($_POST);exit; or something similar, the variable is empty?

😉

Correct…

This:

public $hooks           = array(
  'member_manager'      => 'add_member_login',
  'member_member_login_start'    => 'check_member_login',
        ....


        /**
  * Member Login Validation
  *
  * Validate the Hon:EE Bee field on a member login form
  *
  * @return void
  */
 function check_member_login()
 {
  var_dump($_POST);
  exit;
        }

Just submits the form…

Sounds like the hook isn’t being fired at all if exit isn’t stopping the execution. I’d make sure you have the hook correctly registered in the extensions table. If that all looks correct, show me the template code you’re using to generate the login form.

See image…

I used the demo code from the docs…

                                    [code]<h1>MEMBER LOGIN FORM</h1>
                                    {exp:member:login_form return="site/index"}
                                        <p>
                                            <label>Username</label><br>
                                            <input type="text" name="username" value="" maxlength="32" size="25">
                                        </p>
                                        <p>
                                            <label>Password</label><br>
                                            <input type="password" name="password" value="" maxlength="32" size="25">
                                        </p>
                                        {if auto_login}
                                            <p><input type="checkbox" name="auto_login" value="1"> Auto-login on future visits</p>
                                        {/if}

                                        <p><input type="checkbox" name="anon" value="1" checked="checked"> Show my name in the online users list</p>
                                        <p><input type="submit" name="submit" value="Submit"></p>
                                        <p><a href="{path='member/forgot_password'}">Forgot your password?</a></p>
                                    {/exp:member:login_form}[/code]

I’ve just used the exact same template code and make an extension to call the exact same method and it’s properly dumping POST and halting execution, so I cannot reproduce this issue. Are there any other hooks in your install using member_member_login_start?

This is it right here.