I had fixed this issue. After investigation, there were 2 records for the "calendar" route in the route_new table one of which was invalid and the one being used which was causing the issue. Deleting or renaming the invalid one fixed it.
It turned out that prior to the release of the Calendar feature, Craig had used the "calendar" route in the old custom Calendar page he created using Google Calendar iframe. I wonder why the upgrade script (when Calendar was introduced) didn't detect it and update the existing calendar route record instead of inserting a new one.
It turned out that prior to the release of the Calendar feature, Craig had used the "calendar" route in the old custom Calendar page he created using Google Calendar iframe. I wonder why the upgrade script (when Calendar was introduced) didn't detect it and update the existing calendar route record instead of inserting a new one.
Comment