3

ExpressionEngine gives edit_date special treatment inside the Channel Entries loop to account for the way it's saved, but inside a query it's just another 14-digit number. To get it to format properly in a query loop, the SELECT statement can be modified to offset the value from GMT and convert it to a Unix timestamp. Luckily, EE's current_time variable ...


3

Relative Dates have been introduced to (native) Expression Engine in Version 2.8. Have you checked if your Site is running on EE 2.8 or newer?


2

EECMS just saves the IP of who edited an entry, not his or her member_id. You can try the Audit add-ons: Audit Pro, which lets you archive logged data, set custom email notifications and search log entries; Audit Tags, which lets you output Audit’s logged data in your templates. The add-on can be found on github as well.


2

I believe, your options are: to change the format of date you're using on the segment_2, which isn't a good idea because EllisLab can some day finally normalize all date fields; to reformat the date to match the way its used on edit_date database column; To change the date format, I suggest you the Low Nice Date plugin: {exp:low_nice_date date="{segment_2}...


2

I have spoken with Vector media about this issue and it has been determined to be a bug that resulted due to changes in the date functions from EE2 to EE3. This issue should be addressed in future releases of Cartthrob. The actual cause of the difference in dates is below: /cartthrob/models/cartthrob_entries_model.php has a public function (starting LINE ...


2

There isn't any tag available for entry revision. You can do it with following code example: {exp:channel:entries channel="CHANNEL NAME" ...........} <li>Created: {entry_date format="%m/%d/%Y"}</li> <li>Author: {author}</li> {exp:query sql="SELECT exp_members.screen_name AS revision_author, exp_entry_versioning....


1

This is because date formatting is not supported inside a Safecracker form. See also http://devot-ee.com/add-ons/support/zoo-visitor/viewthread/7449#25153 Cheers, Nico


1

After working with EllisLab support on this issue, it turned out to be a rogue config item in the database for "server_offset" config item. It was set to -1140 for some reason. They were kind enough to decode, unserialize, modify, re-serialize, and re-encode the variable for us and that fixed the problem. Here's the response regarding the resolution from ...


Only top voted, non community-wiki answers of a minimum length are eligible