Version 2.0 does NOT work.

[NotScooty]

Uninstalled 1.0.2 and downloaded 2.0 and it prompts me back to buying premium.

[dimdenGD]

Which browser

[NotScooty]

Chrome. Fresh install as well.

[dimdenGD]

I just installed Chrome and 2.0 extension on it 3 minutes ago and it worked fine

[vitumen]

Same here. Version 1.0.2 was working well. Now with 2.0 it took me to Buy premium

[AdamMReese]

It's not working for me, either. It redirects me to the main Twitter website and asks me to buy premium. I'm on Microsoft Edge version 116.0.1938.54 (Official build) beta (64-bit).

[piovsn]

Same here on chrome. Chrome throws up an error which links to this page https://developer.chrome.com/blog/mv2-transition/ "January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions."

[WhereTheTimeWent]

It's working fine on my end. Google Chrome 116.0.5845.97. "Updated" from 1.0.2 (loaded 2.0.0 and removed 1.0.2 manually).

[dimdenGD]

Works fine on both Edge and Chrome for me

[NotScooty]

Since I can't get 2.0.0 to work should I stick to 1.0.2 or should I try to work around it.

[AdamMReese]

Same here on chrome. Chrome throws up an error which links to this page https://developer.chrome.com/blog/mv2-transition/ "January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions."

Check the updated version of that blog post. That got postponed.

[AdamMReese]

Okay, I think it's a caching issue. I removed all the cookie and cache data for the Twitter website and reloaded, and it's working now. Everyone else can see if that works for them as well.

Edit: Of course, it could be as simple as logging out and then logging back in, but better to be safe.

[piovsn]

Clearing cache and cookies did not fix it for me unfortunately.

[AdamMReese]

Yeah, my brother is saying the same thing. It's strange, since it worked for me.

Edit: I just noticed that when I scrolled down the page itself, I see... the new TweetDeck?

There are overlapping elements and I can see the new TweetDeck in the margins behind the site as well. For instance, when I try to compose a new tweet, it shows a flashing cursor between the columns.

When I switch back to 1.0.2, it's back to normal again without the overlap and underlap.

[Uron0238]

Thank you for creating this browser extension. Does BTD support version 2.0.0? In my environment (Chrome), when I open the tweet input field, certain actions like scrolling become impossible.

[dimdenGD]

Updated again, try reinstalling and see if it works now

[lcreed]

that latest pull fixed it again on brave. It is NOW working with shields up. Thanks!!!

Anyone got the btd plugin working with this?

[AdamMReese]

After a few attempts, I got it to go back to TweetDeck, but it's still showing the new TweetDeck UI underneath and I can't compose a new tweet without it activating the UI underneath it with the flashing cursor.

[dimdenGD]

After a few attempts, I got it to go back to TweetDeck, but it's still showing the new TweetDeck UI underneath and I can't compose a new tweet without it activating the UI underneath it with the flashing cursor.

Updated, try latest version if it fixes this

[xtommas]

Not working for me on Firefox Nightly. Chrome works fine

[piovsn]

Working now on chrome, and the better tweetdeck works too. Thanks Dimden! Much appreciated.

[lcreed]

any secrets to get btd working?

[piovsn]

are you using dimden's forked version? it's linked at the bottom of the readme

[lcreed]

Ahh, didn't see that. Let me grab it and try. Thank you!

[lcreed]

Downloaded the Chrome.zip for BTD and dragged it into my Brave Extensions. Its throwing this error:

[dimdenGD]

Don't pay attention to errors, I get that error too all the time and it works fine

[lcreed]

interesting that i suddenly got an update btd had been updated and now its working. Thanks so much!

[Uron0238]

Version 1.0.2 works fine, but starting from 2.0, it doesn't function properly after opening the tweet input field. When hovering over the sidebar, a popup similar to the column names appears in the upper-left corner of the screen. Is there any correlation between these occurrences?

[AdamMReese]

Yeah, I had to switch back to 1.0.2 because I kept having that issue where the newer TweetDeck UI kept overlapping everything, even after clearing the cache. Hopefully it gets resolved soon.

[CR0077]

I use Chrome and it didn't work for me at all, got Edge and it worked for a while until it didn't and now I got Opera and it works for now. The errors just randomly appear after closing the browser and it stops working.

[arika0093]

Version 1.0.2 works fine, but starting from 2.0, it doesn't function properly after opening the tweet input field. When hovering over the sidebar, a popup similar to the column names appears in the upper-left corner of the screen. Is there any correlation between these occurrences?

I share this because I had a similar problem and solved it.

I don't know why, but it seems to be caused by the body::before element covering the entire screen and making it impossible to use. The solution is to disable it by adding the following CSS to BetterTD's custom CSS.

body:before {
    position: relative !important;
}

Browser: Google Chrome OldTweetdeck: v2.0.1 BetterTD: v4.11.1

[Fapo39]

Firefox / Firefox ESR, can't get 2.0.1 to work just takes me to buy page and this was after wiping cache and even starting new profile; v1.02 would say it's corrupted

[ItsBradaz]

Opera, neither 2.0.1/1.0.2 work anymore. Just redirects to tweetdeck login page with "Log in with your Twitter account Sorry, something went wrong. Please try again later." even after pressing login.

[codelioness]

Firefox, 2.0.1 is only redirecting to /i/premium_sign_up for me as well. Clearing cache and cookies for Twitter didn't work.

[kururuchan]

It seems to be working on and off. About 10 minutes ago I was getting the re-direct, but now it's working again.

[kleusbalut]

I share this because I had a similar problem and solved it.

I don't know why, but it seems to be caused by the body::before element covering the entire screen and making it impossible to use. The solution is to disable it by adding the following CSS to BetterTD's custom CSS.

body:before {
    position: relative !important;
}

Thank you for making a great Chrome extension. I used Stylus and the same code worked.

Japanese: 素晴らしいChrome拡張を作ってくださり、ありがとうございます。 私はStylusを使用して、同じコードで機能しました。

@-moz-document url-prefix("https://tweetdeck.twitter.com/") {
    body:before {
        position: relative !important;
    }
}

Browser: Vivaldi 6.1.3035.100 (Stable channel) (64-bit) OldTweetdeck: v2.0.1 Stylus: v1.5.33