Hi Tullio!

My suggestion:
Export your users to one or more XML files, then import the XML files into 
magnolia.

Note: IIRC, the normal Users views do not have the XML Import/Export items in 
their menus, so to access this function, create a JCR Browser for the users 
workspace, then you'll be able to export them.

To get the format of the XML right it's probably a good idea to export an 
existing user, and go from there.

Regards from Vienna,
Richard

PS: We've found that XML is usually a fairly low effort way to get data loaded 
into magnolia. Most systems these days have some kind of XML export - add a 
little XSLT to get the data into shape, and it's ready for import...



(iPhone)

On 20.01.2011, at 16:07, "Tullio Bettinazzi" <[email protected]> wrote:

> 
> 
> I need to import, into magnolia, users coming from an older DB based CMS
> application.
> I need to import more or less 10000 users.
> I tried creating a blossom paragraph which creates users reading from DB
> data.
> It seems to work but is ver sloow (too slow) : it took 4 hr. for  2000 users
> and then :
> . memory went to high
> . system went to  slow for other users
> . browser timed out.
> Now I'm in test but in a few days we'll go production and the import of
> existing user could be a big problem.
> Is there any way to do that in a faster or, at least, less heavy way?
> Tks
> Tullio
> 
> -- 
> View this message in context: 
> http://old.nabble.com/Massive-user-import-tp30719688p30719688.html
> Sent from the Magnolia - User mailing list archive at Nabble.com.
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
> 
> 



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to