What exactly do you mean with “Header of website” ?
Best,
Bozana
Hi @bozana,
I use OJS 3.1.1 and get the reference tab for editors.
Can you elaborate about this reference tab or direct me to pages where the details of this reference tab is available?
Hi @anupent
Currently it is only for the references to be parsed (line-by-line), then each reference saved, and then displayed on the article view page. This is the very first step toward Crossref reference linking, that will come in one of the next OJS releases, together with the new Crossref deposit API integration. Then the references will be added to the Crossref DOI registration XML, and the user will have the possibility to check if a DOI is found for article references by Crossref. If a DOI is found it will be retrieved from Crossref and saved in OJS DB and can then be displayed together with the references on the article view page.
Best,
Bozana
1 Like
Dear @bozana,
I have got the same problem as mentioned above. Fresh installation of OJS 3.1.1. but Reference box is missing. I cleared the cash, unchecked and checked the box for reference…
Any other idea or …?
Thanks
Lazar
Hi! @Lazar_Stosic
In my case reference box was missing if making submission through journal manager/editor role. But its working if submit with author role. Try to submit with different account having author role.
Hi all,
The fix is coming with this GitHub Issue: enable manager roles to add references during a submission · Issue #3750 · pkp/pkp-lib · GitHub and next OJS release 3.1.1-1…
Best,
Bozana
@asmecher @bozana
I have upgraded my OJS version. Now I am facing an issue. If I set
connection_charset =
database_charset =
charset_normalization =
these three settings to off the special characters don’t appear but when we go to any article and click on Add Reviewer nothing shows.
However when I set these three
connection_charset =
database_charset =
charset_normalization =
to Utf8 Add Reviewer starts working but special characters appears in reference.
I have attached screenshot too.
Hi @Haroon_Sattar,
Your post doesn’t show the settings you’re using. Can you double-check? Please include both the settings you’re using now, and the settings from your old OJS version.
Also please check your PHP error log to see if anything relevant appears there.
Thanks,
Alec Smecher
Public Knowledge Project Team
these were my old settings
client_charset = utf-8
connection_charset =off
database_charset =off
charset_normalization =off
Everything was working perfectly fine, but after update the above mentioned error arises.
Error Log
[05-Sep-2018 22:07:36 UTC] PHP Strict Standards: Declaration of ReviewerForm::fetch() should be compatible with Form::fetch($request, $template = NULL, $display = false) in /home/ppsorg/pjp.pps.org.pk/lib/pkp/controllers/grid/users/reviewer/form/ReviewerForm.inc.php on line 19
[05-Sep-2018 22:07:36 UTC] PHP Strict Standards: Declaration of ReviewerForm::initData() should be compatible with Form::initData() in /home/ppsorg/pjp.pps.org.pk/lib/pkp/controllers/grid/users/reviewer/form/ReviewerForm.inc.php on line 19
[05-Sep-2018 22:07:36 UTC] PHP Strict Standards: Declaration of ReviewerForm::execute() should be compatible with Form::execute() in /home/ppsorg/pjp.pps.org.pk/lib/pkp/controllers/grid/users/reviewer/form/ReviewerForm.inc.php on line 19
[05-Sep-2018 22:07:36 UTC] PHP Deprecated: Non-static method PKPRequest::getUserVar() should not be called statically, assuming $this from incompatible context in /home/ppsorg/pjp.pps.org.pk/lib/pkp/classes/form/Form.inc.php on line 369
[05-Sep-2018 22:07:36 UTC] PHP Deprecated: Non-static method PKPRequest::_checkThis() should not be called statically, assuming $this from incompatible context in /home/ppsorg/pjp.pps.org.pk/lib/pkp/classes/core/PKPRequest.inc.php on line 592
Hi @Haroon_Sattar,
The ideal settings are
client_charset = utf-8
connection_charset = utf8
database_charset = utf8
However, if your database is not currently properly encoded, you may need to transcode it using mysqldump and something like iconv or ftfy. Be especially careful not to introduce another encoding into your data, e.g. by configuring it to something that doesn’t match your data and accepting new submissions for a while – that would be very difficult to disentangle.
Regards,
Alec Smecher
Public Knowledge Project Team