tiylwp

@incubado: Kannst du sagen, woran der ursprüngliche Fehler lag und wie du ihn behoben hast? Ich habe das n?mlich auch gerade ??

(Leider kann ich zur zweiten Frage nichts beitragen.)

In other threads (see for example https://www.ads-software.com/support/topic/missing-or-a-s3-server-url-after-update-to-3-4-5/), @duongcuong96 mentioned that the option to use other S3 services besides Amazon was removed and is not supported anymore:

For now, we currently only support backup to AWS S3 so that why we removed the custom S3 service.

If true, thats a real pity and a reason to switch to another backup solution.

Even worse is the half-assed confirmation of a bug in this thread by @duongcuong96 and the deafening silence since then.

I can confirm that error, seeing the sam behaviour and nginx refusing to start after W3TC changes its nginx config file.

It seems to result from line 1480 in PgCache_Environment.php. Adding a “;” in front of \n might help as a temporary solution.

@duongcuong96
Any updates on this topic. It’s one week since your developers should have a look at the topic and my backups to Google Storage are still not working.

I have no idea how to attach images in this forum, but you may find my settings (and the error message) in this linked png:
https://www.dropbox.com/s/y0z1h8psy93t2np/backWPupS3Google-1.png?dl=0

Note the wrong URL in the curl message that does not fit for Google services.

The error message in the log shows the same:
[13-Apr-2018 22:09:42] 1. Trying to send backup file to S3 Service …
[13-Apr-2018 22:09:49] ERROR: S3 Service API: [curl] 6: Could not resolve host: xxxxx.s3.google-storage.amazonaws.com [url] https://xxxxx.s3.google-storage.amazonaws.com
[13-Apr-2018 22:09:50] 2. Trying to send backup file to S3 Service …
[13-Apr-2018 22:09:57] ERROR: S3 Service API: [curl] 6: Could not resolve host: xxxxx.s3.google-storage.amazonaws.com [url] https://xxxxx.s3.google-storage.amazonaws.com
[13-Apr-2018 22:09:57] 3. Trying to send backup file to S3 Service …
[13-Apr-2018 22:10:04] ERROR: S3 Service API: [curl] 6: Could not resolve host: xxxxx.s3.google-storage.amazonaws.com [url] https://xxxxx.s3.google-storage.amazonaws.com
[13-Apr-2018 22:10:05] ERROR: Step aborted: too many attempts!

Everything worked fine before the last update to 3.4.5.

I can confirm that the changes fix this behaviour in all combinations mentioned/tested.

Thanks a lot!

The reported behaviour seems neither related to the theme nor other plugins or CSS rules. The following screenshots are from a new test installation with only Woocommerce V 2.6.14 and Woocommerce Germanized V 1.8.3 as active plugins, WordPress V 4.7.3 and the WordPress theme Twenty Seventeen.

Woocommerce Germanized setup uses the default options, I just added “inkl. MwSt.” as a global price suffix, as shown in the following screenshot. Please note that the product has a regular and a sale price, but no sale price labels (“Streichpeis Hinweis”/”Angebotspreis Hinweis”) in this example:

With this setup, the display is correct: The regular price is striked out, there is a space separating regular an sale price, the additional text “inkl. MwSt.” is present as a price suffix.

Now, lets switch just one setting for the product, leaving everything else untouched. Select “UVP:” as the sale label (“Streichpreis Hinweis”) for the product. Here is the corresponding screenshot:

Note that now (as expected) the regular price has “UVP:” as a prefix and is stroked out again, but the space separating the regular and the sale price is missing and the additional price suffix “inkl. MwSt.” is gone, too.

Now, changing the product setting again by using “UVP:” not as the “Streichpreis Hinweis”, but the “Angebotspreis Hinweis”:

This time, the regular price is not even striked out, the separating space is missed and the additional price suffix doesn’t show either.

You can clearly see that just by changing one setting, the display of the product price is messed up. That’s true for the shop overview as well as the product pages. No other plugins or CSS rules are involved.

Thank you, I apologize. Somehow, I thought that a plugin called “Woocommerce Germanized” with problems only affecting the german language community would offer support in german. Moreover, it seems there are support threads in german in this forum.

But to repeat my problem in english:

Display of pricing information in the store is somehow broken when using sale labels in Woocommerce Germanized v1.8.1 and v1.8.3:

• After selecting a “sale label” (“Regul?rer Preishinweis”), in customer facing pages the old price is striked out (as expected), but the additional price information “inkl. MwSt.” (“incl. VAT”) is missing (it is shown for all other products that don’t have a sale label attached). This happens in the store overview as well as on the product pages. In version 1.8.3 of the plugin, in addition I’m missing (for some products?) a space separating the old, striked-out price and the new one. That didn’t happen in version 1.8.1.
• If attaching a “Sale Regular Label” (in german UI: “Neuer Preis Hinweis” (sic!)), even the strike-out markup of the old price is missing, which really seems faulty. And again, the pricing info “inkl. MwSt.“ is missing.

The informational text “inkl. MwSt.” seems crucial for customers and required by law. (BTW. The second info text “zzgl. Versandkosten”/ “plus Shipping Costs”) is not affected and displayed correctly everywhere.)

Yes, totally messed our site.

So, don’t update!

And in case you already updated and have the same problems:
Deactivating caching options didn’t help for us, only deactivating the plugin altogether.

No good advertizing for the premium options.

Update: Ich war jetzt in der Lage, dem Versandkostenrechner auf der “Kasse”-Seite zu aktivieren. (Option übersehen, sorry). Trotzdem funktioniert das Erzwingen des kostenlosen Versands nicht mehr bei mir.