create ezpublish users from a script

Next topic

Author	Message
Ruben Torres	Tuesday 06 April 2004 11:36:16 pm Hello, I'm migrating a users database to ezpublish and I want to use a script to create all my users in ezpublish without having to do this one by one. What tables do I have to use? Does someone has a functional script like this and wants to share it with me? I would really appreciate this because Im in a hurry. Using ezp 3.3-3 and postgresql 7.3.4-4 over Fedora.
Marco Zinn	Thursday 15 April 2004 2:30:04 pm I suggest, that you have a look at the "contribution" section. There are scripts for migration ez2-DBs to ez3. This includes user groups and users, which are read (via SQL) from an ez2-table or two and creates users in ez3 by calling the ezPublish API for this. This worked well for me and should be easy to adapt for another SQL DB, when you know and understand that structure. Note, that you will need to make up your mind about permissions and roles, as this script does not take care of this, as the concept was changed completly between ez2 and ez3. How many users do you need to migrate? The import scripts are not very fast! (PS: Maybe it's an option to create an ez2-like table structure from your data, so you could just "run" that existing script). Marco http://www.hyperroad-design.com

Author

Message

Tuesday 06 April 2004 11:36:16 pm

Hello,

I'm migrating a users database to ezpublish and I want to use a script to create
all my users in ezpublish without having to do this one by one. What tables do I
have to use? Does someone has a functional script like this and wants
to share it with me? I would really appreciate this because Im in a hurry.

Using ezp 3.3-3 and postgresql 7.3.4-4 over Fedora.

Marco Zinn

Thursday 15 April 2004 2:30:04 pm

I suggest, that you have a look at the "contribution" section. There are scripts for migration ez2-DBs to ez3.
This includes user groups and users, which are read (via SQL) from an ez2-table or two and creates users in ez3 by calling the ezPublish API for this. This worked well for me and should be easy to adapt for another SQL DB, when you know and understand that structure.
Note, that you will need to make up your mind about permissions and roles, as this script does not take care of this, as the concept was changed completly between ez2 and ez3.
How many users do you need to migrate?
The import scripts are not very fast!

(PS: Maybe it's an option to create an ez2-like table structure from your data, so you could just "run" that existing script).

Marco
http://www.hyperroad-design.com

eZ debug

Timing:	Jan 18 2025 22:11:16
Script start
Timing:	Jan 18 2025 22:11:16
Module start 'layout'
Timing:	Jan 18 2025 22:11:16
Module start 'content'
Timing:	Jan 18 2025 22:11:16
Module end 'content'
Timing:	Jan 18 2025 22:11:16
Script end

Main resources:

Total runtime	0.0221 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0071	589.3594	152.6250
Module start 'layout'	0.0071	0.0049	741.9844	39.4609
Module start 'content'	0.0120	0.0082	781.4453	89.3047
Module end 'content'	0.0202	0.0019	870.7500	30.3047
Script end	0.0221		901.0547

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	10.7178	14	0.0002
Check MTime	0.0011	4.8886	14	0.0001
Mysql Total
Database connection	0.0008	3.6926	1	0.0008
Mysqli_queries	0.0054	24.4688	3	0.0018
Looping result	0.0000	0.1271	1	0.0000
Template Total	0.0015	6.7	1	0.0015
Template load	0.0008	3.6021	1	0.0008
Template processing	0.0007	3.0903	1	0.0007
Override
Cache load	0.0005	2.3371	1	0.0005
General
dbfile	0.0025	11.2684	8	0.0003
String conversion	0.0000	0.0356	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs