Hey Le Freak,

May i know do you using mini registration or full registration?

By the way, I have tried to access in your Easysocial setting from backend, but I hitting this :

Error

You are not authorised to view this resource.

Can you assign this user account have Superadmin privileges so I can take a look of your settings?

Oops, did so now. Also had to change the pass, please check the new one here.

I am using the mini registration only.

Hey Le Freak,

I am sorry that delay of this reply,

I noticed I can't fill in the address data in the quick registration module.

I suspect you have do some custom css code in your current template, If I temporary remove this following css code, it would be fine.

body div#fd.es.mod-es-register.w600 .quick-register .form-control[data-field-address-city=''] {

	width: 60% !important;

  float: left !important;

}



body div#fd.es.mod-es-register.w600 .quick-register .form-control[data-field-address-zip=''] {

	width: 40% !important;

  float: right !important;

  margin-top: 0 !important;

}

By the way, may i know do you have done any customization for Easysocial? If no, can I have the permission to update to latest version again?

Oh, those css modifications were made by your support team, you can see it here: http://stackideas.com/forums/quick-registration-module-city-and-zip-one-below-the-other-instead-of-side-by-side

I have no idea what happened to the address field. Yesterday they were working fine. Now I can see that there are no more addresses saved, because GeoCommunity map shows no more profiles on the map. Dough!

This here was an additional modification made by your support team:
http://stackideas.com/forums/mini-registration-%C3%A4-%C3%BC-%C3%B6-using-makes-registration-impossible-and-give-error

If it is the only way to reinstall, there is no choice, so please go on.

Hey there,

Hm, yeah looks like I was missing another block of css code in my reply earlier. Where did you place the custom css codes? I need to add this,

.quick-register-form .register-field {

  clear:both;

}

Okay, this seem like a chicken and egg situation. The fix that I have applied for you with the utf-8 on the city seems to caused another issue on the "birthdate". I have temporarily reverted the fix on the utf-8 characters and we will release a fix for this in the next release.

Ooh, does not sound funny at all. Hm, okay, I got no problem when a fix will come. But I need to say that I have no idea what it means when you say for the 'next release'. Can you give me a hint and tell me roundabout how long this takes?

Sure I will not be done with my site within the next few days but if you tell me it takes more than a month I might get into some trouble due to my own deadline. I can not publish the site as long as there are no umlauts possible.
I am not a member for a long time yet so I got no idea how often there are these kind of updates. There is no intention to make pressure but only curious about what exactly 'next release' means.

I know that you can not provide an exact date but just a roundabout estimate.

Hey there,

Just an update, we have already added a fix for this internally. Do you need this urgently? I could patch this now for you but I would suggest that you wait for 1.3.30 as we are probably going to release the maintenance release sometime mid of this week

Thank you very much for your effort and offer to make this quick, but at the moment there is no need to make any quick actions. I have seen the update it available, many thanks for making it.

Hi there,

You are most welcome. Glad that your issue has been resolved now.