WordPress Error: Call to undefined function curl_init() Ubuntu/Debian Server

Solving: Call to undefined function curl_init() in Debian/Ubuntu Hi, this is an easy Troubleshooting of the Call to undefined function curl_init() Issue for WordPress in Ubuntu/Debian GNU/Linux Servers. Usually this problem is caused by a Missing or Unachieved PHP cURL Setup! Installing PHP cURL Extension Now to Install PHP cURL Generally play: sudo apt install phpX.Y-curl php-curl And so for instance for the current PHP 7.4 it looks like: sudo apt install php7.4-curl php-curl Restarting Apache So then to Restart Apache Web Server It’s is important to Reload it just like with: sudo /etc/init.d/apache2 restart

Continue Reading

WordPress Publicizing Failed on Ubuntu/Debian Server Issue

Solving: WordPress Publicizing Failed in Debian/Ubuntu Hi, this is an easy Troubleshooting of the Post Publicizing Failed Issue for WordPress in Ubuntu/Debian GNU/Linux Servers. Usually this problem is caused by a Missing or Unachieved PHP cURL Setup! Installing PHP cURL Extension Now to Install PHP cURL Generally play: sudo apt install phpX.Y-curl php-curl And so for instance for the current PHP 7.4 it looks like: sudo apt install php7.4-curl php-curl Restarting Apache So then to Restart Apache Web Server It’s is important to Reload it just like this: sudo /etc/init.d/apache2 restart

Continue Reading

WordPress MySQL High CPU Usage Troubleshooting

Solving WordPress MySQL High CPU Usage Guide Hi, this Tutorial Shows You Step by step How to Debug WordPress MySQL High CPU Usage Issue. And usually this problem is caused by MySQL Slow Query coming from an installed Plugin. Fortunately, WordPress dispose of a formidable Plugin like the Query Monitor to find out the Cause. Especially relevant, in case the Issue is manifesting during a New Post/Page publication, instead see this Troubleshooting. 1. Installing Query Monitor Plugin How to Download and Install WordPress Query Monitor Plugin Get WordPress Query Monitor Plugin Query Monitor 2. Debugging MySQL Issue Then to Debug …

Continue Reading

GNU/Linux Yoast WP CLI Indexing Easy Guide

GNU/Linux Yoast WP CLI Indexing Guide Hi! The Tutorial Shows You Step-by-step How to Index a WordPress Website for Yoast SEO using the WP CLI. And to Yoast WP CLI Indexing your posts securely you have to make use of the www-data Non Login User. 1. Accessing www-data Shell Fist, you have to Access www-data Shell Simply with: sudo -u www-data sh 2. Indexing Posts Now to Index WordPress Posts with WP CLI Use: wp –path=’/var/www/[PATH2WPSITE]’ yoast index Replace [PATH2WPSITE] with your current one in the above Command. So for instance: wp –path=’/var/www/html/tutorialforlinux.com/wordpress’ yoast index

Continue Reading

WordPress Editor Remove p Tag Issue Solution

Solving WordPress Editor Remove p Tags Hi, this Tutorial Shows You Step by step How to Solve Editor Remove p Tag Issue on WordPress. And WordPress Editor Remove p Tag is due to the New Gutenberg Block Editor functionality. Finally, this Solution Do Not Need of Any Extra Plugin or Editor, but only of Knowlegde about the Default Editor Features. Switching to the Code Editor On the Top Right Choose ‘More Tools & Options’ Then Switch to Code Editor Finally Simply Wrap the HTML Code Inside a ‘wp:html‘ Comment Tag like: <!– wp:html –> YOUR HTML CONTENT <!– /wp:html –> …

Continue Reading

Solving:Midori Browser has detected that the server is redirecting the request for this address in a way that will never complete

WordPress Apache WebSite Wrong 80 to 443 Redirection Hi! This Tip Shows You How to Solve the “Midori Browser has detected that the server is redirecting the request for this address in a way that will never complete” Issue on a WordPress Apache Debian/Ubuntu GNU/Linux Server Setup. Possible Solution Check for a Double Redirection in the /etc/apache2/sites-availabe/[MYSITE].conf And also: [SERVERROOT]/.htaccess Try to Remove the Eventual: RewriteCond %{SERVER_PORT} ^80$ RewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R] In the .htaccess and See if this Solve the Issue 🙂

Continue Reading

Solving:Firefox Browser has detected that the server is redirecting the request for this address in a way that will never complete

WordPress Apache WebSite Wrong 80 to 443 Redirection Hi! This Tip Shows You How to Solve the “Firefox Browser has detected that the server is redirecting the request for this address in a way that will never complete” Issue on a WordPress Apache Debian/Ubuntu GNU/Linux Server Setup. Possible Solution Check for a Double Redirection in the /etc/apache2/sites-availabe/[MYSITE].conf And also: [SERVERROOT]/.htaccess Try to Remove the Eventual: RewriteCond %{SERVER_PORT} ^80$ RewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R] In the .htaccess and See if this Solve the Issue 🙂

Continue Reading