×
Kunena 5.1.18 Released (30 Jun 2020)

The Kunena team has announce the arrival of Kunena 5.1.18 [K 5.1.18] which is now available for download as a native Joomla extension for J! 3.9.x. This version addresses most of the issues that were discovered in K 5.1 and issues discovered during the development stages of K 5.1.

×

Please Read This First:


This category is only for discussing add-on software products for K 3.0 that were obtained on the download page . Topics about other products obtained from other sources will be deleted.

Other add-ons that were developed by the Kunena team - but no longer maintained - are available on an "as is" basis. People who use these products do so at their own risk.

This category is for the community to share their experiences and to develop their own solutions to problems that they may encounter. Please note that the adminstrators and team moderators are not obligated to reply to topics in this category.

Solved Notice: Kunena: Timezone issue! (Kunena Login module)

More
7 years 1 week ago - 7 years 1 week ago #1 by Ventilator
When a user is logged in, an error message appears at the Kunena Login module, under 'Last Visit'.

"Notice: Kunena: Timezone issue! in /<xxx edited for privacy xxx>/public_html/libraries/kunena/date.php on line 104

Warning: DateTime::setTimezone() expects parameter 1 to be DateTimeZone, string given in /<xxx edited for privacy xxx>/public_html/libraries/joomla/utilities/date.php on line 438"

Obviously, Kunena's having difficulty resolving the time of last visit, though it appears to get the date right...

...can anyone help?

Cheers

Ventilator


This message contains confidential information

Database collation check: The collation of your table fields are correct

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 60 seconds | Max execution memory: 128M | Max file upload: 100M

Kunena menu details:

Warning: Spoiler!

Joomla default template details : beez_20 | author: Angie Radtke | version: 2.5.0 | creationdate: Unknown

Kunena default template details : Blue Eagle (default) | author: Kunena Team | version: 1.7.2 | creationdate: 2012-01-31

Kunena version detailed: Kunena 3.0.0 | 2013-05-15 [ Wanga ]
| Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: Content - Kunena Discuss 3.0.0

Modules: Kunena Latest 3.0.0 | Kunena Login 2.0.4

Last edit: 7 years 1 week ago by Ventilator. Reason: omission of error message

Please Log in or Create an account to join the conversation.

More
7 years 1 week ago #2 by xillibit
Hello,

If you use Kunena login 3.0.0 it would be better :)

I don't provide support by PM, because this can be useful for someone else.

Please Log in or Create an account to join the conversation.

More
7 years 6 days ago #3 by Ventilator
That seems to have done the trick (should have noticed the mismatch between versions) - thanks!

Please Log in or Create an account to join the conversation.

More
6 years 11 months ago #4 by BamiGorengo
I Have the Same Problem with Kunena Login =( after Login:

Letzter Besuch
Notice: Kunena: Timezone issue! in /www/htdocs/w00f3b23/xbox360/libraries/kunena/date.php on line 107

Warning: DateTime::setTimezone() expects parameter 1 to be DateTimeZone, string given in /www/htdocs/w00f3b23/xbox360/libraries/joomla/utilities/date.php on line 438
Today


How can i fix this error?

Kunena and Kunena Login is last version... And Joomla is 2.5.14...

Sry for my bad english =(

Greetz from Germany

Please Log in or Create an account to join the conversation.

More
6 years 11 months ago #5 by sozzled
BamiGorengo: would it be possible for you to share your configuration report with this community so that we may have better knowledge of your site environment?
The following user(s) said Thank You: BamiGorengo

Please Log in or Create an account to join the conversation.

More
6 years 11 months ago - 6 years 11 months ago #6 by BamiGorengo
Ah okay sorry =) here it is:

This message contains confidential information

Database collation check: The collation of your table fields are correct

Joomla! SEF: Enabled | Joomla! SEF rewrite: Disabled | FTP layer: Disabled |

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 30 seconds | Max execution memory: 64M | Max file upload: 200M

Kunena menu details:

Warning: Spoiler!

Joomla default template details : HomebrewGenius - Xbox360 | author: Sven Budak | version: 1.0 | creationdate: Unknown

Kunena default template details : Blue Eagle 2.0 | author: Kunena Team | version: 3.0.1 | creationdate: 2013-06-29

Kunena version detailed: Kunena 3.0.1 | 2013-06-29 [ Noordwijkerhout ]
| Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: None

Modules: Kunena Login 3.0.1

Last edit: 6 years 11 months ago by BamiGorengo.

Please Log in or Create an account to join the conversation.

More
6 years 10 months ago #7 by BamiGorengo

Please Log in or Create an account to join the conversation.

More
6 years 10 months ago #8 by sozzled
Very strange. Theoretically, everything should work. I'm guessing that there's something about the data that the Joomla date library cannot handle.

Another possibility is that the last login field in the Joomla user profile has become corrupted in the database. Maybe resetting the last login date in the Joomla user profile to NULL and "synch user profiles" (forum tools in the Kunena dashboard) may overcome the problem. I don't know.

I've looked around this forum for answers; perhaps it's been answered but my memory on this is a little hazy. Perhaps your issue has been discussed on the Joomla forum ?

As a matter of interest, when did this problem start to happen? Is there something else we should know about (e.g. did you recently migrate from J! 1.5 -> J 2.5, for example)?
The following user(s) said Thank You: BamiGorengo

Please Log in or Create an account to join the conversation.

  • Not Allowed: to create new topic.
  • Not Allowed: to reply.
  • Not Allowed: to edit your message.
Time to create page: 0.238 seconds