Snehal social media scheduler#1359
Closed
SnelPatare wants to merge 35 commits into
Closed
Conversation
|
Hi, |
|
Tested backend PR #1359 with related frontend PR #3466 ,server runs fine, but Facebook API call returns “App not active.” Functionality depends on Facebook developer app reactivation or tester access. |
Member
|
Replaced with new PR set: OneCommunityGlobal/HighestGoodNetworkApp#4714 and #2005 |
1 similar comment
Member
|
Replaced with new PR set: OneCommunityGlobal/HighestGoodNetworkApp#4714 and #2005 |
This file contains hidden or 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.
Description
(PRIORITY HIGH) Jae: Create appropriate auto-poster for Facebook + Facebook Groups - Scheduler
Related PRS (if any):
This Backend PR is related to the OneCommunityGlobal/HighestGoodNetworkApp#3466 Frontend PR.
To test this backend PR you need to checkout the OneCommunityGlobal/HighestGoodNetworkApp#3466 frontend PR
Main changes explained:
How to test: