BTW – this is the code snippet for the registration button, from Google Chrome Inspect:
<input type=”submit” class=”woocommerce-Button button” name=”register” value=”Register” disabled=”disabled”>
Hi @derrickr
It looks good as I can see on your my-account page.
Link to image: https://cld.wthms.co/htIRoj
I guess you could resolve the issue by yourself?
Please let us know if you still need help.
Hi @htdat
Yes, I got in touch with WeDevs (developers of Dokan) who gave me a ‘fix’ by commenting out line 184 of ‘…/wp-content/plugins/dokan-lite/assets/js/vendor-registration.js’ as follows:
// $( ‘input[name=register]’ ).attr( ‘disabled’, ‘disabled’ );
Obviously this is a short term ‘fix’ and would be over-written whenever they bring out an update!
They specifically told me: “Dokan is based on Woocommerce . This file https://github.com/woocommerce/woocommerce/blob/master/templates/myaccount/form-login.php from woocommerce has been overridden by your theme. If you check carefully you will see that Woocommerce uses “<button ” tag and Dokan is also uses the same. However your theme is using something else which is back dated that where the conflict is. So they had to comment out that line of Dokan. It can be done in other way by reverting back that line and modifying the theme’s tag.”
FYI – We’re using WooCommerce with Storefront and Listify, from which the previous implementation team (i.e. before I was asked to get involved) created their own child theme, in which I can see a number of additional functions that I suspect they were told to add.
I kind of feel very stuck in the middle here, with WeDevs essentially saying: ‘It’s not us, look at Listify’. So, I guess that’s my next port of call.
All in all, very frustrating!
Thanks for updating us.
I understand this is frustrating. However, it’s great to see that WeDevs could track down the cause (the theme).
Please contact the theme author to get help.
If you have any other issue with WooCommerce core, feel free to create a new topic.
