Ronnie55

@crubenstein11 I never figured it out, sorry.

Thanks for the response @threadi

I went to the URL and clicked “view page source” in Chrome. I don’t see the shortened/incorrect URL referenced anywhere. Just the full, correct URL mentioned a few times throughout the page source code.

Thanks, Jeff, for the work you’ve done on this, and for the fast reply. I’ll be downloading on Monday and leaving you a great review, too.

Quick update: I just read an article saying that Google is replacing H1 titles in search results now, as of 1-2 days ago:

https://www.searchenginejournal.com/google-is-rewriting-title-tags-in-serps/416793/#close

So I guess it’s not a plugin issue.

If the code snippet and order of items above looks fine, please just let me know and I’ll forget it ?? Thanks.

Thanks. This plugin certainly has a creator that gives fast replies to support questions. That’s a plus. Thanks, Jeff! ??

Thanks for the reply. Really appreciate it.

If it’s not too much trouble, I’m also a bit confused on Query Alteration Settings. (Search and Archive).

For example, is search query alteration only to exclude pages from showing up if people search within my own site? Through my internal search bar?

If so, I don’t need. I just wasn’t 100% clear on what these settings do.

• This reply was modified 3 years, 11 months ago by Ronnie55.

I just had this thought too. I don’t need pro but will probably buy anyway. Great plugin!

I had a similar experience yesterday after updating to the newest version. I’ve left Yoast and will never use this plugin again.

Right, I guess my question was: I didn’t think I had changed my permalink structure. Nothing has changed. That was my concern.

Thanks for the reply, though.

Hi,

Everything is 100% up to date. I’m using latest version of WP – 5.4.1, and all plugins including Yoast are up-to-date.

Note: Not sure if it matters but I’m using WP Classic Editor plugin because I hate Gutenburg. Screenshots below, from the post edit page. These are all areas where I think there used to be colors or icons or something?

https://ibb.co/6NW2WPn

https://ibb.co/88nhD3V

https://ibb.co/xmY1FMT

Yes. That’s the option I had used.

EDIT: I think it’s fixed. After reactivating, I deactivated again and it seems fine now. I think my host made some changes with their own settings this week, which may have caused a redirect loop or caching issue, or something.

It’s fine now.

Thanks for creating such a great plugin.

• This reply was modified 4 years, 10 months ago by Ronnie55.

Hi Rogier,

Thanks for the fast reply.

This error showed up for me AFTER updating to 3.2.2 today. Just to be clear.

I had no issues. Then I saw a new version available and updated to 3.2.2.

Then I got this error and notification from WordPress.

I just found this error log at the bottom of the automatically-generated email from WordPress informing me of the technical difficulty.

I removed my website name and folder names and replaced it with “xxxx”. But the rest is there.

I also see “multisite” mentioned. My site is a single site.

Wasn’t this latest version fixing something related to multisite vs. single site?

Error Details
=============
An error of type E_ERROR was caused in line 667 of the file /home/xxxxx/public_html/wp-content/plugins/really-simple-ssl/class-multisite.php. Error message: Uncaught Error: Call to undefined function get_blog_option() in /home/xxxxx/public_html/wp-content/plugins/really-simple-ssl/class-multisite.php:667
Stack trace:
#0 /home/xxxxx/public_html/wp-includes/class-wp-hook.php(286): rsssl_multisite->check_site_protocol(‘https://xxxx…’, ”, NULL, ‘/’)
#1 /home/xxxx/public_html/wp-includes/plugin.php(208): WP_Hook->apply_filters(‘https://xxxxx…’, Array)
#2 /home/xxxx/public_html/wp-includes/link-template.php(3126): apply_filters(‘home_url’, ‘https://xxxx…’, ”, NULL, ‘/’)
#3 /home/xxxx/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher.php(150): get_home_url(‘/’)
#4 /home/xxxx/public_html/wp-includes/class-wp-hook.php(288): SiteGround_Optimizer\Supercacher\Supercacher->purge_everything(Object(Plugin_Upgrader))
#5 /home/xxxx/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(”, Array)
#6 /home/xxxx/public_html/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#7 /home/xxxx/p

• This reply was modified 5 years, 9 months ago by Ronnie55.

We’ve never had memory issues before though. The only thing that changed was the version of this plugin.

At least for me.

How would we both start experiencing memory issues only after updating this plugin today?

I’m no developer but it doesn’t make sense to me.

Thanks. I’ll keep an eye on it.

I don’t know what my memory limits are right now (it’s not defined in wp-config.php from what I can tell, currently).

But I’m on a VPS with a ton more resources than I need (in terms of RAM). And I’ve never had an issue before, even when updating 5-6 plugins.

I’ll see if the message ever returns, though, next time I run updates.