Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-65262

Moodle 3.6 whitespace database invalid response

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Log in as admin.
      2. Navigate to _Calendar > Manage subscriptions ({wwwroot}/calendar/managesubscriptions.php)
      3. Under Import calendar, set the following:
        • Calendar name: Test leading whitespace in location.
        • Import from: Calendar file (.ics).
        • Choose a file: Upload the testCalEvent.ics file attached to this Tracker issue.
        • Type of event: User.
      4. Click Add.
      5. Navigate back to the Calendar monthly view.
      6. CONFIRM you see the event on 8 April 2019 in the calendar.
      7. CONFIRM you receive no error message.
      8. Click on the calendar event
      9. Click on Edit
      10. Click on Show more so details such as location are displayed.
      11. CONFIRM the information in the calendar entry loads (including location).
      12. CONFIRM that the location has no leading or trailing whitespace
      13. Close the event.
      14. Create a new user calendar event within Moodle, called 'MDL-65262'. Include  a location with a space at the start, reading ' starting space'.
      15. Save the event.
      16. Refresh the calendar monthly view.
      17. CONFIRM you receive no errors.
      18. Open your 'MDL-65262' calendar event and click 'show more'.
      19. CONFIRM the event details load, but the location is now 'starting space' (with no space at the start).
      Show
      Log in as admin. Navigate to _Calendar > Manage subscriptions ({wwwroot}/calendar/managesubscriptions.php) Under Import calendar , set the following: Calendar name: Test leading whitespace in location. Import from: Calendar file (.ics). Choose a file: Upload the testCalEvent.ics file attached to this Tracker issue. Type of event: User. Click Add . Navigate back to the Calendar monthly view. CONFIRM you see the event on 8 April 2019 in the calendar. CONFIRM you receive no error message. Click on the calendar event Click on Edit Click on Show more so details such as location are displayed. CONFIRM the information in the calendar entry loads (including location ). CONFIRM that the location has no leading or trailing whitespace Close the event. Create a new user calendar event within Moodle, called ' MDL-65262 '. Include  a location with a space at the start, reading ' starting space'. Save the event. Refresh the calendar monthly view. CONFIRM you receive no errors. Open your ' MDL-65262 ' calendar event and click 'show more'. CONFIRM the event details load, but the location is now 'starting space' (with no space at the start).
    • Affected Branches:
      MOODLE_36_STABLE
    • Fixed Branches:
      MOODLE_36_STABLE
    • Pull from Repository:
    • Pull 3.6 Branch:
    • Pull Master Branch:
      MDL-65262-master

      Description

      Moodle 3.6+ , upon update from 3.5 we happen to have a problem with the database issued by the calendar events, logs are clear and all good, just that upon logg in it pops up invalid response , so everytime the calendar is modified or new data is coming in we have to alter the database to delete whitespaces that are left upon the updates on the interface. Any hints on how to fix ? If i reroll back on 3.5 it works without problems. 

      Thanks.

        Attachments

        1. calendar location error.png
          calendar location error.png
          57 kB
        2. screenshot-1.png
          screenshot-1.png
          163 kB
        3. testCalEvent.ics
          0.7 kB

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                13/May/19

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 hours, 5 minutes
                3h 5m