webmaniacgr

lolol

@Pseudohuman you don't need to

ok thanks @Pseudohuman, it all makes sense now

@Pseudohuman who is kenorb?

@Pseudohuman where is that?

@Pseudohuman where do you live?

thanks for your time on that Shabir, I appreciate.

And that's not possible, it's too messy.

Also, the solution above is not going to work on all view modes and all templates, I would have to copy it across my whole codebase, wherever event nodes are rendered.

Yes, that's my problem :) Any thoughts on that?

But that I need to avoid

I'm working with very specific wordings in the template and the HTML has to be specific and following the date.theme's functions. So I would have to replicate everything according to that, e.g. <span class="date-display-start">Tuesday 03 May 2016 - 17:02</span>

well as I mention in my initial question, ...Programmatically altering the markup of the field would probably not be a preferred solution as any change of the format on the UI under display settings (e.g. from long to short etc) would be ignored....

Oh, and then print $new_formated_date in my template? That's what you mean?

I hope everything is more clear now...?

So when $content['field_event_date'] goes through render, what's important is the format of the date selected on UI display settings (e.g. "long"), not the value of the date.

Yes, I can change the values, ie value & value2 as I like and I can see the change in my dpm. But when the date is rendered (for example on a node page, the template generates the page with that: <?php print render($content['field_event_date']); ?>) and I get the same exact thing.

changes the value but not the way the date is rendered. My output is exactly the same as before, not sure if that's what you meant.

this:

In the meantime...

Sorry but this pseudo code can be confusing, especially after trying to solve that for the last few hours!

Given the screenshots I showed you, can you give me a real code example of what you mean?

Sure

I can do whatever I want with value & value2 but I don't know how to override the output on my node basically...

So as you can see, value & value2 are what's stored in the db, nothing to do with format.

and inside $vars['content'], that's what the field contains:

that's what I have in my field, dpm straight from preprocess_node

By the way, updating the module to latest version doesn't add anything to my dpm

I mean, within the node object, which value do you set as the format?

on the array you're dumping on my question page, to which value do you assign the date / date_format?

How do you actually apply that to the stored dates?

ok so you assign the desired format to $date_format.

what's with the $date_format = date() ?

ok so first you get the start and end dates set in the db, that's OK.

I need to keep the selected format (which is currently set to "long" on display settings for the default view mode) and just alter the output by presenting just the date, not the time.

in date.theme, the theme functions construct the output, e.g. for date range, for single date and so on. This is a different thing than changing the date format e.g. "long", "short" etc.

for some nodes (where a checkbox is checked), I need to present the field's output without the time, that's all.

I'm using 7.x-2.8, do you think 7.x - 2.9 provides all these attributes? I'll see if it does. In the meantime, value & value2 values never change, no matter the display settings as they correspond the values stored in the dabase (e.g. 2014-04-30 22:30:25). As a result, I'm not sure how I can alter these, which is the base of my problem.

I get the exact same thing within $node.

In my case, dpm ing $vars only returns value, value2, timezone, timezone_db and date_type. All these are stored in the field's array, under $vars->field_node_date[0]. Any ideas on how to access dateOnly?

I had no idea dateOnly can be used like that, so setting it to TRUE would just display the date part excluding the time, no matter the format selected under Display settings? I'll give that a try.

Thanks for your suggestion, the date formatting part is the tricky one because of the way the dates are stored within the node object. Can you add an example of how to display the format(s) above?