Dev {Tricks}

You are here: Home / Archives for dev

by

How to Install cPanel/WHM on Ubuntu 20.04

  • How to Install cPanel/WHM on Ubuntu 20.04
  • How to Install cPanel/WHM on Ubuntu 20.04
  • System Requirements for Ubuntu | cPanel & WHM
  • How to install WHM & CPanel on Ubuntu 20.04 LTS Linux

Step 1

Login as root user to SSH of freshly installed Ubuntu 20.04

Step 2

Disable firewall, while installing cpanel & whm on linux ubuntu system

iptables-save > ~/firewall.rules
systemctl stop firewalld.service
systemctl disable firewalld.service

Step 3

Update Ubuntu System Packages

apt update
apt upgrade

Step 5

Set your hostname for example my.hostname.com

set hostname my.hostname.com
edit hostname

vi /etc/hosts
vi /etc/hostname

Reboot the server.

Step 6

Create a shell session of Linux Screen utility. It helps to remain active even after the network disruption.

screen

If the screen is not installed, install it.

apt install screen

Step 7 – Install Cpanel/WHM

cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest

Step 5 – Login to WHM Web interface

https://SERVER_IP:2087

Use your root login credentials.

That’s All!

by

MySQL: Error Code: 1118

  • #1118 – Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.
  • Change limit for “Mysql Row size too large”
  • Row size too large 8126 Changing some columns
  • 1118 Row size too large

The error was: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

  • Solution
  • Login to phpMyAdmin with root previllege
  • Go to Variables
  • Then edit Innodb Strict Mode as follows 
    innodb_strict_mode = 0

 

by

Install office 365 with free lifetime license

Create a Microsoft developer account and join Microsoft 365 Developer Program.

1. Search “Microsoft Developer”
2. Go to “Microsoft 365 Dev Center”
3. Join “Join the Microsoft 365 Developer Program today!”
4. Sign up or if you have account “Sign in”
5. Now fill up the form for “Join the Microsoft 365 Developer Program today!”
6. What is your primary focus as a developer? (Choose only one)
– Custom solution for my own customers
7. What areas of Microsoft 365 development are you interested in? ​We will show you resources, tools, and training to help you get started.
– Microsoft Team
8. Set up your Microsoft 365 E5 sandbox
– Configurable sandbox
9. Set up your Microsoft 365 E5 configurable sandbox
– Set username, domain and password and then continue.
10. Provide you mobile number and verify it.
11. After that you will get “Your Microsoft 365 developer subscriptions” page. Click on “Go to subscription”
12. You will be prompted for login with the just created password.
13. After login, you will get office.com page.
14. Now on this page, click on “Install apps” and then “Microsoft 365 apps”
15. A around 7MB file will be downloaded.
16. Install it .

 

https://support.microsoft.com/en-us/office/uninstall-office-from-a-pc-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8#officeversion=click-to-run_or_msi

by

Google Scholar Indexing | PKP Docs

Google Scholar, a popular scholarly indexing engine.  It crawls the web looking for scholarly publications such as articles, books, reports, theses, conference proceedings, pre-prints, among others.

Google scholar

  • Identifies scholarly content
  • Determines each item’s bibliographic metadata, and
  • Groups different online versions of an item together with this (bibliographic) metadata in search results.

Note: There is no need to register your journal with Google Scholar. Google Scholar will eventually find and automatically crawl the site.

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

  1. Crawl all the URLs, – or essentially links, – or a sitemap.
  2. Bibliographic information from articles. This is in the form of machine-readable metadata tags (“metatags”).
    Bibliographic metatags indicate to Google Scholar the specific metadata for an article (e.g. title, author, publication date, etc.).

Inclusion Guidelines for Webmasters Google Scholar inclusion guidelines

Metatags example

<meta name="citation_title" content="16th Amendment Controversy between Legislature and Judiciary: An Analysis">
<meta name="citation_author" content="Mahdee Zubuair">
<meta name="citation_date" content="2022/06/30"> 
<meta name="citation_journal_title" content="Asian Journal of Humanity, Art and Literature">
<meta name="citation_volume" content="9">
<meta name="citation_issue" content="1">
<meta name="citation_firstpage" content="9">
<meta name="citation_lastpage" content="18">
<meta name="citation_pdf_url" content="https://i-proclaim.my/journals/index.php/ajhal/article/download/635/590">

The <meta name="citation_pdf_url"/> provides a direct URL to the article galley, and tells the indexing system which file to associate with this metadata.

If you notice that your journal(s) are not appearing in Google Scholar, there may be some issues that need to be addressed, see the common OJS indexing problems and suggested fixes below.

Troubleshooting for Journal Managers and Editors

It could be due to inconsistencies between the journal’s metadata and the Galley files (PDF, HTML, XML etc).
Metadata in the Tags & Galley should match precisely.

Some common discrepancies include:

  • Incorrect publication dates listed in metatags, issue data and gallery files.
  • Mixing up multiple languages or scripts in metatags and gallery files.
  • 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 (PDF, HTML, XML etc)

Note that any changes will not be reflected until Google Scholar makes changes to its’ index which occurs twice yearly.

  • Check for consistency in the publication date
  • Use only one language in each metadata tag, and don’t reproduce duplicate metadata for different languages. Instead use translated version.
  • Use the full-text language in the metadata tags
  • Ensure that authors’ names are formatted consistently

Troubleshooting for Site Administrators

Google Scholar will stop indexing a journal if:

  • There are high numbers of metadata errors
  • The metatags are missing entirely
  • The HTTPS certificate is invalid or expired
  • There are frequent site downtimes
  • The OJS site has been hacked

Best practices for OJS journal indexing

  • Avoid customized URL structures
  • Set up article-level redirects
  • Improve SEO

Please contact for OJS management and support

OJS Expert