This repository was archived by the owner on Jul 29, 2025. It is now read-only.
Fix PHP demo for current CS PHP SDK #1
Closed
Conversation
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
The composer file was looking in a lib folder, however the SDK now uses src instead. Also updated the .gitignore to include the CS SDK folder to prevent those files from being seen by this git repo.
The blog controller was looking in the wrong place for the SDK files. Seems that the CS SDK was initially being placed inside AppBundle folder but was moved at some point - since the composer file wasn’t looking there. To fix that I use dirname to get the correct folder and updated the lib to src.
Contributor
|
Thanks @mallardduck We will look into it and keep you posted. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
The current PHP SDK for ContentStack seems to have been modified since the creation of the demo. These changes will fix the demo side issues someone encounters after setting it up. There are still a few issues remaining - however those are library side issues in the SDK.