Today I faced a very strange problem when I logged into my journal as Editor. I see this message:
DB Error: The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay
However, I can login as author, reviewer, section editor ( logging through other users account), but when I click on Editor in my user home page, I see this message. It is not allowing to go through the editorial process of newly submitted papers. Please help.
Sincerely,
Sanjeev
Error message when logged in as Editor
Moderators: jmacgreg, michael, John, vgabler
Forum rules
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.
What to do if you have general, workflow or usability questions about OJS:
1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.
2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.
3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.
What to do if you have general, workflow or usability questions about OJS:
1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.
2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.
3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.
3 posts
• Page 1 of 1
Error message when logged in as Editor
by sanjeevsys » Tue Oct 19, 2010 1:27 pm
- sanjeevsys
- Posts: 2
- Joined: Fri May 08, 2009 12:19 am
Re: Error message when logged in as Editor
by sanjeevsys » Tue Oct 19, 2010 1:30 pm
Hi Alec:
Thanks for your reply which is:
That's a MySQL error message, not something OJS generates -- you'll have to either increase the maximum join size in your MySQL config as the error message suggests, or find out which query is triggering the message and optimize it.
I don't understand how to fidn out the query which is triggering this message and/or increase the max join size. Please can you suggest something on this.
Sincerely,
Sanjeev
Thanks for your reply which is:
That's a MySQL error message, not something OJS generates -- you'll have to either increase the maximum join size in your MySQL config as the error message suggests, or find out which query is triggering the message and optimize it.
I don't understand how to fidn out the query which is triggering this message and/or increase the max join size. Please can you suggest something on this.
Sincerely,
Sanjeev
- sanjeevsys
- Posts: 2
- Joined: Fri May 08, 2009 12:19 am
Re: Error message when logged in as Editor
by asmecher » Tue Oct 19, 2010 1:50 pm
Hi Sanjeev,
You should be able to find the particular query in your MySQL error log (depending on how MySQL is configured). Alternately, you can change the "debug" setting in OJS's config.inc.php file to "On" and view the page that causes the problem; it'll contain all the database queries that are used to generate the page, and the last (or next-to-last) should be the problematic query. Note that turning this option on will make your OJS site unusable until you turn it back off again.
Regards,
Alec Smecher
Public Knowledge Project Team
You should be able to find the particular query in your MySQL error log (depending on how MySQL is configured). Alternately, you can change the "debug" setting in OJS's config.inc.php file to "On" and view the page that causes the problem; it'll contain all the database queries that are used to generate the page, and the last (or next-to-last) should be the problematic query. Note that turning this option on will make your OJS site unusable until you turn it back off again.
Regards,
Alec Smecher
Public Knowledge Project Team
- asmecher
- Posts: 5768
- Joined: Wed Aug 10, 2005 12:56 pm
3 posts
• Page 1 of 1
Return to OJS Editorial Support and Discussion
Who is online
Users browsing this forum: No registered users and 1 guest