rohe

Hi @magazine3

in Version 1.9.25 this issue is fixed, so I allow myself to mark this thread as resolved ??

Thanks for your great support, even with the free version. That’s more than I know from several other developers… thumbs up and keep on creating awesome stuff ??

Hi @magazine3

thanks for your response.
I tried the update to Version 1.9.22 today, unfortunately the issue still shows up in the new version.

Because of that I repeated my tests and made some screenshots of my plugin setting the configuration of Schema & Structured Data for WP & AMP and the duplication of the category thumbs showing up in the frontend. Maybe it helps.
You can donload the commented screenshots as a single JPEG-File following this link: https://drive.google.com/open?id=1TsmsM-_S_bJEbB1eUPXu2PRIFDIkgMd4

I repeat my offer, if you need access to an installation that shows this behavior I can give you access to my development environment. It is completely seperated from any life-system, so it doesn’t matter if anything crashes ??

Wow… that sounds great.
Thanks for putting this issue to the feature-list.

I’m looking forward to what is coming up with the next updates ??

Kind greetings, Roland

• This reply was modified 5 years, 6 months ago by rohe. Reason: error correction

Hi Fred,

still not working. Neither in time based nor in action based mode.

And after testing your advice and switching back to action based mode (the only change I made), Swift now got another issue:
After clearing cache Swift should rebuild it automatically and it starts doing this. But after a few seconds it is starting from the beginning again and is caching the same 10-15 pages again and again and again…

The Log shows neither errors nor warnings.

Sorry, but I got the feeling Swift is not suitable as a caching-solution for big sites with daily updates like an onlineshop.
I will wait about another day if you maybe have a solution, but I think it is better to switch back to W3 Total Cache. It is not as efficient as Swift, but it is working.

Hi Fred,

Nope, sorry. Doesn’t work.
Changed settigs as you told, cleared cache, tried. Same result as always.

• This reply was modified 5 years, 8 months ago by rohe.

Hi Fred,
thanks for the quick answer. This is pretty cool.

the URL is https://hexerey.com/my-account/

The e-mail verification is managed by “woocommerce germanized”, a plugin which adds some functions to woo and adjusts some other so that woo complies to german and european law.

As far as I understand the mechanics of the registration process, it breaks at the point at which the user should be redirected back to the my-account mainpage. Also at this point there should be a cookie check if the confirmation is already done. Depending on the result of this check a dynamic driven message should either welcome the user or ask him to check his mails and confirm registration.
But cookie check and triggering the message should be standard woocommerce features… afaik.

Dear Rynald0s,

in case you’ve overseen it: There are two issues in this thread.
One with the markup on the product pages which throws warnings in GSC.
This is the one at github #22842.

The second issue is mentioned by @smokingblends in the 3rd reply.
It is the one that concerns the archive pages (product category) and throws errors in the GSC.

It is nice to read that there seems to be a solution for the first issue. Haven’t tried it yet.
But what about the archive pages? Is there a solution similar to #22842?

And could you please give us a hint when Automattic is planning to fix this in future versions?
It’s nice to have a snippet that works… more or less clean… for now… but shouldn’t schema markup be included in the core-product, and not by some user-workaround?

Aye, same here. I’m one one of “every Woocommerce user”.

Fortunately I’m using a plugin named “WooCommerce Germanized” for some features I need to run a shop according to german and european laws, which offers some of data Google wants to know as some kind of “side effect”.
(Don’t get this wrong for a solution outside of germany, it changes many things really deeply especially for german law. It may collide with your local laws!)

Unfortunately it only offers data for some minor warnings in the GSC.

The major ERRORS, named missing “offers”, “review” and “aggregateRating” remain.

Before all it is mostly annoying that woocommerce seems to miss the “offers” shema completely.

I hope there will be an update fixing this soon. Cause without, woocommerce will become unattractive to every merchant who is interested in doing earnestly business within weeks.
If we like or not, we need google and we need our rankings.

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

Hi CoolHappy,

since the 1.3.1 Update and some new custom CSS everything works fine again. Thank you ??

Best Regards

Das ist natürlich cool beide Optionen anzubieten. Elegant gel?st. Ihr habt soeben meinen Tag gerettet. **Denkt Euch hier einen kitschigen Facebook-Knutsch-Smilie**

Was mein Szenario angeht, das hat ja bis zur 2.2.4 mit Bordmitteln wunderbar funktioniert. Lagerbest?nde von Dropshippingartikeln per CSV importiert, dann nur noch per Bulkedit meine drei verschiedenen Lieferzeiten wieder zuordnen, weil die ja von dem jeweiligen Eintrag des Gro?h?ndlers überschrieben werden.
Ist t?glich 10 Minuten Handarbeit, was aber den Vorteil hat dass ich immer in etwa auf dem Schirm habe was sich so bei meinem Dropshipper tut.

Ja, das lie?e sich sicher auch automatisieren alles. Aber so weit ist der Shop einfach noch nicht. N?chstes Jahr kommt erst mal noch Eure Pro-Version neben 3 anderen kostenpflichtigen Must-Have-Plugins und dann hoffe ich das Projekt aus der Klasse “Nebenerwerb” raus pushen zu k?nnen.

Danke für die schnelle Antwort.

OK, so weit ich das sehe l?sst mich der Filter genau EINE individualisierbare Meldung anzeigen. Das funktioniert im Test auch wunderbar, ist aber trotzdem nicht sonderlich praktikabel bei dem beschriebenen Szenario.

Denn wie l?se ich es, wenn Produkte mit Backorder-Status 3 verschiedene Lieferzeiten haben sollen?
In der Praxis habe ich 3 verschiedene Backorder-Stadien die sich in der Lieferzeit wiederspiegeln.
1. Frisch eingetroffen, muss noch erfasst werden –> Lieferzeit A = Kurz (zusammen mit Artikeln die sofort versandfertig sind)
2. Bestellt, im Zulauf –> Lieferzeit B = Mittel
3. Wird erst auf Kundenwunsch bestellt –> Lieferzeit C = Lang
Da ich die Verfügbarkeit der Ware innerhalb der jeweiligen Lieferzeit garantieren kann, soll sie natürlich bestellbar bleiben. Egal ob ich die selbst versende oder mein Dropshipper.

Oder wie l?sen Andere sowas? Ist das so ungew?hnlich Ware bestellbar halten zu wollen wenn man wei? dass man sich auf seine Lieferanten verlassen und seine Lieferzeiten einhalten kann?

Bin hier übrigens auch für Workflow-Tipps von anderen Usern offen. Wie würdet Ihr dieses Szenario l?sen?

Grü?e, Roland