You are viewing the PKP Support Forum | PKP Home Wiki

Database errors after patching to 2.4.2

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
The Public Knowledge Project Support Forum is moving to http://forum.pkp.sfu.ca

This forum will be maintained permanently as an archived historical resource, but all new questions should be added to the new forum. Questions will no longer be monitored on this old forum after March 30, 2015.

Database errors after patching to 2.4.2

Postby szczuka » Thu Oct 17, 2013 1:53 am


After patching form 2.3.6 to 2.4.2 I kee p experiencing various problems.
One still unresolved is described here viewtopic.php?f=8&t=10797#p41856
The other one I have got is that somemany of my editors, who do not have the problem mentioned above, keep getting the database error when they click on "In review" or "Unassigned" in their pages. The error is always the same:
DB Error: Unknown column 'ea.user_id' in 'where clause'
It looks like if they have an unmodified version of the user home page, that calls for a non-existing column. Should I modify the users in database or the code that generates page.
If the latter, what files are responsible for this problem? During patching the only files that not patched properly were:

I have manually replaced the SectionEditorAction.inc.php and PKPUser.inc.php with version from 2.4.2 - which may be the source of the problem, but I need a guidance what to do. The problem is a serious one and the complete reinstallation is not an option.

Marcin Szczuka
Posts: 14
Joined: Wed Aug 03, 2011 5:03 am

Re: Database errors after patching to 2.4.2

Postby JasonNugent » Thu Oct 17, 2013 5:34 am

Hi Marcin,

It sounds like you're running into a lot of the issues that have been fixed in our 'recommended patches' list for 2.4.2:

http://pkp.sfu.ca/wiki/index.php/OJS_2. ... ed_Patches

In particular, the incorrect column name was solved in this bug:


By applying this patch:

https://github.com/pkp/ojs/commit/35edd ... b75a1.diff

Site Admin
Posts: 910
Joined: Tue Jan 10, 2006 6:20 am

Return to OJS Technical Support

Who is online

Users browsing this forum: No registered users and 3 guests