Dev {Tricks}

You are here: Home / Archives for OJS / Installation

by

OJS journal Checklist

Journal Identity

  • Journal title *Required
  • Journal initials *Required
  • Journal Abbreviation

Publishing Details
These details may be included in metadata provided to third-party archival bodies.

  • Publisher
  • Online ISSN
  • Print ISSN

Key Information
Provide a short description of your journal and identify editors, managing directors and other members of your editorial team.

  • Journal Summary
  • Editorial Team

Description
Include any information about your journal which may be of interest to readers, authors or reviewers. This could include your open access policy, the focus and scope of the journal, copyright notice, sponsorship disclosure, history of the journal, a privacy statement, and inclusion in any LOCKSS or CLOCKSS archival system.

  • About the Journal

Contact

Principal Contact
Enter contact details, typically for a principal editorship, managing editorship, or administrative staff position, which can be displayed on your publicly accessible website.

  • Name *Required
  • Email *Required
  • Phone
  • Affiliation
  • Mailing Address *Required

Technical Support Contact
A contact person who can assist editors, authors and reviewers with any problems they have submitting, editing, reviewing or publishing material.

  • Name *Required
  • Email *Required
  • Phone

Website Settings

  • Logo
  • Favicon
  • Journal thumbnail
    A small logo or representation of the journal that can be used in lists of journals.
  • Homepage Image
    Upload an image to display prominently on the homepage.
  • Additional Content
    Anything entered here will appear on your homepage.
  • Page Footer
    Enter any images, text or HTML code that you’d like to appear at the bottom of your website.
  • Sidebar

 

 

by

How to increase memory limit?

  • Fatal error: Allowed memory size of 123456 bytes exhausted (tried to allocate 234567 bytes) in /path/file.php

Usually your php.ini will be located at (XX – PHP version, for example 73):

vi /usr/local/php73/lib/php.ini

or use below trick to find your php.ini would be to ask php itself what it’s using, eg:

/usr/local/bin/php --ini | grep 'Loaded Configuration File'

or another trick to find php.ini

php -i | grep "php.ini"

Now open the php.ini file and edit memory_limit to a higher value.

memory_limit = 8M      ; Maximum amount of memory a script may consume (8MB)

Save, and then restart apache.

systemctl start httpd.service

CentOS/RHEL (Red Hat) Linux version 7.x or newer specific commands

or

sudo systemctl restart httpd.service

Alternative way: php.ini per folder

Location of the global server php.ini file is

/usr/local/php/php.ini

Location of the global per account php.ini file is

/home/USERNAME/php.ini

You can also have per folder changes, example:

/home/USERNAME/public_html/website1.com/php.ini
/home/USERNAME/public_html/website2.com/php.ini
/home/USERNAME/public_html/website2.com/myapp/php.ini

How to test php.ini changes?
Simple create phpinfo.php file in the users public_html folder and add the following content in it.

Example location: /home/USERNAME/public_html/phpinfo.php

<?php
phpinfo();
?>

Now open url in your browser (Apache restart is NOT needed):

http://your-domain.com/phpinfo.php

PHP.ini values

http://php.net/manual/en/ini.list.php

 

by

The tar command is not available | DirectAdmin

Problem:

  • The tar command is not available. Please correctly configure it in your “config.inc.php”.

There are two possible solutions of the above problem, your path to Tar tool is not correct, or the system can’t access to the path. In my case, I have both problems, so:

Solution One: Fixing the path of Tar

Open your terminal

Type which tar or whereis tar

which tar

or

whereis tar

Then use the path it returns in config.inc.php. For example,

tar = /usr/bin/tar

Still receiving the same error message, follow the second step.

Solution Two:

  1. Login to DirectAdmin admin panel.
  2. Go to “Server Manager > PHP Configuration (or PHP Settings). Select the domain you want to modify and
  3. Select the option “Disable Open Basedir”

Still getting error? Follow next step.

Solution Three:

You may get one of the following issues.

  • The “exec” PHP function has been disabled on your server. Contact your system administrator to enable it.
  • The uploaded plugin archive does not contain a folder that corresponds to the plugin name.

To fix the problems, you have to enable exec() function by deleting from the disable_functions

Go to link How to enable exec()

by Leave a Comment

Deprecated: Non-static method | Application::getName() | VersionCheck::getCurrentCodeVersion() | PKPRequest::getUserVar() | PKPRequest::_checkThis()

OJS Installation

Deprecated: Non-static method Application::getName() should not be called statically, assuming $this from incompatible context in /home/bdtopten/public_html/ojs/ojs3modern1/lib/pkp/classes/install/form/InstallForm.inc.php on line 149

Deprecated: Non-static method Application::getName() should not be called statically, assuming $this from incompatible context in /home/bdtopten/public_html/ojs/ojs3modern1/lib/pkp/classes/install/form/InstallForm.inc.php on line 151

Deprecated: Non-static method Application::getName() should not be called statically, assuming $this from incompatible context in /home/bdtopten/public_html/ojs/ojs3modern1/lib/pkp/classes/install/form/InstallForm.inc.php on line 153

Deprecated: Non-static method VersionCheck::getCurrentCodeVersion() should not be called statically, assuming $this from incompatible context in /home/bdtopten/public_html/ojs/ojs3modern1/lib/pkp/classes/install/form/MaintenanceForm.inc.php on line 37

Deprecated: Non-static method PKPRequest::getUserVar() should not be called statically, assuming $this from incompatible context in /home/bdtopten/public_html/ojs/ojs3modern1/lib/pkp/classes/form/Form.inc.php on line 369

Deprecated: Non-static method PKPRequest::_checkThis() should not be called statically, assuming $this from incompatible context in /home/bdtopten/public_html/ojs/ojs3modern1/lib/pkp/classes/core/PKPRequest.inc.php on line 592

 

These are warnings, not errors, and are cosmetic if you found the errors in error log. You should be able to ignore these and can continue installation.