Allyson

Fixed in the next release @cmoura, I’ve added a filter to dates attribute display.

Thanks for your feedback!

Thanks @chenryahts, it’s a critical bug, I fixed that and will publish an update today.

@chenryahts, by default not, but at the moment coding your own product template you can implement this rule. I’ll consider this to a feature/option to be added to the plugin.

Thanks!

Hi @chenryahts,

I need to add a filter to de date displayed in some places, I’m planning an update as soon as possible. And at the moment do you need to code your own product template getting the time to be displayed to your users.

Thanks for your feedback!

Hi @cmoura, thanks, we are happy that you enjoyed our plugin!

I gave a look into the code, and change some incorret text-domain definitions for Clear selection and Participant %u, but the Dates still a mistery for us too. We are trying to fix that and as soon as we find this bug, we leave a reply for you, ok?

Sorry for that problem.
Thanks for the report.

Hi @hornets08,

What is the version of your PHP? This sounds like a problem with the array declaration method used, $users = [];, this short version was implemented in PHP 5.4 (WordPress requires/suggest PHP 5.6+)

Hi @lbrumfie,

You can try put this code in your theme functions.php to remove the action associated to “participants” custom checkout fields generation. But first, update to the latest version, we patched some bug fixes to prevent errors when removing these fields.

remove_action( 'woocommerce_after_order_notes', 'WC_Registrations_Checkout::registrations_checkout_fields', 10, 1 );

Solved! It’s just an incorrect hyphen in plugin header, “Text-Domain”. Resolved by @nielslange in Advanced WordPress Facebook Group.

Sou meio leigo nessa parada dos códigos corporativos cara, o que você quer dizer com os “códigos que s?o enviados”? Os códigos que a empresa recebe ao realizar o contrato com os Correios?

Parece que deu certo, como os códigos estavam como “placeholder”, achei que eles já eram tidos como default e n?o precisava definí-los. Valeu Claudio!

Hi mcgregormedia,

This issue has been fixed in the 1.0.1 version. Thanks for your appointment.

Contacted via form, thanks.

Hi Vladimir,

We’re happy that you liked the plugin! ??

As soon as possible, we will look at this bug, that looks to be a already solved impress.js problem. We need to update the impress.js included in the plugin.
Impress.js issue: https://github.com/impress/impress.js/issues/238

Thank you csonnek, this worked perfectly!

Hi Jeremy,

Sorry too for the late reply. It’s a project in finishing phase, and I cannot wait to find a solution, so I choose to use normal pagination. Sorry but I think it’s not possible to test it in the production website, but I have reproduced the problem in a clean fresh install of WordPress + WooCommerce + Twenty Sixteen.