Error
While we make a huge effort to not break things during updates, when something can't be avoided we will document it here.
// From this: [RouteAttribute("api/FinancialScheduledTransactions/WithPreviousTransaction")] public HttpResponseMessage GetWithPreviousTransaction(int pageSize, int pageNumber) // To this: [RouteAttribute("api/FinancialScheduledTransactions/WithPreviousTransaction")] public virtual HttpResponseMessage GetWithPreviousTransaction(int skip, int top) // From this: [RouteAttribute("api/FinancialScheduledTransactions/Process/{scheduledTransactionId}")] public HttpResponseMessage ProcessPayment(int scheduledTransactionId, bool ignoreRepeatChargeProtection = False, bool ignoreScheduleAdherenceProtection = False) // To this: [RouteAttribute("api/FinancialScheduledTransactions/Process/{scheduledTransactionId}")] public virtual HttpResponseMessage ProcessPayment(int scheduledTransactionId, bool enableDuplicateChecking = True, bool enableScheduleAdherenceProtection = True) // From this: [RouteAttribute("api/FinancialTransactions/Process")] public HttpResponseMessage ProcessPayment(AutomatedPaymentArgs automatedPaymentArgs, bool ignoreRepeatChargeProtection = False, bool ignoreScheduleAdherenceProtection = False) // To this: [RouteAttribute("api/FinancialTransactions/Process")] public virtual HttpResponseMessage ProcessPayment(AutomatedPaymentArgs automatedPaymentArgs, bool enableDuplicateChecking = True, bool enableScheduleAdherenceProtection = True)
We've updated the way the 'unsubscribe' functionality works. Be sure to look at the generic Unsubscribe HTML in the Email medium (under Admin Tools > Communications > Communication Mediums) and make similar changes to any custom templates you have (replacing Unsubscribe/{{ Person.UrlEncodedKey }} with Unsubscribe/{{ Person | PersonActionIdentifier:'Unsubscribe' }}).
Unsubscribe/{{ Person.UrlEncodedKey }}
Unsubscribe/{{ Person | PersonActionIdentifier:'Unsubscribe' }}
SELECT ... FROM [Attendance] AS a INNER JOIN [Group] g ON a.GroupId = g.Id
SELECT ... FROM [Attendance] AS a INNER JOIN [AttendanceOccurrence] o ON o.Id = a.OccurrenceId INNER JOIN [Group] g ON a.GroupId = g.Id
{% attendance where:'GroupId == "24"' %}
{% attendance.GroupId %}
{% attendanceoccurrence where:'GroupId == "24"' %}
{% attendanceoccurrence.GroupId %}
Below is a list of all the code changes made in Rock 8.0 that may potentially affect custom code and/or plugins.
Rock.Web.UI.Cache.*
Rock.Model.Attendance.Group
Rock.Model.Attendance.IsValid
Rock.Model.Attendance.Location
Rock.Model.Attendance.Schedule
Rock.Model.Attendance.SundayDate
Rock.Model.HistoryItem.Changes
Rock.SystemGuid.DefinedType.PROTECT_MY_MINISTRY_PACKAGES
Rock.SystemGuid.DefinedType.BACKGROUND_CHECK_TYPES
The following properties were removed from the Rock.Model.Group class:
Rock.Model.Group
These properties were all moved to a new Rock.Model.GroupSync class to support role-specific group syncing.
Rock.Model.GroupSync
If you are using the SendGrid Email Transport update the plugin from the RockShop immediately after upgrading to Rock v7.
Page view and email activity data has been moved in Rock v7. While we make a huge effort to not break things during updates the transition of this data to new tables may break custom SQL or code that was querying this data from the PageView and/or CommunicationRecipientActivity tables. All of the data has been transitioned to their new home in the Interactions tables so you won't miss a thing. This should impact only a very small number of organizations who have written custom code or SQL against these few tables. Note that since there could be a large amount of data to convert from the old PageView and CommunicationRecipientActivity tables, a Rock Job called 'Move Data from PageViews and Communication Activity to the new Interaction Tables' will run at 4am after v7 is installed. This job could take an hour or so depending on how much data there is.
The external giving blocks have a new 'Give as Business' option which defaults to 'on'. If you don't want your giving blocks to have the 'Give as Business' option, you'll have to change that manually.
There is a new 'Expiring Credit Card Notices' job which is enabled to run at 7:30 AM on the 1st of every month. It can be disabled manually if needed.
The ZebraPhoto lava command was changed to use the R: (DRAM) location due to long term problems with repetitive writing to the E: (Flash) location. Any labels using ZebraPhoto must also change their Recall Graphic (^XG) command to use the R: location too. http://www.rockrms.com/lava/person#zebraphoto
There is a new 'Database Maintenance' job that is enabled to run at 2:30 AM every day by default. If you SQL database already has a maintenance plan, update the 'Database Maintenance' job and/or your SQL Maintenance Plan to do what you want.
Make sure to enable the Google Static Maps API in your Google API Manager dashboard.
A change was made in how group requirement notifications are sent out. Before it would send to all Roles marked 'IsLeader' of the group, with the ability to provide a list of Role Ids to exclude. This has been changed to use the 'Receive Requirements Notifications' property on the Role. If you have setup jobs to send group requirement emails you will want to ensure that you configure the roles you want to receive these emails to have the 'Receive Requirements Notifications' checked.
Staff and Staff-Like roles will be given Edit access to the following group types if those group types do not already have specific 'Edit' roles defined. This is so that staff can add new groups of those types.
ContentChannelView has been updated to not support legacy Lava syntax for accessing global attributes. To enable this, a new "Enable Legacy Global Attribute Lava" block setting needs to be set to true (which negatively affect performance of this block).
Group Attributes now enforce security. Edit each Group Type in General Settings > Group Types, and make sure to set the security on each of the Group Attributes so they can be edited by the appropriate team.
iScroll.js is now included in the RockLibs.js bundle. If you have a custom blocks (i.e. check-in) that is loading iScroll.js, this is no longer needed.
This release fixes a bug where workflow activities marked as inactive were still being processed. If you have any activities where 'Is Active' is not checked they will no longer run even if you use the 'Activate Workflow Activity' action. This action activates an instance of an activity. The activity type however, must be active for this to occur.
Below is a list of all the code changes made in Rock v7 that may potentially affect custom code and/or plugins.
People without birth date will no longer be able to check-in to groups that have an age range requirement. This behavior can be changed by editing the 'Unattended Check-in' workflow, selecting the 'Person Search' activity, then the 'Filter Groups By Age' action, and un-checking the new 'Age Required' option.
Only members of the 'RSR - Data Integrity Worker' will be able to complete person merges. Everyone else will only be able to request merges (new functionality). This can be modified by adding other security roles to have edit access to the merge block.
Security was adjusted on the Website Ads and Bulletin Content Channels to give the 'RSR - Staff Worker' and 'RSR - Staff Like Worker' View/Edit rights.
The regular release notes detail changes that are important to admins and users. There is also a pre-alpha release notes which covers stuff in the latest pre-alpha-release branch.