SOLVED: Upgrading to php 7 wp-rss-multi-importer/inc/excerpt_functions.php on line 570

SOLVED: Upgrading to php 7 wp-rss-multi-importer/inc/excerpt_functions.php on line 570

I recently got an email from an old client because one of plugins was giving them an error and stopped working breaking their site. After taking a quick look I determined the issue was due to php depreciation.

Below is the error they were receiving:

  wp-content/plugins/wp-rss-multi-importer/inc/excerpt_functions.php on line 570

How to fix this:

I fixed it for me the following way:
1) Go to /wp-content/plugins/wp-rss-multi-importer/
2) Open editor on excerpt_functions.php
3) Go to line 570
4) Change first occurrence of $thisLink to $thisLink1 (you are only adding a number at the end)

wp-content/plugins/wp-rss-multi-importer/inc/excerpt_functions.php on line 570
wp-content/plugins/wp-rss-multi-importer/inc/excerpt_functions.php on line 570

After the change is done and saved, make sure you activate the plugin and everything should come back to normal. The feed will show the original content as it was before.

Any questions let me know on the comment below.

What’s New in WordPress 5.1?

Inspired by Archie Bell & The Drells, WordPress’s theme for 2019 is to “tighten up”, and WordPress 5.1 focussed on exactly that.
With security and speed in mind, this release introduces WordPress’s first Site Healthfeatures. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.
Furthermore, when installing new plugins, WordPress’s Site Health features will check whether a plugin requires a version of PHP incompatible with your site. If so, WordPress will prevent you from installing that plugin.
The new block editor has kept improving since its introduction in WordPress 5.0. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother. There are more features and performance improvements planned in upcoming WordPress releases, you can check them out in the Gutenberg plugin.

WordPress 5.1 is now released

The first release candidate for WordPress 5.1 is now available!
This is an important milestone, as the release date for WordPress 5.1 draws near. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.1 is scheduled to be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time!
There are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).

How to fix WordPress “500 Internal Server error” page

How to fix WordPress "500 Internal Server error" page
How to fix WordPress “500 Internal Server error” 

You maybe getting this error page due to a server issue rather than WordPress configuration. So do not change or delete anything in your WordPress yet as it may not be related to your WP installation at all.

In order to solve this issue lets first look at what the “500 Errors” actually mean. Basically the 500 Internal Server Error is quite a common HTTP status code that indicates something is not working properly on the web-site’s server but the server itself could not tell you what the exact problem is. The WordPress 500 internal server error its just like any other web page that shows up in your browser window.

Now that we know know what the “500 Internal Server Error” is we can look at WordPress in relation to this error.

1. Try deleting your .htaccess as your permalinks might not work, but you’ll at least know whether this is being caused by an error in htaccess.

2. I deletion of .htaccess did not work the re-upload it and add the following:
SecFilterEngine Off
SecFilterScanPOST Off

3. Increase the server memory in php.ini file for example from 64m to 128m

4. If you have changed the prefix of your MySQL database tables manually this can also affect it so revert back to your previous tables.

5. If you have just moved to another server/hosting and your php version is old try adding this to your .htaccess file: AddType x-mapp-php5 .php

6. Disable your brower-cache then quit tour browser then open it again and see what happens. This one is pretty straight forward.

7. Check your file permissions as some server will behave better if you set your permissions to chmod 777 instead of chmod 755 – as strange as it sounds.

8. Some people have had issues with GoDaddy WP-Cache plugin so my suggestion is to remove WP-Cache and install another plugin like WP-SuperCache or Hyper Cache.

Solution to error “wp-includes template-loader.php on line ..”

Ever gotten this type of error ?
wp-includes template-loader.php on line 26 or 43

Regardless of the number after the “on line” its a very common issue with WordPress due to template or plugin installations.

Here are some simple solutions to this error:

Firstly, deactivate all of your active/inactive plugins (and yes, all) just temporarily to narrow down the issue list. After having done this and the error goes away, re-activate them individually (one-by-one) to find the buggy plugin(s). If you are not able to login into your admin dashboard, try re-setting the plugins folder with your favorite FTP client or phpMyAdmin. Every now and then, an allegedly inactive plugin can still cause errors-problems because the php hooks remain unless plugins have been completely uninstalled/removed or some plugins hang around in cached folder. So when you rename the plugin the folder, you break them and force them to become inactive). If applicable, also remember to deactivate any other plugins in the old-plugins folder. Probably, the easiest and simplest way is to rename that folder to inactive-plugins-old, however its totally up to you the name as it wont make any difference.

Secondly, switching to the un-changed default theme (e.g Twenty Eleven template) for a moment by renaming your current theme’s folder in wp-content/themes. The idea is to force WordPress to go back to the default theme to exclude any theme-related issue. This basically check to see if anything is wrong with your custom theme. If you still don’t have access to your admin dashboard, then access your server via FTP or shell connection or whatever file management application your hosting company provides.

Third, if the above troubleshooting steps have been exhausted and do not resolve the issue, try manually re-uploading all files and folders EXCEPT the wp-config.php file and the /wp-content/ directory from a fresh download of WordPress. This method will replace your core files without changing your content and settings in wp-config.php file and the /wp-content/ directory. Note – make sure you do not overwrite the highlighted files as that will misconfigure the database settings and it will create more work than needed.
If all fail then feel free to contact us to do this for you !