plimfec

Hi @fresatomica,

Thanks very much for replying.

I tested the issue here at my test website:
https://www.leestipper.nl/nieuws-acties/nieuws/polare-sluit-na-winkels-nu-ook-website/

This one is updated for WordPress, theme and plugins. It’s running the default Twenty Twenty theme, like you suggested. None of these plugins are in conflict with Jetpack (I tested with all deactivated).

It’s interesting, because here the problem does NOT exist. But in my other websites it still does.

—

I tried to rule out a thousand of possible causes, but can’t get it solved yet. There is one strange thing though: the translations (English -> Dutch) are different.

Compare: https://www.vooreenandergeluid.nl/blog/algemeen/hoe-blijf-jij-in-deze-tijd-sterker-staan-in-de-arbeidsmarkt/

• Houd me via e-mail op de hoogte van nieuwe reacties.
• Houd me via e-mail op de hoogte van nieuwe berichten.

to: https://www.leestipper.nl/nieuws-acties/nieuws/polare-sluit-na-winkels-nu-ook-website/

• Stuur mij een e-mail als er vervolgreacties zijn.
• Stuur mij een e-mail als er nieuwe berichten zijn.

Both websites are up-to-date and running the last version of WordPress and Jetpack (8.6.1). So one could expect the same translations here.

—

QUESTIONS:

• Where can I find these translations?

• How come these translations are different while running the same versions?

• And most important: could the cause for my problem somehow be related to the (source of the) translations? Perhaps the old translation files are blocking to obey the settings?

Hi @macmanx,

They are different hosting providers, so I can’t ask one of them to compare both websites..

Since the hosting provider for https://www.q-art.nl/magazine/redactioneel/drie-liederen-voor-sopraan-contrabas-en-piano/ apparently is not blocking xmlrpc.php, and I do neither, could you please have a suggestion why Jetpack nevertheless seems to ignore my settings for this website?

Because my problem is not the blocking of xmlrpc.php by any hosting provider, but Jetpack not letting me switch off ‘subscribe to site’ below the comment form.

Thanks again!

Best regards,
Plimfec

• This reply was modified 4 years, 8 months ago by plimfec.
• This reply was modified 4 years, 8 months ago by t-p.

Hi @macmanx,

Thanks for looking into this, much appreciated.

I’m running a firewall at https://www.vooreenandergeluid.nl indeed, but it’s not blocking xmlrpc.php. I arranged that in the settings. But to be sure I did a test with the firewall completely switched off.

Again with these settings:

View post on imgur.com

Unfortunately there was no difference though: still both options were displayed at the front, while I switched off the first (subscribe to site) in the back.

—

The issue could be caused by the hosting provider then (like you supposed), so I took a look to another website I’m running as well:
https://www.q-art.nl/magazine/redactioneel/drie-liederen-voor-sopraan-contrabas-en-piano/

Again with these settings:

View post on imgur.com

This one has another hosting provider and as far as I can find out, there is no block for xmlrpc.php.

Could you please investigate the issue through this website then? Because my problem with these Jetpack settings is not limited to just one website. I noticed it for some time now, a few months I think, in several websites I do maintenance for.

Thanks again!

Hi @fresatomica,

Thanks for your reply.

Yes, that’s correct. These are my settings:

View post on imgur.com

Translations:

• abonneren op site (from screenshot) = subscribe to site = Houd me via e-mail op de hoogte van nieuwe berichten (message shown at the front of the website)
• abonneren op reacties (from screenshot) = subscribe to comments = Houd me via e-mail op de hoogte van nieuwe reacties (message shown at the front of the website)

With the settings in the screenshot still BOTH subscribe options do show at the front of the website.

—

Even when I disable all, like this:

View post on imgur.com

… STILL the front of the website shows the option ‘subscribe to site’ (= Houd me via e-mail op de hoogte van nieuwe berichten)

—

The website affected: https://www.vooreenandergeluid.nl/blog/algemeen/hoe-blijf-jij-in-deze-tijd-sterker-staan-in-de-arbeidsmarkt/

(again: what you see there, is with these settings: https://i.imgur.com/4rYbj3m.png)

Hi @tgboy,

No problem, thank you.

I found two other (minor) bugs I think, perhaps you’re interested. Also present in your own demo https://demo.themegrill.com/himalayas/.

1)
When the title in ‘section-title-wrapper’ > ‘main-title’ becomes a bit longer, the template gives a horizontal scrollbar because of the lines generated by ‘main-title:before’ and ‘main-title:after’.

Example: change the title ‘HIMALAYAS THEME’ into ‘HIMALAYAS THEME HIMALAYAS THEME’ and narrow the screen (or check your mobile device), you’ll see.

2)
Switch between the menu items ‘BLOG’ and ‘OUR TEAM’. The background (blue) shifts in a strange way while the page is scrolling.

Kind regards,
Plimfec

Figured it out. Seems like a bug to me.

See Dashboard > Appearance > Customize.

To force the menu to work properly, you can’t use the header image option the template offers, instead you MUST use the slider. When you choose for a header image, the template just not generates the right code (there’s no destination for the ‘#home’ -> no ‘id=”home”‘ to go to).

Workaround:

• 1) Disable your header image
• 2) Enable the slider instead
• 3) Choose your homepage for slider 1
• 4) Don’t use the other sliders
• 5) Add your header image as a featured image for your homepage now
• 6) Hide the overlay and text coming with the slider option, using CSS in you child theme

Use this CSS to hide:

.slider-wrapper .parallax-overlay {
    display: none;
}

.slider-wrapper .tg-container {
    display: none;
}

Hi @malayladu,

That’s a relief to hear, thanks for your reply!
Keep up the good work, I appreciate very much.

Grtz,
Plimfec

I see it in your changelog for version 2.3.1 indeed. I’m gonna install it soon. Thanks for picking up the issue so quickly.

Best regards,
Plimfec

Hi @jessepearson,

I won’t call it a resolution I suppose.

Two weeks ago I got another email from Google about errors for not specifying the fields ‘offers’, ‘review’ and ‘aggregateRating’ and warnings for missing fields ‘description’ and ‘image’.

That was why I posted in another thread started by some else, linking back to my own topic. But my messages there were deleted and so were someone else’s. Now that thread is set to ‘resolved’ because of ‘inactivity’. Yes, when you delete all messages in a thread, it looks pretty inactive indeed.

Regarding my situation: when I take a look now into the Google Search Console, I have warnings for ‘brand’, ‘ID, ‘aggregateRating’ and ‘review’. No errors at this moment.

I’m not too worried about warnings, but I don’t understand why Google is emailing me now and then about errors. When this stops, I would call this issue as resoluted. But not at this moment I think.

Thanks & grtz,
Plimfec

Hi @madeincosmos,

I tried again to validate the warning ‘Product-ID missing’ in the Search Console and after the ‘first quick validation’ Google did, I get this popup message again:

View post on imgur.com

It says what I mentioned before: ‘Cannot proceed the validation process; solve the problem and validate again’, as well as: ‘This is related to the pages below.’ So I took the page ‘Thomas Olde Heuvelt – Echo’ (second page in the screenshot) and put it in the Structured Data Testing Tool, giving me this as a result:

https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fwww.dwarsliggers.thaumas.nl%2Fdwarsligger%2Fthomas-olde-heuvelt-echo%2F

Just the four warnings again..

I really don’t understand. You know, I could live with these warnings, but indeed I’m kind of worried about the decrease in products showing up in the Search Console. Right now I have only 1 ‘valid’ product left, and 123 products ‘valid with a warning’. Before the WooCommerce update (May 3) there were 393 products in total (from which 315 plain ‘valid’).

Do you have any idea why Google is ‘throwing out’ my products since the update?

Thanks again!
Plimfec

PS No, unfortunately I wouldn’t know how to reach Google about this. Unless you have a company (and paid support), they’re quite unreachable as far as I know.

I don’t think I’m doing something wrong. I did use the validation option before. I just click the button ‘Validate’ and then I get a popup saying ‘Performing first quick validation, this takes no longer than one minute’. After this, I get the error.

So it is not the full validation that’s giving errors, it seems Google first does a quick scan as a threshold for the real validation process.

No Dutch? That’s a bloody shame ??

I tried to validate for each warning at the time. It’s the only way the Search Console lets me do it. But then it gives me within minutes the error I posted above.

Well, they did email me. The sender is ‘Google Search Console Team’ and the address they sent it from is:

Of course this is not a person emailing me, but something apparently triggered their system. I will save you the email itself, because it is in Dutch and I presume you don’t understand, but the subject (translated) of the first mail I got was:

Btw, I’m now trying to validate / report the problems as solved in the Google Search Console, but I get an error during that process. ‘Cannot proceed the validation process; solve the problem and validate again’:

Screenshot: https://i.imgur.com/FdCSj2g.png

Thank you very much @serafinnyc for your reply.

Yes, luckily these are warnings. Strange thing is Google didn’t email me about the ‘errors’ I had before, but did so about the ‘warnings’ I got after I ran the update. But perhaps they did this because of the rapidly increasing number of warnings at that moment.

What is worrying me the most at this moment, is the steep decrease of total indexed products since May 3 (the day I updated WooCommerce).

Any ideas about the cause for that? Or even better: to reverse it?
Would be great.

Thank you!
Plimfec

PS I’m gonna tell Google the problems have been fixed, like you said. Curious to know how this will affect the stats in the Google Search Console next weeks.

Hi @madeincosmos,

Thank you very much for looking into this.

When I go to the Google Search Console, I still get a lot of ‘warnings’. Looking in particular to the product-ID (one of the items you asked for), I get this info:

Screenshot: https://i.imgur.com/uvhpkgB.png

As you can see, it says: ‘Product-ID missing’ and last crawled: May 20, 2019, which is yesterday (regarding to the url at the top of the list).
That url is:
/dwarsligger/saskia-noort-de-eetclub/

When I check this url in the Structured Data Testing Tool, it gives me 4 warnings, but none of them regarding the product-ID:
https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fwww.dwarsliggers.thaumas.nl%2Fdwarsligger%2Fsaskia-noort-de-eetclub%2F

I don’t understand why, because the Google Search Console keeps telling me a different message.

As you can see in the screenshot, this is going on for a few months. I must say I didn’t notice at first, untill I updated to the last version of WooCommerce. The next day Google started sending me emails about these warnings, so I opened this topic. (Strange thing btw is: the number of ‘real errors’ (in red) decreased since I ran the update.)

What can you make of this?

—

Another worrying trend I notice is the decrease of indexed products in general, and a dramatically decreasing total number of ‘valid products’ since I updated to WooCommerce 3.6.2.

Screenshot:https://i.imgur.com/ssFY0OL.png

The number of valid products went from 316 (just before I did the update) to just 3 (today). I don’t have a clue why this is happening, except it’s happening since I updated WooCommerce.

Do you have any ideas to make the best of all this?

—

Thanks in advance!
Plimfec