Forums / Developer / How to change the user registration process

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

How to change the user registration process

Previous topic

Developer

Next topic

Author	Message
Oliver Frommel	Tuesday 05 August 2008 11:28:07 am Hello, for a new site we need to establish a relatively complex registration process including: payment details, checking against a database and so on. How can we do this, where do we start? Thanks Oliver
Piotrek Karaś	Tuesday 05 August 2008 11:54:58 am Hi, If you want to have that in all in registration, then probably you will have to create some custom datatypes that would handle different checks, validations etc. I find the datatype one of the most flexible interfaces between eZ and "custom/outside world". For one of our projects where we have online payments, we separated user registration (it's a bit community site) and payment account registration. It is impossible then to take certain actions (again, with a use of almost-empty validation-purpose datatype) if you do not have valid payment account, which is not required for access, though. Please share if you can the final outcome of this project. Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Oliver Frommel

Tuesday 05 August 2008 11:28:07 am

Hello,

for a new site we need to establish a relatively complex registration process including:
payment details, checking against a database and so on. How can we do this, where do we start?

Thanks
Oliver

Piotrek Karaś

Tuesday 05 August 2008 11:54:58 am

Hi,

If you want to have that in all in registration, then probably you will have to create some custom datatypes that would handle different checks, validations etc. I find the datatype one of the most flexible interfaces between eZ and "custom/outside world".

For one of our projects where we have online payments, we separated user registration (it's a bit community site) and payment account registration. It is impossible then to take certain actions (again, with a use of almost-empty validation-purpose datatype) if you do not have valid payment account, which is not required for access, though.

Please share if you can the final outcome of this project.

Piotrek

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu