Use oAuth with getExpose() #42
Open
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
added 3 commits
December 13, 2016 11:20
to avoid E_NOTICE as of php 4.3 when session is already started
so Objects published only for „Hompage“ on IS24 can be retrieved. Should work with IS24 published Objects as well. App has to be zertified
before trying to redeclare it. Otherwise fatal php error is thrown if php oAuth extension is installed.
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.
getExpose() did not work with Objects published only for "Hompage" at IS24. With oAuth getExpose can retrieve such Objects and also "IS24" published Objects. Downside is the App needs to be certified.
I also disabled session_start(), since this results in a E_NOTICE since php 4.3 if a Session is already started. The App code should start the session, should it not?
The OAuth class just defined the OAuthException class without checking if it already exists. This resulted in a fatal error if the PHP oAth extension is installed.