As previously announced via banners and our newsletters, support is no longer available through this platform.

For easier navigation, you can still click on "Submit a Ticket" here, choose the appropriate category, and you'll be redirected to the correct support channel for your plugin.

You can still access your previous tickets and browse public tickets, but please note that responding to tickets is no longer possible.

Paid customers: Please log in to your store account for support.

Pre-purchase questions: Use the support widget in the bottom-right corner of our websites:
https://wpamelia.com
https://wpdatatables.com
https://wpreportbuilder.com

Okay
  Public Ticket #2696330
calendar mis-timed
Closed

Comments

  •  1
    Dan Wahpepah started the conversation
    February 19, 2021 at 9:22am

    I have my settings at 10 to 17. When i open my oage the calendar says 1 am to 9 am. How to reconfigure?

  • [deleted] replied
    February 19, 2021 at 11:58am

    Hello Dan,

    thank you for reaching out.

    There are several things that you can check, which could be the cause of this:

    1. Your Calendar's time 
    2.  WordPress's time zone
    3. Amelia's time zone
    4. Global working hours, found in Amelia settings are predefined as 09:00 – 17:00. If you created an employee before those hours are changed, employee still has those hours saved, and this as well could cause a conflict. Therefore, you will need to edit your employee’s profile, and configure his working hours in his profile.

      Please kindly let me know if the setup worked.
  •  1
    Dan Wahpepah replied
    February 22, 2021 at 12:32am

    Hi Ivana. I'm a noob.

    1. My calendar shows no problems.

    2. I'll have to check with WP about their timezone.

    3. Where do I find Amelia's calendar? I've done exhausting investigations and can't find it.

    4. Employees hours are 9:00 to 17:00. Employee was created only a couple weeks ago.


    Thanks for helping

    Dan

  •  1
    Dan Wahpepah replied
    February 22, 2021 at 12:55am

    It was in the WP timezone. Fixed. Thanks so much.


    Dan

  • [deleted] replied
    February 23, 2021 at 8:32am

    Hi Dan,

    Thank you for letting me know; I'm glad it's resolved now.

    If you have any questions in the future, please feel free to reach back out via new ticket.