esi and private cache problem with logout nonce

Thanks, 1- so to cache privately, it should be used like this?:

add_action( 'litespeed_esi_load-my_esi_block', 'my_esi_block_esi_load' );

function my_esi_block_esi_load()
{
do_action( 'litespeed_control_set_private' );
echo "hi";
}

2- If we don’t set ttl, the cache will remain indefinitely?: do_action( 'litespeed_control_set_ttl', 300 );

3- Is there a way to force the content cache of this esi to be cleared during an operation?
(only for that user)

No I didn’t, please guide me how to do it?

This is the code that creates the menu list and the LOGOUT button link at the end:

<?php foreach ( wc_get_account_menu_items() as $endpoint => $label ) : ?>
    <li class="<?php echo wc_get_account_menu_item_classes( $endpoint ); ?>">
        <a href="<?php echo esc_url( wc_get_account_endpoint_url( $endpoint ) ); ?>"><?php echo esc_html( $label ); ?></a>
    </li>
<?php endforeach; ?>

We can also have the LOGOUT button outside the FOREACH like this:

<li class="wc-account-menu-item logout">
    <a href="<?php echo esc_url( wc_logout_url() ); ?>">logout</a>
</li>

• This reply was modified 1 year, 11 months ago by monoor. Reason: add alone logout

ls log (click here), log is for a user with the customer role

As it is in the log, this role is not an admin: [Router] get_role: customer

But I don’t know why admin bar is written yes.

And I tested this with a subscriber role, the result was the same as the previous report.

Anyway, isn’t wc_logout_url a function for WooCommerce? Shouldn’t the way its nonce work be the same on all sites?