ulrichnielsen

Hi @markwolters,

thanks for your help. I just turned the extension back on and it seems to be working. It remains unclear what exactly caused the global redirection. For the time being, please consider the issue resolved. If it pops up again, I’ll report back.

Regarding svg, the https:// is part of a namespace, it’s a constant and not a real url therefore most sources don’t recommend to tamper with it. But Lighthouse and other peformance tools perceive it as non-secure and this probably affects SEO too. The w3c consorcium just never bothered to update this ancient piece of code.

This is great news. Thanks for the awesome support!

Hi @cybr, thanks for the reply. Fortunately there’s no error message now, it went away on second attempt, so consider it resolved. However, if a complete uninstall involves losing all entered SEO data, it’s not a viable solution. It would be such an effort to recreate all contents and settings, I’d not use it even as a last resort. If you mean just deleting the plugin in the file manager and uploading the new version manually, I’ll try next time this error occurs. Thanks again!

This is perfect, much appreciated!

Wow this is perfect, thank you so much!

Thanks much @yingscarlett, it works, although I was hoping to find a solution similar to the one I posted above. Half of my problem was that I didn’t know is_home returns true even if the blog page is not the home page. I checked the WP reference and it was indeed trivial.

But I don’t get it how the blog page is different from archive pages like tags, categories, search. They all can display the title without injecting extra markup. If this went into the header template it’d be fine but in functions.php it’s sort of a hack.

This is what I finally added:

 echo '<h1 class="entry-title">' . get_the_title(19) . '</h1>';

I know it’s an extra db query but a hard coded title just didn’t feel elegant.

This is it! Thank you so much, David! Awesomest support in the whole WP community ??

Thanks for all the help, I’ll figure it out. I’ll need to read up on it.

Hi @fernandoazarcon2 , thanks much, I’ll give it a try. I do have the GP premium plugin but I’m not using the block editor, in fact I’ve disabled it to remove excess js/css. I prefer doing everything manually.

Hi @yingscarlett , thanks but it just has hooks and I’d like to access the .inside-header div, which doesn’t seem possible through the header.php in the GP root folder.

I should have considered the dependency, it’s basic. Thanks much for your support, now I got everything I need ?? I’ll mark it as resolved.

@diggeddy Thanks, David, it works but works too well. It effectively removes all styles regardless where they come from. There isn’t a single css linked in the source code when this snippet is active.

Any idea what goes wrong?

Update: I found a workaround, although I’m not sure it’s right. But it works. After your snippet I added this to enqueue my child theme style again:

add_action( 'wp_enqueue_scripts', 'my_plugin_add_stylesheet' );
function my_plugin_add_stylesheet() {
	wp_enqueue_style( 'generate-child', get_stylesheet_directory_uri() . '/style.css', false, '1.0', 'all' );
}

I got it from the WP child theme developer manual. Seems to me like a pretty ugly hack.

@fernandoazarcon2 Thanks but no joy. I tried on two different sites. It has no effect, main.min.css is still being pulled from main GP theme. Nothing stops it from popping up.

Anyway, what’s the point of adding the snippet through a plugin vs. functions.php?

Hi Luis,

thanks so much for your assistance. The URL string is in place so it’s not the culprit. Testing plugin conflict is a challenge as this is a production site and Hummingbird won’t work properly on localhost. Polylang and SEO Framework might affect it, although in the latter I turned off sitemap generation, and anyways it would conflict with the sitemap plugin rather than with caching.

Worst case scenario, I flush the page cache manually when there’s a new post. This is a minor issue and the plugin is otherwise awesome.

I’ll report back when it’s done. Thanks again.

Hi Mateusz,
just an update: 5.4.2 seems to have fixed the issue. It’s back to normal. Whatever it was, it was the plugin and not my config after all. I kept investigating today the whole day which is pretty cumbersome as I have almost zero experience with rest api.
Thanks much! Consider the issue resolved.

• This reply was modified 1 year, 11 months ago by ulrichnielsen.