[SOLVED] Grab + modify field value and fill another field with result

onAfterUserRegistration is fired after the user object has been stored to database. So yes your query field should be able to pull the value without a problem. It may not be working due to access restrictions. If the field is on a tab with Registered access for example you won't be able to get the fields value unless you're logged in, etc..

Have you an idea when it will be ready ?

No, I'm too busy working on CB 1.10.0 to work on next releases of incubator projects so I can't say when it'll be done, sorry.

I looked and my field is inside a public tab but simply in position "not_on_profile_1". The field itself is not restricted in any way but I still unable to pass his value in my Post..

Anymore suggestion ?

Alternatively instead to try to modify the date, is possible to simply store the date value in European format that mean DD-MM-YYYY instead YYYY-MM-DD ? I suppose this is not possible due to some database constraint ??

Don't know what more to advise. None of the format functions work outside of conditionals for now. This will be changing in next release, but I can not drop what I am doing to implement it as CB 1.10.0 is more important, sorry.

Anymore suggestion ?

Yes, edit your endpoint and have it do date( 'd-m-Y', strtotime( DATE_FROM_URL ) ). Then it'll work no matter what format you send the date in.

Yes, edit your endpoint and have it do date( 'd-m-Y', strtotime( DATE_FROM_URL ) ). Then it'll work no matter what format you send the date in.

I'm sorry I don't understand well what you mean.. As I said, when we use a CB Date field, the value seem to be always stored in format YYYY-MM-DD and this even if in CB Configuration the settings related to "Date format" is well DD-MM-YYYY.

So you mean is possible to change this ?

thank

I'm sorry I don't understand well what you mean..

You're sending the information via HTTP POST using a Request action as per your original topic. The location you are sending it should reformat the string to whatever it needs. It shouldn't be the other way around. So whatever script you're sending the date to use the formatting as provided in my previous reply to allow it to accept any date format. Best case is your system should be using MYSQL standard date formatting (Y-m-d H:i:s) anyway and it should formatted on output.

As I said, when we use a CB Date field, the value seem to be always stored in format YYYY-MM-DD and this even if in CB Configuration the settings related to "Date format" is well DD-MM-YYYY.

It will always store to the database like that, because that's MYSQL standard date format. It's the only format that it should ever be stored as in your database. It's reformatted for display.