Thanks for your reply. I will make a fresh upgrade to check if the problem still exist and report here probably by tomorrow.
Error usageStats plugin after upgrading from OJS 3.1.0-1 to 3.1.1
Regarding the usage statistics graph: s. this GitHub Issue: https://github.com/pkp/pkp-lib/issues/3556. Please track that issue for the coming fix, that you would then need to apply
EDIT: this change is needed: https://github.com/pkp/pkp-lib/pull/3559/files
Article metrics problem in OJS 3.1.1
Appreciate your hard work and help. Above fix solved download statistic Issue.
Regarding reference box, I noticed that reference box appears properly when submit article with author role, However, if make a submission with journal manager/editor role reference box does not appear.
After upgrading OJS to 3.1 we are getting special characters at the end of references of previously added articles. Anyone knows the reason ?
- Fung E, Nemeth E. Manipulation of the hepcidin pathway for therapeutic purposes. Haematologica 2013;98(11):1667â€“76.
- Hintze KJ, McClung JP. Hepcidin: A Critical Regulator of Iron Metabolism during Hypoxia. Adv Hematol [Internet] 2011. ID 510304, 7 pages. Doi:10.1155/2011/510304…
- Kwapis J, Slomka A, Zekanowska E. Hepcidin and its Role in Iron Homeostasis. EJFICC 2009;20(2):124â€“8.
Its look like you changed following character_set_name in config.inc.php
Just check that above setting is same in your previous installation and upgrade installation before initiating upgrade process.
There are many threads in the forum to convert and fix utf8/utf-8 character_set, kindly find it if this is the issue.
Thank a lot ! @aabahishti It worked for me.
Can you please guide me how to add quick submit plugin in OJS 3.1 .
I think you should as admin user go to the Settings > Website > Plugins > Plugin Gallery and install the plugin from there.
@bozana I was able to install the plugin manually. Thanks a lot for your time.
Can you tell me how to change the styling of Header of website. ?
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?
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.
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 …?
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.
Thank you for answer. The problem was solved. Now everything work.
The fix is coming with this GitHub Issue: https://github.com/pkp/pkp-lib/issues/3750 and next OJS release 3.1.1-1…
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
to Utf8 Add Reviewer starts working but special characters appears in reference.
I have attached screenshot too.
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.
Public Knowledge Project Team
these were my old settings
client_charset = utf-8
Everything was working perfectly fine, but after update the above mentioned error arises.
[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
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.
Public Knowledge Project Team