Resources, Articles, Tricks, and Solutions in connection to WordPress

WordPress error Class wp_theme not found - Fix it now

This article covers method to resolve 'WordPress: Class wp_theme not found' error for our customers.


To perform a manual WordPress upgrade:

1. Get the latest WordPress zip (or tar.gz) file.

2. Unpack the zip file that you downloaded.

3. Deactivate plugins.

4. Delete the old wp-includes and wp-admin directories on your web host (through your FTP or shell access).

5. Using FTP or your shell access, upload the new wp-includes and wp-admin directories to your web host, overwriting old files.

6. Upload the individual files from the new wp-content folder to your existing wp-content folder, overwriting existing files. Do NOT delete your existing wp-content folder. Do NOT delete any files or folders in your existing wp-content directory (except for the one being overwritten by new files).

7. Upload all new loose files from the root directory of the new version to your existing WordPress root directory.

However, if you did not perform step 7, you would see this error message when trying to complete your upgrade:

Class WP_Theme not found in theme.php on line 106


Hence, to avoid this issue, or to fix this issue, make sure you perform step 7 and continue on the remaining steps for the manual WordPress updating process.

Read More


WordPress 405 Method Not Allowed Error - Fix it now

This article covers different methods to troubleshoot 405 Method Not Allowed Error on WordPress.

The 405 Method Not Allowed WordPress error occurs when the web server is configured in a way that does not allow you to perform a specific action for a particular URL. 

It's an HTTP response status code that indicates that the request method is known by the server but is not supported by the target resource.


To Fix 405 Method Not Allowed Errors:

1. Comb through your website's code to find bugs.

If there's a mistake in your website's code, your web server might not be able to correctly answer requests from a content delivery network. Comb through your code to find bugs or copy your code into a development machine. 


2. Sift through your server-side logs.

There are two types of server-side logs -- applications logs and server logs. Application logs recount your website's entire history, like the web pages requested by visitors and which servers it connected to.


3. Check your server configuration files.

The last way to find out what's causing your 405 Method Not Allowed Error is by taking a look at your web server's configuration files.

Read More


The WordPress Missed Schedule post Error - Methods to fix it

This article covers how to easily fix the missed schedule post error in WordPress. WordPress scheduled posts not publishing can be resolved by using a plugin such as "WordPress cron jobs" to help trigger scheduled posts to publish your WordPress Post.

Cron is a technical term for commands that run on a scheduled time, like your scheduled posts in WordPress.

Technically, a real cron job will run at the server level. But because WordPress doesn't have access to that level, it runs a simulated cron.

These simulated cron jobs, like scheduled posts, are supposed to be triggered whenever a person or bot visits your site. 

But because it's not a real cron job, sometimes it causes a missed schedule error.


TO FIX THE MISSED SCHEDULE ERROR IN WORDPRESS:

Every fifteen minutes the post scheduler plugin checks for posts that have the missed schedule error, and will automatically publish them for you.

Multiple techniques for checking your site's missed posts are used to make sure a scheduled post is not missed.


Methods to fix the WordPress missed schedule error:

1. Use the Scheduled Post Trigger plugin.

2. Manage cron jobs directly through your server.

Read More


WordPress 401 error - Fix it now

This article covers easy to follow methods to resolve WordPress 401 error. 

The 401 error has multiple names including Error 401 and 401 unauthorized error. 

These errors are sometimes accompanied by a message ‘Access is denied due to invalid credentials’ or ‘Authorization required’.


To fix the 401 error in WordPress:

1. Temporarily Remove Password Protection on WordPress Admin

2. Clear Firewall Cache to Solve 401 Error in WordPress

3. Deactivate All WordPress Plugins

4. Switch to a Default WordPress Theme

5. Reset WordPress Password

Read More


Genericons XSS Vulnerability - How to Protect your WordPress Site

The article covers Genericons #XSS Vulnerability and saw how to protect the WordPress Site from it. 

The Genericons package includes a file called example.html which has been found to be vulnerable to a DOM-based XSS #vulnerability. 

This package is included in various WordPress plugins and themes.

You can fix this issue by trying to Remove the example.html file located in the genericons directory.


The recommended way to patch your system is simply to upgrade WordPress. 

This will not only secure your system against this vulnerability, but also any other issues that may have been fixed.

If your permissions allow it, you can usually upgrade your installation using the admin panel update controls.

Although we highly recommend that you update WordPress completely (along with any affected themes or plugins), you can also easily manually delete the offending files.


To do so, log into your WordPress server and navigate to your document root directory.

You can remove the offending files by typing:

sudo find . -path "*/genericons/example.html" -exec rm -f {} \;

You can then check your directory structure again:

find . -path "*/genericons/example.html"

 All of the example.html instances within a genericons directory should be removed.


#Genericons includes a file called example.html which has been found to be vulnerable to attack from the Document Object Model level. 

Any WordPress plugin or theme that includes this file is open to an attack. 


To help combat this, we have done the following for VaultPress users:

1. We've deleted the file everywhere we can to proactively secure your site.

2. We've added it to our security scanner so that if there are any cases where we couldn't detect the file or couldn't delete it, you will still be notified if the file exists on your site. 

3. For users with sites where we couldn’t remove the file, we have personally emailed each of you with steps to remove the file and details about where the file is located.


Also, another important security update was released today for #WordPress in Version 4.2.2. Version 4.2.2 fixes several vulnerabilities that could allow users to compromise your site including the Genericons vulnerability.

Read More


WordPress error This site ahead contains harmful programs

This article will guide you on how to tackle this site ahead contains harmful programs error in #WordPress. 

To remove the #deceptive #site notice, you'll have to first remove the malware on your site. 

Then, submit a review request at Google Search Console to delete the notice. In 1-3 days, Google will update the status and remove the deceptive site warning.

You can check Google's Transparency Report to see if a website is blacklisted due to a Copyright or DMCA claim. 

You can also use Google's #Safe #Browsing Site Status tool.

To fix website that is NOT safe for browsing:

1. Scan your own computer with antivirus and malware detection software and remove all threats.

2. Change passwords to your hosting account (cPanel , plesk, webmin etc.)

3. Change FTP passwords.

4. Verify that your website is infected and remove malicious code.

Read More