krileon wrote:

Then using CBSubs SQL Actions isn't the best approach as everytime they resubscribe/renew it will re-execute that query.

Ok, so it seems to better to drop the CBSubs SQL Action plugin because user will do renewal in next year.

There's only 1 registration, but yes you can configure it to execute a query/queries after registration.

so it seems to be the incubator project that can be the solution here. I want to execute the query for all users but only when registration finish.

I just thought of something else, could it be possible to use CBSubs SQL action and in the query check if the username is a number? if it is, the query exits. If it isn't, then the query will change the username. In this way it would not make any different if the query executes every time a user do renewal.
Sorry for all the question, I'm not that good in SQL. and thanks for all your help.

krileon wrote:

It's possible the query is happening and CB is storing AFTER the query causing the first + last to override the new username.

I can't get it to work properly and above seems to be the thing that is happening.
I have done some further testing and everything seems to work if I not using the #__user table to save the data.

I found another thread on the forum regarding the problem:
www.joomlapolis.com/component/option,com_joomlaboard/Itemid,38%3E/func,view/catid,89/id,112663/#112663

Do you know if there has been any progress on the bug #1295?

Post edited by: Ducatiklubben, at: 2010/11/06 16:47

All test I have done has been registrations of new members via frontend. BUT I have activated the user in the backend. I guess that this could be the problem?

We will have users that will do offline payments and need to be activated via backend so this might be a showstopper right now for me.

How far away is 1.2?