The purpose of shop account handlers

Author Message

Eirik Alfstad Johansen

Wednesday 21 January 2004 2:26:11 am

Hi,

I'm having some trouble grasping the concept of shop account handlers and how to use them. AFAIK, shop account handlers are designed to make it easier and extensible to decide which data fields are stored (and fetched for orderview) in conjunction with the order head.

However, if this is the case, why does shop/register have the account_identifier and the form field names for the validation procedure hardcoded? Shouldn't the account identifier be fetched from the INI settings, and the validation be done in the shop account handler?

Thanks in advance !

Sincerely,

Eirik Johansen

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Eirik Alfstad Johansen

Monday 02 February 2004 7:27:29 am

Hi guys,

I refuse to belive that editing shop/register.php is the only way to alter which fields that are stored in conjunction with an order header (data_text_1).

Is this really the case? There's surely must be others who have worked their way around this, without modifying the kernel.

Sincerely,

Eirik Johansen

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Petter Arneson

Wednesday 30 August 2006 7:12:47 am

How did you eventually do this?

What is the structure of a shophandler extension?

I have tried something like:

 extensions\myshophandler
   --> shopaccounthandlers
       --> shopaccounthandlers\myshophandlershopaccounthandler.php
       --> shopaccounthandlers\userregister.php
   --> settings
       --> shopaccount.ini.append.php
       --> site.ini.append.php
   --> design
      --> standard\templates\shop\userregister.tpl
 

Where shopaccount.ini.append.php contains:

#?ini charset="iso-8859-1"?

[HandlerSettings]
Repositories[]=kernel/classes
ExtensionRepositories[]=myshophandler

[AccountSettings]
Handler=ezuser

Alias[]
Alias[ezuser]=myshophandler

I got the shophandler to run, but I cant seem to connect to my userregister.php. Do I have to make a module folder for this?

I would really appretiate help, so I could avoid making changes in the kernel.

www.vzt.no

Petter Arneson

Wednesday 30 August 2006 2:57:48 pm

Ah, ok.

A module folder did the trick ;)

www.vzt.no

Mathias VITALIS

Sunday 03 September 2006 4:43:30 pm

Hi,
Could you explain what you did to change the userregister.php ?
I try to create new true user account when an anonymous user buy into the shop, and I think this is the way.
Thanks in advance !

Mathias VITALIS
- www.SilverHand.fr -

Andreas Adelsberger

Monday 28 April 2008 8:00:08 am

Hi, could you please explain how you got your custom userregister.php working?

Can I override the kernel classes using the new autoload mechanism?

Thanx Andi

---------------------------------------
Styleflasher New Media OG
Websites. Games/Multimedia.

Petter Arneson

Tuesday 14 October 2008 6:05:00 am

The structure you need would be something like this:

extensions\myshophandler

  --> design
     --> standard\override\templates\shop\userregister.tpl
     --> standard\override\templates\shop\accounthandlers\html\ez.tpl

  --> modules
     --> myshophandler\module.php
     --> myshophandler\userregister.php

  --> shopaccounthandlers
      --> shopaccounthandlers\myshophandlershopaccounthandler.php

  --> settings
      --> design.ini.append.php
      --> module.ini.append.php
      --> shopaccount.ini.append.php
      --> site.ini.append.php

Module.php should look like this:


$Module = array( 'name' => 'myshophandler', "variable_params" => true );

$ViewList = array();

$ViewList["userregister"] = array(
    "functions" => array( 'buy' ),
    "script" => "userregister.php",
    'ui_context' => 'edit',
    "default_navigation_part" => 'ezshopnavigationpart',
    'single_post_actions' => array( 'StoreButton' => 'Store',
                                    'CancelButton' => 'Cancel'
                                    )
    );

www.vzt.no

Andrei Popa

Tuesday 14 October 2008 6:23:06 am

Thank you very much. Great person.

What do I do?! What do I do?!?

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