fix: maintain backwards compatibility #995
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add backward compatibility for webhook services.
Instead of being saved in
rop_data.services, they will be saved inrop_data.services_webhooks! (same thing for active accounts)The
setandgetfunctions have been modified to ensure that pulling and saving the data are the same for the whole program, even if the data is from two different sources.Note
THe way we merge the data is by making the webhooks always appear first in the Dashboard. If this bothers someone, the accounts can be sorted by the creation date.
Testing
Use the build from this PR together with https://github.com/Codeinwp/tweet-old-post-pro/pull/537