Any working example of Sage 9 latest (Sage 9.0.0-beta.4+) with WooCommerce (3.1.1+)?

sage
, ,
22

Hi, Hambos, great Ill do a Bootstrap 4 version, (you are right its OK anyway) and a vanilla one, Is there a Navwalker in it ? Thanks

23

Νο I didn’t include one. I’ve used extends via scss.

25

Hi again,

I just wanted to try out your option to use radio buttons for the product options in variable products.
As your documentation states:

Radio for product options in variable products!

To enable it

single_product:
	radio_variations:
		- slug
		- slug

I presumed the - slug should be your product attribute right?
So for example if I have 2 product attributes color and size, I would have to add the slugs like this?

single_product:
	radio_variations:
		- pa_color
		- pa_size

Unfortunately that is not working, am I missing something?
What exactly should the slug be here?

Thanks!

EDIT: Got it, it obviously had to be:

single_product:
	radio_variations:
		- color
		- size
1 Like
26

@hambos22

In the current documentation, it mentions that the Bootstrap initialisation has been disabled. If I need bootstrap to be included and initialized how do I do that?

27

Hi

It’s already included. In the docs, I mean that I disabled the choice to initialise frameworks (bootstrap, foundation etc) to protect scss from breaking.

28

@hambos22 Awesome, thanks for all the amazing work, huge time saver!

1 Like
29

How were these problems not thought of before shifting Sage to Blade templating?

The fact that this is such a mess seems like a major oversight in the rush to make Sage as ‘modern’ as possible.

Pretty frustrating - particularly the lack of response from those officially involved.

Why is there no guidance in the (paid) docs or at least a Blog post like there was for the original Sage versions?

@ben @swalkinshaw

1 Like
30

This is open source. Feel free to help out. :slight_smile:

Demonstrating a sense of ownership rather than entitlement is a greater motivator for everyone involved.

31

Thanks, but this is nothing to do with entitlement. It doesn’t diminish how much I appreciate the Sage theme and the entire Roots project.

But for me this is about the importance of releasing something that’s production ready and commercially viable… As I say, not allowing for or planning an easy WooCommerce integration seems like a huge oversight.

We’re seriously considering rolling back to 8.4.2 at this rate.

1 Like
32

What problems?

How come Sage is at fault here?

Not sure what you’re looking for here

Look, clearly you’re having trouble with integrating WooCommerce with Sage. What’s not cool is how you’re expecting everything to be a certain way… maybe try and remember that this is open-source software?

You’ve done a whole lot of complaining without mentioning any specific issues.

Sure looks that way.

Seriously still waiting for you to mention any sort of specific issue.

3 Likes
33

What, specifically, doesn’t work? Have you reviewed the other threads addressing Woo integration? Others are having good luck integrating the two. Where are you getting stuck? Is there an error you can share?

1 Like
34

I have checked other threads regarding Woo integration, there is a common thread of frustration. The fact that a completely seperate theme has been created to easily facilitate the integration seems to highlight a problem?

Lack of Woo Blade template support, duplicate content occurrences, inconsistent information on where to place template override files. I can see that the frustration stems from the lack of support offered by the Roots team.

Why isn’t there a single source of truth or resource that describes where to place these files or integrate efficiently? Surely asking for consistency shouldn’t result in being labeled ‘entitled.’

I feel like there’s a lack of compassion and air of superiority that is conveyed by some which really isn’t helpful.

Anyway, in the meantime I’ll give the completely seperate 3rd party theme a try I guess.

1 Like
35

There are several popular plugins that don’t work well with Sage 9. It’s not the best tool for every project depending on your plugin needs, however working with Woo is definitely possible and has been accomplished by many users.

You are continuing to express frustration with the process, but you’ve yet to explain where and how you are getting stuck. Have you tried the methods in the other threads, despite the fact there might be a couple of different suggestions for where to place the templates? Did you receive an error we could see and help troubleshoot?

The Roots team and the volunteer forum support crew are here to help with Roots products. We’re enthusiastic and eager to assist with these tools we feel make WordPress development easier and better. Unfortunately the Roots team cannot anticipate all users’ plugin needs and as such some plugins, even popular ones, are not yet canonically documented. If you are able to determine a best practice for working with Woo, I’m sure the team would appreciate an article submitted for the Guides section of the site.

7 Likes
36

Thanks a lot @hambos22, I really appreciate your work and effort!! Thanks again.

1 Like
38

Quick Update for anyone looking for the quick fix I mentioned above.

If you are using the latest version of WooCommerce (currently 3.4.4) you need to rename:

/resources/woocommerce/archive-single.php

to

/resources/woocommerce/archive-product.php

WooCommerce has renamed this file so we need to as well to ensure we override it.

I would edit my previous answer if I could.

Just spent ages trying to get this to work and wrongly assumed it was the updated version of Sage (currently 9.0.1).

3 Likes