$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>Timber, Twig, and Woocommerce: Last product stays in the cart after checkout|Programmer puzzle solving
最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

Timber, Twig, and Woocommerce: Last product stays in the cart after checkout

matteradmin10PV0评论

I am building a site in timber that uses Woocommerce. Everything is working great, except I can't get products out of the cart.

I'm using Woocommerce Product Add-ons, a subscription plugin called Subscriptio, and some custom Woocommerce functions. however, when I disable all of these, I still can't get the cart to empty after a successful checkout. I have isolated the problem to Timber.

I can create an extremely simple page.php template, that isn't using twig, like so:

<? get_header(); while ( have_posts() ) : the_post(); the_content(); endwhile; get_footer(); ?>

And when Wordpress uses this template, the cart empties just fine. But when I serve the page using twig, the very last item added to the shopping cart stays in there, so when I pay, then go back to the cart, there's always one item left in it.

The header and footer invoked in the above example just point to twig templates, so it's something about just that twig page template that causes the problem.

Does anyone know what could be going on here, and now to fix it?

Post a comment

comment list (0)

  1. No comments so far