<p>While we wait for an official update, you can patch this pretty easily. Just open up craft/plugins/twitter/TwitterPlugin.php and find this function:</p>



<pre class="lang-php prettyprint-override"><code>public function getSettingsHtml()
{
    // ...
}
</code></pre>

<p>Delete the function entirely, and replace it with this:</p>

<pre class="lang-php prettyprint-override"><code>public function getSettingsUrl()
{
    return 'twitter/settings';
}
</code></pre>

CC BY-SA 3.0
2015-12-02T13:48:39.383Z
2015-12-02T13:48:39.383Z
Brandon Kelly
<p>I actually had to make this same change to the OAuth part of this plugin at craft/plugins/oauth/OauthPlugin.php</p>

CC BY-SA 3.0
2015-12-09T21:03:03.757Z
Are you on the latest versions? Could explain my recent issues
Alan Miller
CC BY-SA 3.0
2015-12-09T20:08:58.067Z
2015-12-09T20:08:58.067Z
Adam McCombs
<p>Weird issue when upgrading Craft to 2.5 that the settings link in the revised dashboard redirects to the settings page for the Dukt twitter add-on. If I disable the add-on then works just fine. Anybody else experiencing this problem?</p>

<plugin-dukttwitter>
Dukt twitter issue Craft 2.5
# Dukt twitter issue Craft 2.5

(Asked by: username_0 on 2015-12-02)

Weird issue when upgrading Craft to 2.5 that the settings link in the revised dashboard redirects to the settings page for the Dukt twitter add-on. If I disable the add-on then works just fine. Anybody else experiencing this problem?

**Tags:** plugin-dukttwitter

---

## 2 answers

### Answer by username_1 on 2015-12-02. Score: 2

While we wait for an official update, you can patch this pretty easily. Just open up craft/plugins/twitter/TwitterPlugin.php and find this function:
public function getSettingsHtml()
{
    // ...
}

Delete the function entirely, and replace it with this:
public function getSettingsUrl()
{
    return 'twitter/settings';
}


---

### Answer by username_2 on 2015-12-09. Score: 1

I actually had to make this same change to the OAuth part of this plugin at craft/plugins/oauth/OauthPlugin.php

> **Comments:**
> **username_3**: Are you on the latest versions? Could explain my recent issues  

---

