Logo in header point to wrong url

Hi Peter,

It seems you already have fixed the problem. Cause when I clicked it it goes to the homepage.

Hi Edde,

This issue does seem sporadic. Could you try something for me? Go to any page on the site and then click on the logo. What page do you end up on?

Do you know where the url associated with the logo is stored?

Thanks

Hey Peter,

You are right. Did you look at appearance>customize. Is your sample page in your post section?

Maybe try deleting your hello world post and see what happens

Hey Edde,

Thanks for the help. I selected “Don’t show any posts or page” in appearance>customize>front page. I deleted the hello world post and that created a page not found error. I undid the delete.

I’ll try deleting the logo and re-uploading.

Cheers

Hmm so none of that work. I haven’t arise to this problem using customizr. But try this in your child theme functions.php

Snippet

I deleted the logo and the site title was displayed and the url problem still existed. I put back the logo.

I tried the snippet you suggested – no change. The snippet mentions tc_logo_title_display. Maybe the issue is there. I’ll keep looking.

Thanks for your help

The problem doesn’t seem to be there for me.
Have you resolved it?
If not, are you running a cache?

Hi,

No not resolved, but I did find something interesting.

I have cleared the cache on my laptop and desktop, but the problem continues on both those machines using IE, Safari or Chrome.

The problem does not happen when using my iphone or ipad using the mobile version of Chrome or Safari to navigate the site.

I am using the latest versions of Customizr and WP.

Thanks

Peter

I meant a cache on the server, like W3 cache.

Does that mean the W3 cache should be cleared? If yes, I’ve never done that before – any advice?

Thanks

Don’t use it myself. Google throws up this: https://www.inmotionhosting.com/support/edu/wordpress/recommended-wordpress-plugins/clearing-cache-in-wordpress

I installed W3 Total Cache and ran it. The problem comes and goes after clearing the cache. I’m ok with that because it seems to prove your idea that the issue is a caching issue. At least now I can pinpoint the source of the problem.

Thanks again for your help.

Peter