test
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • ithacaindy Friend
    #160094

    Has anyone stumbled upon the timezone bug introduced in Joomla 1.6? The problem (which is global to all operations, such as updates, article availability, etc.) happens when you set the system timezone to anything besides UTC. This is just one of the reasons I’ve labeled J!1.6 as still in the beta stage and not ready for production sites. I’ve reverted back to J!1.5 and Teline II.

    Ninja Lead Moderator
    #377137

    Could you be more specific on this issue?
    <blockquote>happens when you set the system timezone to anything besides UTC</blockquote>
    what is the problem exactly?

    ithacaindy Friend
    #377169

    <em>@hungnd 222065 wrote:</em><blockquote>Could you be more specific on this issue?

    what is the problem exactly?</blockquote>

    Sure. First, set the timezone in admin to anything besides UTC. Then, create an article. It will appear with a timestamp a few hours in the future and the article manager will show the post as published, but pending. View other time-specific areas, such as the time you logged in – it will also be off. The bug has already been added to the J!1.6 bugtracker.

    I plan to use J1.5 until July, when J1.6.1 should have been released, and hopefully this bug has been squashed.

    walterjr Friend
    #380107

    I’m with the same problem with timezone.
    anyone can help?

    huypl Friend
    #380206

    hello walterjr,
    This is a bug of Joomla 1.6. But you can try this way to fix this bug:
    Go to your template/blocks/header.php then add this code
    <?php
    date_default_timezone_set(‘America/Los_Angeles’);
    ?>
    Remember to change the parameter (‘America/Los_Angeles’) to your desired time zone, for example “Asia/Shanghai”. 🙂

    walterjr Friend
    #382770

    Thank’s huypl,
    for front end exibition work’s great, but at administrator, still displaying wrong timezone 🙁

    Phill Moderator
    #382774

    Have you updated to Joomla 1.6.1 as I believe this was fixed as part of that release.

Viewing 7 posts - 1 through 7 (of 7 total)

This topic contains 7 replies, has 5 voices, and was last updated by  Phill 13 years, 9 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum