Solved l, d F Y H:i instead of date/time

I am using Joomla 2.5.6, JomSocial 2.6.2 and Kunena 2.0.
When I go to the "latest posts" on a JomSocial profile, I'm getting l, d F Y H:i instead of the date and time.
I've checked the settings in JomSocial, Kunena and Joomla and all show the correct date and time settings.
I saw another post on the Kunena forums regarding this, but there was no help that I saw.
Any help would be greatly appreciated.

thanks in advance,
Flip

Looks like the option needs to have different value on Joomla! 1.5 vs 2.5.

I think it's in your language files: DATE_FORMAT_LC2 -- but you were using English?!?

I am also facing the same issue, please see the problem coming on my profile page (on Jomsocial) please refer to this link: www.ottosen.com/chat/steen/profile
Any help would be highly apprciated.
Thanks!

Reported this as a bug..
github.com/Kunena/Kunena-Addons/issues/66

thanks for the report, Matias. Sorry to have taken so long to reply, but we've had things going on here at the house that didn't allow our attention to "stray" to the website for a bit.
I just did a complete fresh install of the latest Kunena - 2.0.1, JomSocial 2.6.1 and Joomla 2.5.6 - and still have the same problem.
Has there been any news on this bug??
I'm going to look at the bug tracker too, but wanted to catch up here first.

thanks,
Flip & Mickey

I've managed to track down how to fix this issue if anyone is interested.

You need to find the Plug-In file mykunena.php, which should be located in /public_html/plugins/community/mykunena in your Joomla Install

You will need to find the following line of code, around line 90

change it to

Note, the piece of code changed is $postDate->toFormat to just $postDate->Format

It seems the toFormat parameter is now depreciated in Joomla 2.5, and making the above change has worked on my website (take a look at www.u-read.net/waveyuk/ and you will see my forum posts are now displaying the date correctly).

Hope this helps anyone still struggling with this.

Cheers
Dave

Thanks waveyuk, exactly what I needed.

This bug is not fix in 2.0.2 version.

I can also validate that this bug is NOT fixed in the latest release. However the fix posted here does in fact work. Can we please have a developer clarify that the fix is in fact correct and update as necessary? To allow non-support people to produce fixes yet have no response what so ever from the Kunena Team is rather classless and in a sense disrespectful. This is not a rant towards the Kunena developers, merely a suggestion to display an effort to validate fixes produced by non-kunena staff - but also show some appreciation for those solving issues for you!

EXCELLENT Job waveyuk!!! Your contribution to Kunena, whether correct or not is an absolute welcome. It is highly appreciated that you have taken the time to reflect the corrections that worked for you, for everyone else to use!


Thank you,
Voice4Vision

On the contrary, this is the community self help category of the Kunena website, and does not require developer input. As the Kunena project is on GitHub, at github.com/Kunena/ it is possible for anyone registered there to make a branch and post the fix there, and it is more likely to then be addressed in a future update, and helps the developers work on higher priority issues.

Regarding the fix, it does work perfectly as I have also modified my website using this code, so a big thank you to waveyuk!

EDIT: github.com/Kunena/Kunena-Addons/issues/66 It is already in the GitHub, so it should get fixed soon.