You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in #beaver-themer
I tested with [pods name="homepage" field="current_event.date'"] and [pods field="date"] on a events single page. The second shortcode displays the correct format (12.07.2018), the first one (using the relationship from the settings page) displays the wrong format (2018-07-12).
Workaround:
I managed a work-around: [pods name="homepage" template="current-event-date"] with a template "current-event-date" of {@current_event.date, tv_formatdate} and a function "tv_formatdate" of:
function tv_formatdate($input_date) {
return date("d.m.Y", strtotime($input_date));
};
The text was updated successfully, but these errors were encountered:
quasel
added
Type: Enhancement
Enhancements to features that already exist, but are not major additions
and removed
Type: Enhancement
Enhancements to features that already exist, but are not major additions
labels
Aug 31, 2018
Reported in #beaver-themer
I tested with [pods name="homepage" field="current_event.date'"] and [pods field="date"] on a events single page. The second shortcode displays the correct format (12.07.2018), the first one (using the relationship from the settings page) displays the wrong format (2018-07-12).
Workaround:
I managed a work-around:
[pods name="homepage" template="current-event-date"]
with a template "current-event-date" of{@current_event.date, tv_formatdate}
and a function "tv_formatdate" of:The text was updated successfully, but these errors were encountered: