Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    Calendar all day events start 02:00 end 02:00

    Kopano WebApp
    8
    17
    1628
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jmpalomares
      jmpalomares last edited by

      Yes, having the same issue with all day events. It shows like a 2 days event.

      1 Reply Last reply Reply Quote 0
      • A Former User
        A Former User last edited by

        @thctlo

        The problem still excist. The issue is there when using all day calendar items.

        dw2412 1 Reply Last reply Reply Quote 0
        • dw2412
          dw2412 @Guest last edited by

          @ckruijntjens

          Sorry, I’ve just tried exactly as described here to reproduce this on my site - without luck. My appointment is still in right place in attendee calendar and in my calendar.

          My timezone definition for webapp is Europe/Amsterdam and on my Windows 10 Client using Firefox it is “UTC+1 Berlin, Amsterdam…”

          Supported Kopano Packages in use (this maybe explains the difference):
          WebApp: 5.3.0.0-1+172.1
          Kopano Core: 8.7.25
          Z-Push: 2.6.4+0-0

          Windows 10 Client is Pro 21H2 Version latest Patches 03/2022
          Firefox used is x64 98.0

          So please describe what you’re using to give me possibility to test and reproduce this issue.

          Andreas

          A Former User nanathlor 2 Replies Last reply Reply Quote 0
          • A Former User
            A Former User @dw2412 last edited by

            @dw2412 Hi,

            I am using the latest builds at this moment.

            My issue was that the timezone was not configured properly ini php.ini

            Now that this is correct it dont have the issue anymore.

            1 Reply Last reply Reply Quote 1
            • nanathlor
              nanathlor @dw2412 last edited by

              @dw2412

              webapp-6.0.0.66.a7d7f94-Debian_10-all.tar.gz
              core-11.0.2.51.3b0b0e5-Debian_10-amd64.tar.gz

              All on Deb 10, client PCs are openSUSE 15.3

              We are using the Kopano kwebd as the front end web server for users with apache servicing webapp, I don’t know if that makes a difference but I don’t know why it would.

              Dave

              dw2412 1 Reply Last reply Reply Quote 0
              • dw2412
                dw2412 @nanathlor last edited by

                @nanathlor
                Just to get you right, you’re using to create and to read the appointment always Kopano WebApp - in all timezones. I mean in Europe/London where you’ve created the appointment and on other Client PCs using MS Windows in Europe/Berlin Timezone, right? Appointment is created in Summer Time or in Winter Time or is it created on day where Summer/Winter Time or Winter/Summer Time chang occurs?

                Would be easier to reproduce if you could give exact details on how appointment as exactly created (mean which fields you exactly filled with what information).

                Andreas

                nanathlor 1 Reply Last reply Reply Quote 0
                • nanathlor
                  nanathlor @dw2412 last edited by

                  @dw2412 Sure, no problem.

                  Always creating the appointment Kopano Desktop or Webapp:
                  If I create an all day appointment for tomorrow and invite someone else.
                  In My calendar is shows correctly as an all day appointment for tomorrow.
                  In the invitees calendar it shows as a 2 day appointment for today and tomorrow
                  In my mobile (z-push) it shows as an all day appointment for today
                  I understand that in M365 it shows as an all day appointment for today too.

                  If I create an all day appointment in Mobile (z-push) it works fine.

                  All PCs are Europe/London, same version OpenSUSE, same version Kopano Desktop.
                  It even works on my PC only i.e. if I send an appointment from my PC I can see the issue in other peoples calendars they have shared with me.
                  GMT/BST daylight savings has no bearing
                  I have tried changing to different timezones (e.g. Europe/Berlin) too same issue

                  Senders calender:
                  b1ef4070-4c3a-43bb-844d-d41bc4120824-image.png

                  Recipients calendar:
                  0aa3f74a-9788-4281-adfc-cc519fc3e1f4-image.png

                  Note the date range at the bottom of the recipients calendar appointment:
                  28b25669-0829-4900-846f-8d3361ce0fef-image.png

                  php -i | grep Europe
                  Default timezone => Europe/London
                  date.timezone => Europe/London => Europe/London

                  Dave

                  1 Reply Last reply Reply Quote 0
                  • klipp
                    klipp @ekpack last edited by

                    @ekpack same error here
                    did you find any slolution?

                    ekpack 1 Reply Last reply Reply Quote 0
                    • ekpack
                      ekpack @klipp last edited by

                      @klipp
                      No, till now, i haven’t found a solution.

                      klipp 1 Reply Last reply Reply Quote 0
                      • klipp
                        klipp @ekpack last edited by

                        @ekpack
                        two of our developers tried to debug and fix the bug today but kopano is doing some crazy and wired stuff in webapp so we were not able to find the bug without further information from kopano.
                        i seems like kopano community version is going to die soon

                        1 Reply Last reply Reply Quote 1
                        • darootler
                          darootler last edited by

                          I do have the same problem using the latest nightly builds.

                          Does anyone already have a solution to this?

                          Regards
                          Richard

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post