Closed tremby closed 10 years ago
Same here, moving the class inside a new lib/Instagram folder and a composer dumpautoload --optimize
solves the problem for me
That's no good for me since I need this to automatically deploy on various server instances. What I've done for now is manually require_once the file where the class is needed. On 22 Mar 2014 02:54, "Gabriele Perego" notifications@github.com wrote:
Same here, moving the class inside a new lib/Instagram folder and a composer dumpautoload --optimize solves the problem for me
Reply to this email directly or view it on GitHubhttps://github.com/cosenary/Instagram-PHP-API/issues/37#issuecomment-38347400 .
You can fork the repo (fix it) and install that one via composer
Yes, I could. But this solution is good enough for now. This ticket was not asking for solutions; just to alert the maintainer so hopefully it'll get fixed for everyone, not just me. On 22 Mar 2014 04:36, "Gabriele Perego" notifications@github.com wrote:
You can fork the repo (fix it) and install that one via composer
Reply to this email directly or view it on GitHubhttps://github.com/cosenary/Instagram-PHP-API/issues/37#issuecomment-38349203 .
Thanks! Should be fixed in version 2.2
(85aea6e964b7f362cb1ea3ae338cfc4bca4b8933).
Perhaps I'm doing something wrong, but the Instagram class is not autoloaded after installation via Composer.