gerd.neumann

Danke, damit verschwindet das Spinning Wheel.

So ganz toll finde ich das neue Verhalten aber immer noch nicht. Beim Preis selber ist es ja so, dass sich dieser sofort ?ndert, wenn man die Variante wechselt. Anders und deshalb nicht ganz konsistent: Beim Grundpreis flasht jetzt dieser graue Ladebalken bzw. Platzhalter auf und schenkt diesem Grundpreis-Feld mehr Beachtung als es verdient. Also der Blick des Users wird darauf gelenkt.

Kann man es wieder so wie vorher haben, dass einfach der alte Grundpreis die 1s die es dauert den Grundpreis nachzuladen stehen bleibt? Das finde ich weniger “aufdringlich”.

Oder noch besser, wie beim Preis gleich den Grundpreis irgendwie mitliefern, so dass es gar keinen Request hier braucht?

Das hat nicht den gewünschten Effekt. Das Markup des Grundpreises wird beim Wechsel der Varianten ge?ndert zu:

<p class="price price-unit smaller wc-gzd-additional-info variation-modified loading">

D.h wc-gzd-placeholder-loading scheint hier bzw. zu diesem Zeitpunkt gar nicht relevant.

PS Bisschen schwierig zu debuggen, aber mit Rechtsklick auf den DOM-Node in den DevTools und dann Break on > Subtree changes geht es.

Hier ein Screenshot:

View post on imgur.com

So probably you had previously a sitemap generator that created /sitemap-pt.xml before but now that sitemap is not there anymore while the spider still tries to access it.

Nope, been using your plugin for the last 4 years or so. BTW, thank you for making it ??

The issue is fixed in the upcoming release.

Great ??

For anyone getting here via Google. I have created a Pull Request that implements this behavior: https://github.com/themeum/tutor/pull/74

Hi @creativeartbd Will this be part of Tutor 2.0?

How can I follow the status of feature requests or bug tickets? I’ve seen links to a Trello board here in the support threads, but its access is private. See screenshot: https://i.imgur.com/ovE1z2J.png

Kind regards.

PS Regarding workarounds: The given CSS only fixes it for the first button. To have the workaround applied also to the second button (the submit button), it needs to be:

.tutor-course-enrolled-review-wrap .write-course-review-link-btn, 
.tutor-course-enrolled-review-wrap .tutor_submit_review_btn {
  text-transform: none;
}

I the long run I do not want to add such a workaround rule for every button that has a .single_add_to_cart_button, .tutor-button or .tutor-btn css class. ??

Hi @parag44

sure this fixes the error. However, 1st this is a workaround and I would prefer it if this could be fixed in the Tutor plugin itself so I do not have to maintain such workarounds in the long run. Secondly, the rule that causes this also includes .single_add_to_cart_button as selector and because Tutor loads its CSS on every page and not just course page, this also mangles the WooCommerce buttons text.

So it would be great if you development department could consider fixing this within Tutor.

Just wanted to add, that the Polylang developers are very supportive: Very often when I had used a plugin that was not supported out-of-the-box, I notified them via https://polylang.pro/ contact form that I used a certain plugin, and then *they* send in a Pull Request or Patch to this plugin to it got Polylang support.

Hi @munayam

ok, wrote you an email. I initially asked at the public forum since this question is also valid for the Freemium version.

PS

I missed the /courses/ page (since it does not really seem to be a page):

/courses/ => My Account

Hi @hutch79

I am just another user and also have WooCommerce and Polylang. For what I know, Polylang has a WPML compatibility. So if WPML is supported, then Polylang should be also.

https://polylang.pro/doc/the-wpml-config-xml-file/

https://polylang.pro/doc/wpml-api/

I also think that Polylang is superior to WPML, so strange it is not supported. Especially, it does not seem like a lot of work (maybe! – from my understanding)

Would be great if this could be added to the WooCommerce plugin (as an option at least). I also have a working WooCommerce “My Account” page and just need another “Enrolled courses” subpage there.

Hi @niklasinpsyde

so this means the PayPal Plus plugin cannot be used together with the PayPal payment method already included in WooCommerce? Just asking because we already use WooCommerce subscriptions for 3 years (with PayPal) and I was about to evaluate the usage of PayPal Plus.

This looks like a showstopper then.

Kind regards,
Gerd

Ich habe hierzu Upstream ein Ticket aufgemacht: https://github.com/woocommerce/woocommerce/issues/29386 Mal sehen.

ok, danke :-/

Hiermit lie?e sich wohl umsetzen:

// Display product name as uppercase, CSS is not possible
// Too dangerouse, because sometimes the $product_name can come as a link as sprintf( '<a href="%s">%s</a>' ...)
function fr_uppercase_product_name_in_cart( $product_name, $cart_item, $cart_item_key ) {
    return strtoupper( $product_name );
}
add_filter( 'woocommerce_cart_item_name' , 'fr_uppercase_product_name_in_cart', 10, 3 );

Aber da $product_name manchmal auch als ein sprintf( '<a href="%s">%s</a>' ...) als Parameter kommt, ist mir das zu heikel.

Scheint mir nicht ohne zu hohem Aufwand/Zukünftige Risiken bei Updates umsetzbar.