Dominik
Forum Replies Created
-
Forum: Plugins
In reply to: [Germanized for WooCommerce] 3.20.6 Price error at variables@vdwoocommercesupport I also had an error with unnecessary slashes for a product without unit prices.
<p class="wc-gzd-additional-info price price-unit smaller variation_modified variation_gzd_modified" aria-hidden="true" data-o_content="" style="display: block;"> <del></del> <ins></ins> / </p>I temporarily solved this in my functions.php:
add_filter('woocommerce_gzd_formatted_unit_price', 'my_cleanup_empty_gzd_unit_price_html', 10, 4);
function my_cleanup_empty_gzd_unit_price_html($html, $price, $unit_base, $unit)
{
$plain_price = trim(wp_strip_all_tags((string) $price));
if ('' === $plain_price) {
return '';
}
return $html;
}Could this also be relevant for the fix? I added it here because it was about price displays/handling of variable products in the identical version, and I thought it fit well in the context :). Thanks for the quick response!
- This reply was modified 3 months, 2 weeks ago by Dominik.
Forum: Plugins
In reply to: [Germanized for WooCommerce] 3.20.6 Price error at variablesFor variable products that differ in price due to a specific attribute, for example, I receive the following warning since 3.20.6:
PHP Warning: Undefined array key "regular" in /…/wp-content/plugins/woocommerce-germanized/includes/class-wc-gzd-ajax.php on line 385; PHP message: PHP Warning: Undefined array key "sale" in /…/wp-content/plugins/woocommerce-germanized/includes/class-wc-gzd-ajax.php on line 385'- This reply was modified 3 months, 2 weeks ago by Dominik.
Hi @alaasalama! Thank you for the information! I have installed version 4.3.2 of WP STAGING WordPress Backup Plugin – Backup Duplicator, but the MU plugin still shows me version 1.5.5. Could it be that this was not automatically updated with an update of the WordPress plugin? I have had the plugin since October 2023. WP version is 6.8.3. WP version is 6.8.3. The mu-plugins folder has write permissions drwxr-xr-x (755).
After reinstalling, I now also have MU plugin v. 1.6.
- This reply was modified 6 months, 1 week ago by Dominik.
Forum: Fixing WordPress
In reply to: PHP Fatal error allowed memory sizeWordPress, WooCommerce, Divi – no problems with PHP 8.3.x. Only JIT must be deactivated.
So there are no problems if JIT is deactivated. As far as I know, it is still unclear why this does not work for several people with WordPress.
- This reply was modified 1 year, 2 months ago by Dominik.
Forum: Fixing WordPress
In reply to: PHP Fatal error allowed memory sizeI have the same problem today after updating the Divi theme:
Allowed memory size of 4294967296 bytes exhausted (tried to allocate 4295229440 bytes) in /var/www/vhosts/example.com/example.com/wp-includes/theme.php on line 325′
OPcache and JIT are also active in PHP 8.3.
opcache.enable=1
opcache.memory_consumption=256
opcache.jit=1255
opcache.jit_buffer_size=128M
opcache.validate_timestamps=1
opcache.revalidate_freq=2I would have no problem implementing this, but unfortunately there doesn’t seem to be a really good selection option for this, as far as I can see.
Isn’t this forum also intended for such specific questions?
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] WooCommerce Mollie Java Script Events?Hey Femi,
this is about WooCommerce displaying certain things incorrectly by default, as described here (https://vendidero.de/dokument/umsetzung-der-button-loesung-im-woocommerce-checkout).
For example, payment details need to be before the order summary. The “Buy Now” button should be immediately after the order summary (without terms and conditions, payment method selection, etc., in between).
If these shifts are made with JavaScript to not lose the benefits of the Divi Builder for the checkout page, it would be nice to have a JavaScript event indicating that Mollie has loaded the payment methods.
Otherwise, a time-based shift is required for it to work.
- This reply was modified 1 year, 12 months ago by Dominik.
Forum: Plugins
In reply to: [Germanized for WooCommerce] WooCommerce Divi order process broken 3.16.7Thank you very much works again! 🙂
My mistake, I forgot the brand :). After that it worked.
Forum: Plugins
In reply to: [WooCommerce] problem with Version 8.5.1 after update@emrevona is there a way with priority handling to solve this?
Same error here