Registration process running twice?

Next topic

Author	Message
Gabriel Finkelstein	Friday 09 April 2010 12:35:26 pm I'm having problems solving this since it has happened only a couple of times and I cannot reproduce it, and it's driving me crazy. I don't know what causes it, but the consequences are the following: When a user registers, a single object is created but: - it has 2 main nodes - it's name is "," (the pattern is "<last_name>,<first_name>" ) - the registrationinfo mail is sent twice (the second time having all object attributes empty, except for an ezidentifier attribute). - the contentobjectedithandler is triggered twice (the second time also object attributes are empty when fetching the data map) - the content-publish-after event is triggered twice. About 600 users have registered without problems, and around 7 had this problem. I have no errors nor warnings in my logs (except "There are more then one main_node for objectID" ). I'm running ez 4.1.3 on Debian, with PHP 4.2.6 and MySql 5, with the following extensions: birthday, regexpline and place_users. Does anyone have any idea about what might be causing this?
Bruce Morrison	Friday 09 April 2010 7:52:41 pm Hi Gabriel Is is possible the user is refreshing the page before it completes? Cheers Bruce My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
Gabriel Finkelstein	Monday 12 April 2010 10:47:54 am It is possible, but I tried to do the same or even submit the form twice, and I can't replicate the problem. Still, I suppose eZ Publish is prepared for those situations.
Lars Eirik R	Tuesday 14 December 2010 12:31:13 am Did you resolve this problem of yours Gabriel? We are currently having some of the same issues on a project of ours. It does not happen to all users, but somehow the same thing happens here. Our submission is triggered by a javascript but that should not matter?. Any ideas guys on why this happens (apart from the case that someone clicks the refresh button.)