You are viewing the PKP Support Forum | PKP Home Wiki

Problem in Journal Setup

Are you an Editor, Author, or Journal Manager in need of help? Want to talk to us about workflow issues? This is your forum.

Moderators: jmacgreg, michael, vgabler, John

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.

Problem in Journal Setup

Postby pjohanneson » Thu Jan 08, 2004 12:16 pm

Whenever I try to save my settings on the page User > Admin > Journal Setup > Step 2 (ie, /journal/admin/editor/step2.php), I get the error message Failed to update tbljournal table. All the other pages so far have worked just peechy-freekin'-keen for me.

I'm working with an install from scratch, on Apache 1.3.29, PHP 4.1.2, Windows 2000, MySQL 4.0.16.

Any ideas?


Posts: 12
Joined: Thu Jan 08, 2004 12:12 pm

Postby kevin » Sat Jan 10, 2004 9:50 pm

If you could edit admin/editor/step2.php and change Line 59 from:

Code: Select all
$db->query($query) or die("Failed to update tbljournal table");


Code: Select all
$db->query($query) or die(sprintf("<pre>Failed to update tbljournal table.\nERROR: %s\nSTATEMENT: %s</pre>", $db->error(), $query));

That will provide some more useful error output with the failure message.

If you could post this output here or email it to ojs at pkp.ubc.ca we may be better able to diagnose the problem.
Posts: 338
Joined: Tue Oct 14, 2003 8:23 pm

Postby pjohanneson » Mon Jan 12, 2004 8:04 am

Here's what I get:

Failed to update tbljournal table.
ERROR: 1064: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 's transmittal letter and determine whether you can complete the
STATEMENT: update tbljournal set chFocusScope = '',
nReviewersPerPaper = '1',
nReviewDueWeeks = '2',
chReviewProcess = '',

Example from the American Society for Micobriology Journals...

On receipt of the manuscript, you the reviewer should do three things immediately.

Read the editor's transmittal letter and determine whether you can complete the review in the stated time period, usually 2 to 3 weeks.
Double-check the author's cover letter if included, the manuscript title page, and the Acknowledgments section to determine whether there is any conflict of interest for you (with the authors, their institution, or their funding sources) and whether you can judge a given article impartially. (See also p. 5 of these Guidelines.)
Quickly skim the relevant portions of the manuscript and verify that it fits within the scope of the journal.

If you have either a time problem or a conflict of interest, contact the editor for instructions. He may extend your deadline, ask whether there is a colleague at your institution who could do the review, or ask you to return the manuscript to him for reassignment (and, if possible, for you to provide the names and addresses of other reviewers who are competent to handle the subject matter). You may not give the manuscript to a colleague to review without the editor's permission. If your cursory examination reveals that the manuscript does not fit within the scope of the journal, contact the editor for instructions.

Do not discuss the paper with its authors either during or after the review process. Although it may seem natural and reasonable to discuss points of difficulty or disagreement directly with an author, especially if you are generally in favor of publication and do not mind revealing your identity, this practice is prohibited because the other reviewer and the editor may have different opinions, and the author may be misled by having "cleared things up" with the reviewer who contacted him/her directly.

The manuscript sent to you for review is a privileged document. Please protect it from any form of exploitation. Do not cite a manuscript or refer to the work it describes before it has been published and do not use the information that it contains for the advancement of your own research or in discussions with colleagues.

In your comments intended for the author, do not make statements about the acceptability of a paper (see the next paragraph); suggested revisions should be stated as such and not expressed as conditions of acceptance. Organize your typed review so that an introductory paragraph summarizes the major findings of the article, gives your overall impression of the paper, and highlights the major shortcomings. This paragraph should be followed by specific, numbered comments, which, if appropriate, may be subdivided into major and minor points. (The numbering facilitates both the editor's letter to the author and evaluation of the author's rebuttal.) Criticism should be presented dispassionately; offensive remarks are not acceptable.

Confidential remarks directed to the editor should be typed (or handwritten) on the appropriate review form. Advise the editor of your recommendation for acceptance, modification, or rejection by checking the review form at the appropriate place. The final decision regarding modification, acceptance, or rejection of a manuscript rests solely with the editor, so do not state your recommendation in the portion of the review that will be sent to the author.

After completing your review, transmit your comments via mail, fax, or e-mail to the editor. If so requested by the editor, return the original manuscript, including illustrations, to the editor in the envelope provided; otherwise, destroy it.

It is recommended that you make a copy of the review for your files. The manuscript may be returned to you for a second review, particularly if the requested modification was extensive. In addition, if the manuscript is resubmitted after rejection, the new version may be sent to you for review. In either case, you will need to evaluate the author's responses to your original criticisms.',
bOpenAccess = '1',
chOpenAccess = 'This journal provides open access to all of it content on the principle that making research freely available to the public supports a greater global exchange of knowledge. Such access is associated with increased readership and increased citation of an author's work. For more information on this approach, see the Public Knowledge Project, which has designed this system to improve the scholarly and public quality of research, and which freely distributes the journal system as well as other software to support the open access publishing of scholarly resources.',
chSectionPolicies = '',
chPrivacyStatement = 'The names and email addresses entered in this journal site will be used exclusively for the stated purposes of this journal and will not be made available for any other purpose or to any other party.'

Is it something to do with the fact that there are single quotes (') in the text?

Posts: 12
Joined: Thu Jan 08, 2004 12:12 pm

Postby pjohanneson » Mon Jan 12, 2004 8:14 am


It is because I have ' characters in some of the text boxes. How do I escape these in PHP? (I know in ASP I'd just do
Code: Select all
replace([string], "'", "''")
I assume it's similar in PHP...)


Posts: 12
Joined: Thu Jan 08, 2004 12:12 pm

Postby pjohanneson » Mon Jan 12, 2004 10:03 am

ok, I found the addslashes() directive in the PHP manual, and that seems to make it work:
Code: Select all
$query = "update tbljournal set chFocusScope = '" . addslashes($chFocusScope) . "',
               nReviewersPerPaper = '" . addslashes($nReviewersPerPaper) . "',
               nReviewDueWeeks = '" . addslashes($nReviewDueWeeks) . "',
               chReviewProcess = '" . addslashes($chReviewProcess) . "',
               chReviewerGuideline = '" . addslashes($chReviewerGuideline) . "',
               bOpenAccess = '" . addslashes($bOpenAccess) . "',
               chOpenAccess = '" . addslashes($chOpenAccess) . "',
               chSectionPolicies = '" . addslashes($chSectionPolicies) . "',
               chPrivacyStatement = '" . addslashes($chPrivacyStatement) . "'";
Is there a more elegant way to do this (say, adding all the slashes on the form variables)?

Posts: 12
Joined: Thu Jan 08, 2004 12:12 pm


Postby jfenton » Tue Jan 13, 2004 4:59 pm

It appears that OJS relies on magic_quotes_gpc to be enabled. In my case I had disabled it because of another application on the same server that required it to be disabled, and that's when my users started reported errors like the one above.

My solution was to re-enable magic_quotes_gpc in php.ini and then selectively disable it for the other application in httpd.conf using statements like:

php_flag magic_quotes_gpc Off
php_flag magic_quotes_runtime Off
php_flag magic_quotes_sybase Off
Posts: 6
Joined: Tue Jan 13, 2004 4:53 pm
Location: Emory University Libraries

Postby pjohanneson » Wed Jan 14, 2004 7:55 am

re-enable magic_quotes_gpc in php.ini

Perfect, thanks. That fixed my problem. Much appreciated.

Posts: 12
Joined: Thu Jan 08, 2004 12:12 pm

Return to OJS Editorial Support and Discussion

Who is online

Users browsing this forum: No registered users and 2 guests