Thomas@iThemes

I’m not sure if this is what’s causing your issue with those features, but if you examine your site with a web browser’s developers tools (https://www.ads-software.com/support/article/using-your-browser-to-diagnose-javascript-errors/). You’ll see that the site is serving mixed content. In other words, the site us using SSL (HTTPS), but is trying to serve static files via HTTP (non SSL).

You might be able to fix those mixed content issues with a plugin:
https://www.ads-software.com/plugins/ssl-insecure-content-fixer/

And you can read more about mixed content issues here:
https://www.wpkube.com/how-to-fix-insecure-content-mixed-content-error-in-wordpress/

It depends on if your WordPress site is Gutenberg or the “Classic” editor. Before Gutenberg, there were plenty of plugins that you could try:
https://www.ads-software.com/plugins/search/nofollow/

But if you’re using Gutenberg, and can’t find a compatible plugin, you may have to do it manually:
https://www.wpbeginner.com/beginners-guide/how-to-add-nofollow-links-in-wordpress/

I just tried navigating to different areas in your site, and I kept getting redirected to the home page. If that still happened with all plugins deactivated, did you check with your theme support? As it’s possible that your theme is causing that. You might also want to check your .htaccess file in case it has any directives that might be causing that (simple thing to try would be to temporarily rename the .htaccess file to something like .htaccess.bak).

I know you said you were looking at something in regards to recent posts, but in the past, most WordPress users prefer that it display related posts instead. And for that, YARPP has been around forever:
https://www.ads-software.com/plugins/yet-another-related-posts-plugin/

Just something else that you might want to consider.

Actually that has known to happen quite often. You might see if this link helps:
https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-http-image-upload-error-in-wordpress/

The most straight forward thing to do would be to install a member’s plugin and possibly create a user role for the selected members who would have access to certain pages, etc.

Though depending on the specifics that you require, it may take more than one plugin to get the job done for you:
https://www.ads-software.com/plugins/members/

Something else to consider if none of the other replies help, is that there could be a plugin/theme conflict. Especially if the front of the site works fine.

Since you cannot access the dashboard to check for a plugin/theme conflict, you’ll have to use FTP/SFTP or some similar host provided File Manager:
https://www.webhostinghero.com/disable-wordpress-plugins-when-site-crashes/

If that doesn’t help, please try temporarily renaming/removing any server configuration files like .htaccess, php.ini, .user.ini, etc.

Finally, please check to see if there are any hardcoded/custom URLs in the wp-config.php file or theme files still pointing to the source site’s location that needs updated:
https://codex.www.ads-software.com/Changing_The_Site_URL#Changing_the_Site_URL

That parse error, unexpected T_OBJECT_OPERATOR is usually due to the server/site using an older version of PHP. The first thing you’ll want to check is to see which version of PHP the site/server is utilizing. You’ll want to make sure it’s using at least PHP 5.6. As I believe WordPress still supports (works with) at least 5.6.20+
https://www.ads-software.com/about/requirements/

You’ll need to use a plugin like the following:
https://www.ads-software.com/plugins/frontend-reset-password/

If your WordPress install is in a /blog/ directory, my guess is that there are some web.config directives redirecting/forcing WordPress back to the URL instead of the correct one. Unfortunately I’m not that familiar with Windows/Microsoft web servers, but I did find this link:
https://cypressnorth.com/web-programming-and-development/setting-up-url-rewrites-for-wordpress-under-iis-on-a-windows-server/

As you’ll want to see if you can override the default web.config directives with .htaccess in the WordPress site’s web-root directory.

Sounds like a plugin/theme conflict. But if the site has a lot of visitors/users along with a lot of plugins/themes, it might be difficult to troubleshoot that on a live site.

My suggestion would be to first install this plugin:
https://www.ads-software.com/plugins/health-check/

That plugin is written by the WordPress community and some of it is actually in WordPress core now. And I believe it should be compatible with WordPress Multisite, but unfortunately I haven’t tested it with Multisite yet.

What it allows you to do is to disable all plugins/themes and troubleshoot your issue without it affecting anyone else using/visiting the site.

Only thing there is, you would want to create a new user with the same role as the interns and troubleshoot through that new user. Of course that new user will need to be able to activate/deactivate plugins. So that you can activate the “Health Check” plugin and use its troubleshooting options.

It looks like the site has enabled the disabling of the WordPress cron in the site’s wp-config.php file:
https://www.ads-software.com/support/article/editing-wp-config-php/#disable-cron-and-cron-timeout

You’ll want to either comment out the define, remove the define, or change the true value to false

It’s also possible that someone tried to add that define to a theme (or child theme) file. If that’s the case, you’ll probably want to remove it from the file. As that define was only meant to go in the site’s wp-config.php file.

Those are all normal.

.gz one is for the archived/zipped version. Supposedly that’s for speed. As it allows the sitemap to be delivered quicker to the bot (search engine or other). And it’s recommended that you have it.

The last one, the /feed/ one, is for your RSS feeds. By default, WordPress has an RSS feed for your posts.

But yes, and as far as I know, it’s best to leave them like that. (Though I’m not an SEO specialist. But most always have them like that.)

First thing to check would be to make sure that the emails are not going to your spam folder of your receiving email client.

If none are there, like many web applications, WordPress uses the PHP ()mail function to distribute email and, on a correctly configured server, the feature should work seamlessly without the need for user configuration. However, server hosts may place temporary or permanent restrictions on the use of PHP ()mail to reduce automated spam.

So you may want to contact your host, as they may have a specific guide on how it needs to be set up with their hosting.

I may be mistaken, but that looks like the BuddyPress toolbar. If so, you should be able to disable it by going to the BuddyPress -> Settings and uncheck the “Show the toolbar for logged out users”.