Date element acts differently in latest Githubs

juuser

Well-Known Member
Hello,

I have used date element to save the creation date/time for the record and it has worked fine until latest Githubs. I have attached screenshot of my settings.

Before this setup recorded the initial record creation date/time. Now it returns empty value :(
 

Attachments

  • date_time.jpg
    date_time.jpg
    44.3 KB · Views: 211
Hi Hugh,

Thanks, element is visible. Editable is "no-one" and Viewable is "public". When i set Editable also to public, it works ok.

With earlier Githubs it worked well with my previous settings. If it cannot be reverted back, I would have to change settings with all my approx 50 tables and the element would be editable which i don't want it to be :(
 
Friendly bump again...

We still have this problem that date-time elements are not saving in the database - it's very annoying, and I don't want to change access in order to make it work. I'm pretty sure it changed on a recent GitHub update.

Any ideas, please?
 
I had the same problem with Fabrik 3.1. Rob should have fixed it in today's GitHub release. Try to upgrade and test again.
 
Hmm. I've updated from GitHub, but the date/time still doesn't save in the database from a timestamp field. The post-submission email does have the correct date for the field.

John
 
but the date/time still doesn't save in the database from a timestamp field.
Are confusing your terminology, datetime and timestamps are not the same thing.
If you have a timestamp mysql field then you can't edit that with the date element, you should have a datetime mysql field type.
 
Many thanks, Rob. That may be the problem - I changed the element from datetime to timestamp when timestamp didn't work, but left the SQL at datetime. I'll take a look. If that's the only problem, I'll close the thread... but I'll first see if the datetime element works now!
 
No, this is not the problem. With earlier Githubs evertuthing worked fine. Now, when datetime element edit access is "nobody" it doesn't record the date :(
 
Hmmm, it's debatable what should happen if the edit access is nobody. Typically, if someone doesn't have edit access, then we don't save anything.

However, I do agree that if you have a date element which is set up to act as a time stamp, defaulting to the current date / time, then it should record that, even if the user doesn't have edit access.

I'll take a look at our code, and see what may have changed to stop that happening.

-- hugh
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top