<p>It was indeed missing files, as suggested by Alec and Benjamin. All down to some non-specific .gitignore rules that meant it was ignoring all "src" folders - which is one of the folders created by the composer install</p>

<p>Thanks for your help guys!</p>

CC BY-SA 3.0
2015-08-19T12:25:29.737Z
2015-08-19T12:25:29.737Z
Digital Squid
<p>I'm using the <a href="https://dukt.net/craft/twitter" rel="nofollow">Dukt Twitter</a> plugin which requires the <a href="https://dukt.net/craft/oauth" rel="nofollow">Dukt OAuth</a>  plugin.</p>

<p>Both are working perfectly on both my local Dev environment and the remote Staging environment, but not on the Live site. Both plugins install with no errors or problems. Configuring the OAuth plugin (for Twitter only) is fine as well - it accepts the keys/credentials generated from the Twitter API Management Console and shows as "configured" on it's status screen.</p>

<p>However, when I then go to the actual Twitter plugin config and hit the "Connect to Twitter" button, I get this error message:</p>

<pre><code>Fatal error: Class 'League\OAuth1\Client\Server\Twitter' not found in /webserver/domains/[CLIENT]/live/craft/plugins/oauth/providers/Twitter.php on line 46
</code></pre>

<p>Anyone have any idea what this error message means?</p>

<p>I suspect it's more to do with the server or site config than the actual plugin but I'm not sure where to start looking as I don't understand why it can't find that namespace</p>

CC BY-SA 3.0
2015-08-17T21:38:47.083Z
It looks like a file is missing, How are you copying the files to your live server? If your sure than maybe try deleting the vendor directory in the oauth plugin folder, adding this composer.json file: https://github.com/dukt/craft-oauth/blob/master/Source/composer.json and running `composer install` , that way you know for sure all the vendor files are there
Alec Ritson
CC BY-SA 3.0
2015-08-18T12:05:21.330Z
Yeah I think you might just be missing some files. When you download those plugins from GitHub, you're actually only downloading the source and have to build them before they work (as described by Alec). When you download them from dukt.net, the plugins are built and ready to install. Try to do a fresh download/install of both plugins and you should be good to go.
Benjamin David
<plugin-duktoauth><plugin-dukttwitter>
Help understanding an error message from Dukt OAuth plugin
# Help understanding an error message from Dukt OAuth plugin

(Asked by: username_0 on 2015-08-17)

I'm using the Dukt Twitter plugin which requires the Dukt OAuth  plugin.
Both are working perfectly on both my local Dev environment and the remote Staging environment, but not on the Live site. Both plugins install with no errors or problems. Configuring the OAuth plugin (for Twitter only) is fine as well - it accepts the keys/credentials generated from the Twitter API Management Console and shows as "configured" on it's status screen.
However, when I then go to the actual Twitter plugin config and hit the "Connect to Twitter" button, I get this error message:
Fatal error: Class 'League\OAuth1\Client\Server\Twitter' not found in /webserver/domains/[CLIENT]/live/craft/plugins/oauth/providers/Twitter.php on line 46

Anyone have any idea what this error message means?
I suspect it's more to do with the server or site config than the actual plugin but I'm not sure where to start looking as I don't understand why it can't find that namespace

**Tags:** plugin-duktoauth, plugin-dukttwitter
> **Comments:**
> **username_1**: It looks like a file is missing, How are you copying the files to your live server? If your sure than maybe try deleting the vendor directory in the oauth plugin folder, adding this composer.json file: https://github.com/dukt/craft-oauth/blob/master/Source/composer.json and running `composer install` , that way you know for sure all the vendor files are there  
> **username_2**: Yeah I think you might just be missing some files. When you download those plugins from GitHub, you're actually only downloading the source and have to build them before they work (as described by Alec). When you download them from dukt.net, the plugins are built and ready to install. Try to do a fresh download/install of both plugins and you should be good to go.  

---

## 1 answers

### Answer by username_0 on 2015-08-19. Score: 1

It was indeed missing files, as suggested by Alec and Benjamin. All down to some non-specific .gitignore rules that meant it was ignoring all "src" folders - which is one of the folders created by the composer install

Thanks for your help guys!


---

