Dev {Tricks}

You are here: Home / Home

by

Server error (Internal Server Error) | Roundcube | CWP

  • Roundcube 500 internal server error cwp
  • Server error (Internal Server Error)

Solutions:

Check /var/vmail/* permission

drwx------ 4 vmail mail 34 ene 16 14:01 domain.tld

Or try update roundcube

sh /scripts/mail_roundcube_update

 

 

by

Show DOI on Journal Homepage | OJS

Open the file IssueHandler.inc.php at pages/issue/IssueHandler.inc.php and under the function “$showToc” (search and find) add the following code.

$pubIdPlugins = PluginRegistry::loadCategory('pubIds', true);
$templateMgr->assign('pubIdPlugins', $pubIdPlugins);

Now add DOI code to the article_summary.tpl

{* DOI (requires plugin) *} {* CCDN *}
{foreach from=$pubIdPlugins item=pubIdPlugin}
{if $pubIdPlugin->getPubIdType() != 'doi'}
{continue}
{/if}
{assign var=pubId value=$article->getStoredPubId($pubIdPlugin->getPubIdType())}
{if $pubId}
{assign var="doiUrl" value=$pubIdPlugin->getResolvingURL($currentJournal->getId(), $pubId)|escape}
<div class="itemdoi">
<span class="doilabel"> <img src="https://demo.codexcafe.net/ojs3/plugins/themes/ajsrp/img/doi_logo.jpg" width="20">
{capture assign=translatedDOI}{translate key="plugins.pubIds.doi.readerDisplayName"}{/capture}
{translate key="semicolon" label=$translatedDOI}
</span>
<span class="doivalue">
<a {if $journal}href="{url journal=$journal->getPath() page="article" op="view" path=$articlePath}"{else}href="{url page="article" op="view" path=$articlePath}"{/if}>
{$pubId}
</a>
</span>
</div>
{/if}
{/foreach}

That’s all!

 

 

by

How to change the SSH port 22

How to change the SSH port

  • Log in to your server using the current SSH port (default 22).
    Note that you should not close this SSH connection until you have verified that you can access SSH on the new port number.
  • Open / etc/ssh/sshd_config
vi /etc/ssh/sshd_config
  • Set your Port. For example 1234
Port 1234
  • Restart SSHD
/scripts/restartsrv_sshd

or

sudo systemctl restart ssh.service
  • Configure any firewalls with the new SSH port.
  • Test SSH with new port 1234
ssh USER@HOSTNAME -p1234

Use your USER and HOSTNAME and the password and confirm new port.

If the SSH test on the new port is successful you can close the connection. If it is not successful, this SSH connection should not be closed until the SSH test on the new port is successful. Else revert the port to previous state and restart.

find / -name “sshd_config” -print

/usr/share/openssh/sshd_config
/etc/ssh/sshd_config

find / -name “sshd_config” 2>/dev/null

vi /usr/share/openssh/sshd_config

vi /etc/nftables.conf

ufw allow 1234/tcp

vi /etc/services

systemctl restart ssh

service ssh restart

systemctl restart ssh.service

ssh root@server_ip -p NEW_PORT
ssh root@123.512.11.6 -p 1234

 

 

by

Plum Analytics | PlumX Widgets | Technical Overview | Widget Script & Placeholder

  • Plum Analytics Artifact Widget plugin for OJS.
  • Plum Analytics plugin for PKP Open Journal Systems

PlumX integrates with Open Journal Systems (OJS), a journal management and publishing system that has been developed by the Public Knowledge Project through its federally funded efforts to expand and improve access to research.

PlumX customers with OJS-based journals get the following benefits:

  • Ingestion of article metadata into PlumX as new issues are published.
  • Easy implementation of PlumX widgets for display of Plum metrics on OJS article pages.
  • Tracking of PlumX metrics for all articles across all five metrics categories.

GitHub ulsdevteam / ojs-plum-plugin

This plugin provides display of PlumX Metrics from Plum Analytics on the article level for PKP Open Journal Systems.

https://github.com/ulsdevteam/ojs-plum-plugin

Manual Integration without plugin

PlumX Widgets at https://plu.mx/developers/widgets/

 

 

by

How google scholar works | OJS

  • how google scholar works
  • how google scholar citations works
  • google scholar citations
  • google scholar indexing
  • How do I get indexed by Google Scholar?

Google Scholar crawls and indexes scholarly publications. You need not register your journal with Google Scholar. It will automatically crawl your website. It identifies scholarly content and determines each item’s bibliographic metadata.

If you notice that your journal is not appearing in Google Scholar, there may be some issues that need to be addressed.

Google Scholar relies on two key pieces of information in order to do its indexing:

  1. A way to crawl all the URLs or essentially links for articles, either via a crawler-friendly browse (set up by default for OJS instances), or a sitemap.
  2. Bibliographic information from articles in the form of metatags. These metatags are derived from the information you add to the forms in OJS to describe your journal, issues, and submissions.

Some common indexing problems

  • Incorrect publication dates listed in metatags
  • Mixing up multiple languages or scripts in metatags
  • Language of metadata (especially title and abstract) in different language than the language of the article full text
  • Author name formatting discrepancies between metadata and galley (e.g. Given Name and Family Name format and capitalization).
  • Authors listed in a different order in metatags than the author order in the gallery

Fixation suggestion

  • Check publication date consistency
  • Match the publication date of the issue, as well as the publication date listed on the article PDF. Inspect citation date.
  • Use only one language in each metadata tag, and don’t reproduce duplicate metadata in different languages/scripts across multiple metatags
  • Use the full-text language in the metadata tags
  • Adding multilingual metadata in OJS 3.2
  • Ensure that authors’ names are formatted consistently