Cannot follow, unfollow, or change the follow status of any manga:fixed:

[Onepunchjoey]

As the title says. The button does nothing. The drop down menu options also do nothing.

 

[iamzed]

I'm having the same problem.

 

[Plykiya]

@Onepunchjoey
@iamzed

What happens when you try a different browser?

 

[iamzed]

seems to work fine in Internet Explorer so Firefox seems to be the issue, but this only started happening recently.

 

[Holo]

Are you guys blocking javascript?

 

[DrNo]

These functions are working for me. I just picked a couple of random series and followed and unfollowed them. I am using Firefox 66.02 (64 bit). OS is Windows 10 Pro. You might try starting Firefox with add-ons disabled, and see if it makes any difference. NoScript and some similar add-ons block javascript by default, so you might have to whitelist MangaDex.

 

[iamzed]

I just started FF in safe mode with all add-on turned off and I still can't do anything with the Actions apart from follow.

 

[25kirbs]

Also having issues here, Fiefox 66.0.2 (64 bit) Windows 7
Normally run with script blocking add-ons, but whitelisting or disabling them didn't fix the issue
All page elements do nothing, can't switch any tabs on the front page, like switching the top chapters to 24h, 7d, etc
I can follow a manga, but I can't unfollow or anything else since the drop down for the follow button doesn't do anything.

I should also say I think the issue began... maybe 4 or 5 days ago? Can't remember exactly when, but it has been like this for a few days at least

 

[Onepunchjoey]

I'm on Firefox version 66.0.2 (64 bit) as well, here's what I've tested.

So with chrome it works, with private mode it works, using a different container (with the container add-on) works.

I'll delete my mangadex cookies and see if that fixes it.

 

[Plykiya]

@Onepunchjoey

Clearing cache seems to work for other people

 

[Onepunchjoey]

@Plykiya,

Thank you I thought cookies and cache were the same but I guess not. Deleting the cookies didn't do it but the cache did.

 

[iamzed]

Clearing cache fixed it for me as well, thanks for the help people.