March 6, 2020 - version 2.20.13 -- Ongoing maintenance and feature updates
John Keith
started a topic
about 1 year ago
Comments:
We put a change in the next release to re-enable editing of a meeting series schedule after the series has ended. Typical scenario being, the user wants to extend the series. It turns out the reason we disabled that was somewhat indirect -- we were removing the ability to mess with a bunch of things on past meetings, prompted by Elise's noticing that when you do that, you don't get prompted to send invitations again.
We added some little improvements -- when you extend an "expired" meeting series you will land on the next upcoming meeting, instead of the past one you started with, and I added a prompt to re-send the series invitations to the success message.
Bug fixes:
User-visible:
* Fix JS error after adding a new member to an organization. I
introduced this when removing footable SPF for some tables.
* Remove the optional password field from the add your organization form.
* Add "Add a URL" to agenda item editor for meeting templates
* Correct the download behavior for link attachments in the meeting template editor
* Fix broken facilitator guide upload for meeting template in a room (case 10999)
* Fix up the Add Meeting list in the top nav. Was missing some.
* Tune the permissions related to who can edit post-meeting content.
* Correct an error in recurrence descriptions, was putting wrong start date in invitation emails.
* Delete integration links when the associated integration_auth
is deleted via drupal-side code; corrects a situation where
Bascamp mappings were repeatedly lost.
Not user-visible:
* Stop calling the fullcontact API (issue with a google signup).
* Small change to set the member_id before calling fullcontact.
* Fix a bug found by inspection while performance profiling.
* Fix a little array merge bug I just introduced.
* Fix a user_access check.
* Fixed a user delete bug and made related changes associated with cascading deletes.
New features and changes:
* Improve UI for selecting timezone when scheduling or finding a
meeting time. (Add the chosen() widget to the timezone selector
for scheduling or finding a meeting time.)
* Add an attendance download button to the past meetings history page.
* Restore ability to change the schedule of a meeting series that has ended
* Restore the old behavior of account links going to the organization overview page instead of the rooms page.
* Allow meeting participants to edit post-meeting data under more circumstances.
Subscriptions and Billing:
* WIP on allowing end users to to change their subscription plan.
* For enterprise billing count organization members instead of room members.
* WIP on showing billing for various org types
* More WIP to integrate the fixed-price business plan
* Cleaning up the personal and business flex upgrade / downgrade paths.
* Loosen up the ability to manage an account in dunning, so people can actually update their credit card.
* Only record active organizer for a meeting starter if that person is a manager in one or more rooms.
Performance:
* Add just a wee bit of manual in-process caching to reduce DB calls.
* More WIP on UI scalability. Create a separate page for large amounts of meeting history.
* WIP on UI scale.
* Minor WIP on performance for larger tables of data. Such as the org home w/tabs.
* Some WIP on UI scalability (footables mostly).
* WIP on the room-level meeting attendance report. A small step forward.
* WIP on user-perceived performance improvements for rendering the room list for an organiztion tab..
* Cache failure to find room member so we don't keep trying during a single page load.
* Remove static caching of access results (now in user.inc).
* Cache user access checks used by the access functions.
* Do not include the delete modal on room meetings page.
* Optimize the getting of followups to-be-sent for large numbers of meetings (room meetings page).
* Cache the results of user access queries in a give page session to reduce excessive user_load() calls.
* Do not check lucid forms for captchas. Excessive SQL queries.
Chrome extension:
* Add the calendar.readonly scope to our Google auth list.
Office add-in
* Update to the Office 365 add-in
* API: Add windows_timezone to recurrence resource fields. (Case 10994)
* Add a routine for getting the Windows zone for an IANA timezone name (case 10994)
* Add a mapping from IANA to Windows time zones. (Case 10994)
* API: Allow Synchronizer user to look up meeting sources by type and ID, or by meeting ID, independent of member_id. (case 10982)
* API: Allow Synchronizer user to look up meeting series sources by type and ID, or by meeting series ID, independent of member_id. (case 10982)
* API: bug fix for synchronizer access to deleted attendee
* API: Extend synchronizer's search for a user to impersonate (case 10982)
* API: Extend synchronizer impersonation; if meeting lacks facilitators, get a room manager.
* API: merge synchronizer access work into default
* API: add source_data to meeting_series_source POST; was not being saved (case 10981)
* merge
* API: Include source_data with embedded meeting_source, meeting_series_source
* Add full meeting_series_source to meeting_series POST
* API: add documentation for including a meeting_source when creating a meeting
* API: quick addition of full meeting_source (with data) to meeting POST
* API: add start_time, end_time to deleted_meetings
Code cleanup:
* Remove an unnecessary reference to global vars.
* More consistent use of account_member::makeXXX functions.
* Minor tweaks while doing some performance review.
* Correct the download behavior for link attachments in the meeting template editor
* Update to the Office 365 add-in
* Add "Add a URL" to agenda item editor for meeting templates
* API: Add windows_timezone to recurrence resource fields. (Case 10994)
* Add a routine for getting the Windows zone for an IANA timezone name (case 10994)
* API: Allow Synchronizer user to look up meeting sources by type and ID, or by meeting ID, independent of member_id. (case 10982)
* API: Allow Synchronizer user to look up meeting series sources by type and ID, or by meeting series ID, independent of member_id. (case 10982)
* API: add source_data to meeting_series_source POST; was not being saved (case 10981)
* Add a mapping from IANA to Windows time zones. (Case 10994)
* API: Include source_data with embedded meeting_source, meeting_series_source * Fix up the Add Meeting list in the top nav. Was missing some.
* Small change to set the member_id before calling fullcontact. * Add an attendance download button to the past meetings history page.
* API: bug fix for synchronizer access to deleted attendee
* Add full meeting_series_source to meeting_series POST
* API: add documentation for including a meeting_source when creating a meeting
* API: quick addition of full meeting_source (with data) to meeting POST
* Add the calendar.readonly scope to our Google auth list.
* Tune the permissions related to who can edit post-meeting content.
* WIP on showing billing for various org types
* Fix broken facilitator upload for meeting template in a room (case 10999)
* More WIP to integrate the fixed-price business plan
* Cleaning up the personal and business flex upgrade / downgrade paths.
* API: add start_time, end_time to deleted_meetings
* Add just a wee bit of manual in-process caching to reduce DB calls.
* More WIP on UI scalability. Create a separate page for large amounts of meeting history.
* WIP on UI scale.
* Remove an unnecessary reference to global vars.
* Minor WIP on performance for larger tables of data. Such as the org home w/tabs.
* Some WIP on UI scalability (footables mostly).
* Restore the old behavior of account links going to the organization overview page instead of the rooms page.
* WIP on the room-level meeting attendance report. A small step forward.
* WIP on user-perceived performance improvements for rendering the room list for an organiztion tab..
* For enterprise billing count organization members instead of room members.
* More consistent use of account_member::makeXXX functions.
* Correct a really boneheaded error in recurrence descriptions.
* Restore ability to change the schedule of a meeting series that has ended (see case 9521)
* API: Extend synchronizer's search for a user to impersonate (case 10982)
* Loosen up the ability to manage an account in dunning, so people can actually update their credit card.
* Minor tweaks while doing some performance review.
* Cache failure to find room member so we don't keep trying during a single page load.
* Remove static caching of access results (now in user.inc).
* Cache user access checks used by the access functions.
* Do not include the delete modal on room meetings page.
* Fix a bug found by inspection while performance profiling.
* Optimize the getting of followups to-be-sent for large numbers of meetings (room meetings page).
* Cache the results of user access queries in a give page session to reduce excessive user_load() calls.
* Do not check lucid forms for captchas. Excessive SQL queries.
* Fix a user_access check.
* Fixed a user delete bug and made related changes associated with cascading deletes.
* API: Extend synchronizer impersonation; if meeting lacks facilitators, get a room manager.
* API: merge synchronizer access work into default
* Allow meeting participants to edit post-meeting data under more circumstances.
* Delete integration links when the associated integration_auth is deleted via drupal-side code (case 10974)
* Only record active organizer for a meeting starter if that person is a manager in one or more rooms.
John Keith
Comments:
We put a change in the next release to re-enable editing of a meeting series schedule after the series has ended. Typical scenario being, the user wants to extend the series. It turns out the reason we disabled that was somewhat indirect -- we were removing the ability to mess with a bunch of things on past meetings, prompted by Elise's noticing that when you do that, you don't get prompted to send invitations again.
We added some little improvements -- when you extend an "expired" meeting series you will land on the next upcoming meeting, instead of the past one you started with, and I added a prompt to re-send the series invitations to the success message.