• Hello Fabrik Community

    Fabrik is now in the hands of the development team that brought you Fabrik for Joomla 4. We have recently transitioned the Fabrik site over to a new server and are busy trying to clean it up. We have upgraded the site to Joomla 4 and are running the latest version of Fabrik 4. We have also upgraded the Xenforo forum software to the latest version. Many of the widgets you might have been used to on the forum are no longer operational, many abandoned by the developers. We hope to bring back some of the important ones as we have time.

    Exciting times to be sure.

    The Fabrik 4.0 Official release is now available. In addition, the Fabrik codebase is now available in a public repository. See the notices about these in the announcements section

    We wish to shout out a very big Thank You to all of you who have made donations. They have really helped. But we can always use more...wink..wink..

    Also a big Thank You to those of you who have been assisting others in the forum. This takes a very big burden off of us as we work on bugs, the website and the future of Fabrik.

timestamp element show time 6 hours before my time

vaguemind

Vaguemind
hello , i use timestamp element but it shows time in list view 6 hours before my time ? why ?
i set "GMT or Local Server Time" as GMT ?
 
Confirmed.
MySQL is doing timezone conversions on timestamp columns, I assume Fabrik is doing it additionally (on save?).

I can't see a difference between GMT and Local setting, it's always displaying UTC + 2x my timeszone offset and storing my local time.
 
Wait for a fix or use date_time element set to "Always return todays date".
 
I had this problem too a long time ago. What I remember doing to get this solved is to change the server time zone settings of Joomla. It is under Global Configuration > Server > Location settings
 
actually i changed in global configuration as u mentioned but it is the same , i think its a bug need to be fixed as troester said
 
Seems to work OK for me. I'm in CST, and it correctly does the TZ offset. I think it may also matter as to what time zone you have MySQL set to.

However, as per @troester's advice, I would use a date element, with "always return today's date". There are a number of issues with the timestamp data time in MySQL. For instance, even when set to "ON UPDATE CURRENT_TIMESTAMP" (the "update on edit" feature), it won't update unless one of the fields in the row being saved has actually changed. So you can edit and save a row, and the timestamp won't change if you didn't actually change anything.

We've really only kept the timestamp element around for backward compatibility for people who are already using it.

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

Thank you.

Members online

Back
Top