OJS 3.1.0.1 Access and error log filling with references to old(?) citation plugin addresses

@ajnyga wrote:

Hi,

After upgrading to OJS 3.1.0.1. our access log and error log is filling up with 404 errors that are caused by requests to old citation plugin addresses.

There are so many of them that also Google Webmaster tools has sent me an email about the growing number of 404’s two times now. First I thought that they would eventually stop, but they just keep on coming. Any idea what is causing them? I am thinking that this is connected to the change that occured with the citationStylePlugin. Maybe there should be a 302 redirect of some sort? @NateWr @asmecher

Here are a few of them within just a couple of seconds. This is from the access log, there is a corresponding 404 error line in the error_log of course.
54.xx.xx.70 - - [18/Feb/2018:21:13:04 +0200] “GET /journal1/article/cite/50582/CbeCitationPlugin HTTP/1.1” 404 22
54.xx.xx.85 - - [18/Feb/2018:21:13:18 +0200] “GET /journal2/article/cite/60023/RefWorksCitationPlugin HTTP/1.1” 404 22
54.xx.x.143 - - [18/Feb/2018:21:13:19 +0200] “GET /journal3/article/cite/58614/BibtexCitationPlugin HTTP/1.1” 404 22
54.xx.xx.39 - - [18/Feb/2018:21:13:20 +0200] “GET /journal4/article/cite/8313/RefManCitationPlugin HTTP/1.1” 404 22

All these errors are making the error log pretty useless, or at least hard to follow. I got around 100 404 errors within 5 minutes so after a day or so you really have to search for actual errors.

edit: ok, so it was what I suspected: https://github.com/pkp/ojs/commit/0f9a65806bcc6bb5e634b71830d253db64c1e82f#diff-fb472ff00e77018e59dc4279d1917e96

I am worried that the large amount of 404s will affect our results in google. Maybe when handlers are removed from OJS there should be a policy of first adding a 302 redirect and removing the actual handler only later?

Posts: 1

Participants: 1

Read full topic