I have 18,000 users which I tried to import into Gallery 2 through Drupal. It gets to about 1600 then quits. Users don't need to be synchonized with the gallery except for admin. Every once in a while I'll get a user who is cruising around the Drupal side and Drupal will through hundreds of errors in the watchdog. I don't know if it's effecting the experience of the viewer and I can't recreate the problem.

I would just as soon make sure the only user synced with the gallery is user 1 and that everyone else views it as an anonymous user. Is that possible.

The only reason I'm using the gallery is because it's so easy for the manager to just dump a file folder into the gallery. And it's already themed. 

Type	gallery
Date	Sunday, December 6, 2009 - 8:20pm
User	#########
Location	http://thetriton.com/ed-classified/tid/429
Referrer	http://thetriton.com/ed-classified/tid/457
Message	Unable to initialize embedded Gallery. You need to configure your embedded Gallery.
Severity	error
Hostname	##.##.###.##
Operations
CommentFileSizeAuthor
#2 triton-error.jpg343.74 KBAdam S

Comments

lvthunder’s picture

lvthunder commented

I don't think there is a way to just sync user #1 and not the rest. I think the user sync is failing because it is either taking too long or running over the php memory amount. Have you tried to do the sync again. Maybe it would get farther every time you do it until it gets everyone.

Adam S’s picture

Adam S commented
StatusFileSize
new triton-error.jpg343.74 KB

I went into phpmyadmin and emptied the user table and the user group table but first export the first two entrees which I then imported. I ran the user import again and it worked fine and I stopped getting errors.

My max memory for php is 128M which might not be enough. If I get this problem again I will try to bump it up to 256M.

I'm including an image of how it looks on the screen.

lvthunder’s picture

lvthunder commented

Generally a blank screen means PHP ran out of memory. How many users do you have?

Maravizzo’s picture

Maravizzo commented

Hi Adam,
I think I've just found the bug that creates your problem, I reported it here:
http://drupal.org/node/877602

Bye