justsomeman said:
I've been having an issue since this got banned and I've installed the manual update:

On my main posts page I only have two columns and the Blacklist isn't present/functionally there and the Blacklist itself doesn't function - but only on the main posts page. If I go into a post the Blacklist functions as normal.

Any suggestions?

What do you mean by main posts page? Is it the global blacklists or is it custom blacklists?
I don't use a blacklist so I put something in there just now and when I refreshed the new posts page some posts got removed properly and the slideshow didn't view them.
only thing I can think of is if you weren't signed in on that page and refreshing would fix it...
e621 did update their UI a few days ago so maybe that broke something in some edge case?

appreciate all you've done brother, making this site much more usable. do you plan to release any updates from now on though github?
also, can anyone else not favorite through the slideshow anymore after the ui update?

something2say said:
appreciate all you've done brother, making this site much more usable. do you plan to release any updates from now on though github?
also, can anyone else not favorite through the slideshow anymore after the ui update?

So e6's UI updated twice in one month..... The one yesterday broke how the extension detected if you were logged in.
It may take a hot minute to push it to the release build.
So in the mean time if you want to fix it yourself

• in either bundle.js or util.js in the extension find the line loggedIn: () => $("#nav-account").length > 0,
• replace it with loggedIn: () => $(".sign-in").length == 0,

This does make it true by default if the class doesn't exist. Which isn't good. but for right now its a quick dirty fix.

reapersans2 said:
So e6's UI updated twice in one month..... The one yesterday broke how the extension detected if you were logged in.
It may take a hot minute to push it to the release build.
So in the mean time if you want to fix it yourself

• in either bundle.js or util.js in the extension find the line loggedIn: () => $("#nav-account").length > 0,
• replace it with loggedIn: () => $(".sign-in").length == 0,

This does make it true by default if the class doesn't exist. Which isn't good. but for right now its a quick dirty fix.

took me a bit, but changing bundle.js fixed that perfectly
you're a legend bro ty

I added a new pull request to the main branch with a fix which might take a while since wolfgang is probably doing a rewrite of the code.

Until then, I have made my own release build with a bunch of new bugfixes and a new feature in the config supporting full resolution images.
The changelog along with instructions to install is at https://github.com/Temmie-Flakes/umami/releases/latest if anyone wants it.

reapersans2 said:
since wolfgang is probably doing a rewrite of the code.

... This is very generous of you to assume xD

I have merged your PR into staging, and there is a build available on the action for people that want to test it.

If nothing obvious crops up in the next couple days I will upload it to firefox's addon site.

[2025/04/06] 2.6.0 released with more Temmie fixes

This has been released on firefox addon store, and is available on github at the link above for chrome users