mandelkind

Fantastic news!! Keep up!

Yes, that’s definitely the issue. The check $btn[‘disabled’] !== ‘true’ is missing for all three sections in the following locations:

woocommerce-checkout-manager/includes/classes/main.php:1515
woocommerce-checkout-manager/includes/classes/main.php:1529
woocommerce-checkout-manager/includes/classes/main.php:1541

Please fix this as soon as possible since this is a major issue on our end ??

Seems like the error is in ./woocommerce-checkout-manager/includes/classes/main.php:1515

The if does not exclude “disabled” fields:

if ( $btn[‘type’] !== ‘wooccmupload’ && $btn[‘type’] !== ‘changename’ && $btn[‘type’] !== ‘heading’ && empty($btn[‘tax_remove’]) && empty($btn[‘add_amount’]) ) {
?>
document.forms[‘checkout’].elements[‘<?php echo $btn[‘cow’]; ?>’].value = “<?php echo $saved[”.$btn[‘cow’].”]; ?>”;
<?php
}

The crons seem still not to be running. I’ve just downloaded the proposed master branch and still receive the following while running wp cron schedule list in terminal:

Warning: Some code is trying to do a URL redirect. Backtrace:
#0  WP_CLI\Utils\wp_redirect_handler(https://.../wp-login.php?redirect_to=http%3A%2F%2F%3A)
#1  call_user_func_array(WP_CLI\Utils\wp_redirect_handler, Array ([0] => https://.../wp-login.php?redirect_to=http%3A%2F%2F%3A)) called at [/var/www/.../htdocs/wp-includes/plugin.php:235]
#2  apply_filters(wp_redirect, https://.../wp-login.php?redirect_to=http%3A%2F%2F%3A, 302) called at [/var/www/.../htdocs/wp-includes/pluggable.php:1208]
#3  wp_redirect(https://.../wp-login.php?redirect_to=http%3A%2F%2F%3A, 302) called at [/var/www/.../htdocs/wp-includes/pluggable.php:1307]
#4  wp_safe_redirect(https://.../wp-login.php?redirect_to=http%3A%2F%2F%3A, 302) called at [/var/www/.../htdocs/wp-content/plugins/wp-force-login-master/wp-force-login.php:49]
#5  v_forcelogin()
#6  call_user_func_array(v_forcelogin, Array ([0] => )) called at [/var/www/.../htdocs/wp-includes/plugin.php:525]
#7  do_action(init) called at [phar:///usr/bin/wp/php/wp-settings-cli.php:405]
#8  require(phar:///usr/bin/wp/php/wp-settings-cli.php) called at [phar:///usr/bin/wp/php/WP_CLI/Runner.php:736]
#9  WP_CLI\Runner->load_wordpress() called at [phar:///usr/bin/wp/php/WP_CLI/Runner.php:697]
#10 WP_CLI\Runner->start() called at [phar:///usr/bin/wp/php/wp-cli.php:21]
#11 include(phar:///usr/bin/wp/php/wp-cli.php) called at [phar:///usr/bin/wp/php/boot-phar.php:5]
#12 include(phar:///usr/bin/wp/php/boot-phar.php) called at [/usr/bin/wp:4]

Wir haben ebenfalls das Problem, dass seit dem Update auf 2.0 die 404page nicht mehr funktioniert.

Haben zwar keinen Site-Origin installiert, allerdings hat das Parent Theme eine 404.php im Theme Rootverzeichnis und diese wird jeweils angezeigt anstelle der im Plugin definierten Seite. Eventuell h?ngt das ja irgendwie zusammen?