Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OJS] uBlock Origin browser plugin causing problems in OJS 3.0.2 #2316

Closed
ajnyga opened this issue Feb 28, 2017 · 4 comments
Closed

[OJS] uBlock Origin browser plugin causing problems in OJS 3.0.2 #2316

ajnyga opened this issue Feb 28, 2017 · 4 comments

Comments

@ajnyga
Copy link
Collaborator

ajnyga commented Feb 28, 2017

Hi,

One of our journal editors noticed that when he had the uBlock Origin browser plugin enabled some of the features in OJS 3.0.2. stopped working.

For example when trying to view the editorial history page for a submission the content of the modal window kept on loading. I was first convinced that some error was causing this, but it turned out that simply disabling the browser plugin the editoria history page loaded without problems.

Probably uBlock Origin filters are catching something in the code that they consider to be an ad? I am using Adblock Plus and have not encountered anything similar.

@ajnyga
Copy link
Collaborator Author

ajnyga commented Feb 28, 2017

The string that uBlock Origin is picking up is /event-log/

Basically the call to http://domain.fi/journal/$$$call$$$/grid/event-log/submission-event-log-grid/fetch-grid?submissionId=60532&_=1488312791239 is blocked because of that string.

I can of course make an exception for a domain in the adblocker, but probably most of the users will not realize what the problem is.

@asmecher
Copy link
Member

asmecher commented Mar 1, 2017

@ajnyga, thanks for tracking this down. I'm not sure whether there's anything we ought to do here, beyond noting it in case someone else hits the same problem. We also occasionally have similar run-ins with mod_security in other situations, and my feeling is that we shouldn't rename elements of the software to suit overreaching rules like this.

@ajnyga
Copy link
Collaborator Author

ajnyga commented Mar 1, 2017

Yes agreed, there is not much sense in filtering /event-log/ to start with in my opinion. Maybe it would be actually better to send a bug report to the plugin developer.

@asmecher
Copy link
Member

asmecher commented Mar 1, 2017

Agreed, thanks!

@asmecher asmecher closed this as completed Mar 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants