GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Sign in to your account. It may also have been updated. It will require Bootstrap classes added in.
On 18 Feb , at This was needed to be able to edit the archive-product. To get around the issue, I commented out the following lines in woocommerce-setup. Whenever you get a change, please look into whether commenting out this code might cause any long term problems with the theme. I think I understand what vagu I too had the same error when I tried to extend upon the woocommerce functionality of this theme.
If that's all it takes to fix it, then OK just comment out those lines. It's been a couple of years since I build a WooCommerce site in full. I have tried to see the error message that Vagu was seeing, but it's not happening for me on my Mac AMPPS installation with debugging enabled.
Vagu commented something out on Feb 20, but it wasn't clear to me what that was, so I didn't touch it. As far as I know, he didn't reply when I asked him to fork my theme and do implement his fixes in there, so that I could respond to a pull request. With my modifications for Bootstrap compatibility. Most of my modifications were in styling the buttons etc. I did some googling just now and I couldn't find my source, as far as I can remember.
These were no problems at the time; I wonder whether WooCommerce has moved on. There are some simple WooCommerce tutorials out there, for making themes compatible. Maybe WBST should be stripped back and started again, following one of these tutorials.
WBST is meant to be very simplistic. If this is causing so much trouble for people, maybe I should just delete it. I don't have time in my life to keep going with WooCommerce compatibility, and I don't need it for any projects I'm working on these days. Simon, hope you're good. The product archive throws this error: Hi Vagu71 This was all working fine. Maybe the WooCommerce plugin has moved on. There is nothing on line 50 that would cause this error, I think. Simon On 18 Feb , at Sorry, I am not seeing this error.
Not sure if this would cause a problem elsewhere though. Hi Simon, Whenever you get a change, please look into whether commenting out this code might cause any long term problems with the theme.
Look forward to your reply. Hi Simon, I think I understand what vagu Hi Reece, If that's all it takes to fix it, then OK just comment out those lines. SimonPadbury closed this Mar 28, Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment.
You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window.More...