Thanks for the additional feedback.
When you mention Shopfront Themes, are you talking about this one (which appears to be a theme for Easy Digital Downloads) or was that a typo and you meant the Storefront theme (which is what WooCommerce develops). I’m asking because you mention about “eating your own dog food” and that would make more sense if it was Storefront you are referencing.
We do read all feedback so again, we do appreciate you taking the time to leave it.
Hi there! Thanks for taking the time to write your review. Would you be able to give us a few examples of what type of support requests you faced? Anything specific can help us with future planning.
Thanks!
Hi!
Thanks for taking the time to write this up. It sounds like your products are setup as External/Affiliate Product types correct?
Currently the Featured Product block doesn’t provide the option to automatically link to the external url set for the product if the product is an External/Affiliate product type. The button for this block is set to default to the link to the product details page on your site.
The buttons for the Hand Picked products block do link to the external urls because they are generating the link using the “Add to Cart” logic which automatically switches to external urls if those are present for the product type. That’s why you are seeing different behaviour between the blocks.
I can understand why this might be confusing but ultimately it comes down to the difference between what each button is using as the source for the button link.
I’ve created an issue for the Featured Product block because this sounds like something that would be useful.
The good news is there is a workaround that you can use for the featured product block to get it to link to the amazon link. The button in the block is editable including what it links to. If you click the button in the featured product block while in the block editor, you’ll see a toolbar with a button that allows for changing the link. You can change the link address to whatever you want and then save the post/page containing the block. From that point forward the block should link to what you set. Here’s an image showing what you click:
Hi there!
The All Reviews block requires the WordPress REST Api to populate the reviews on the frontend. It looks like your site has the WordPress REST Api locked down to only authed users which is why it’s not working on your site. Do you have a plugin installed that is restricting REST api requests to only logged in users?
I just tried installing the latest version of WooCommerce Blocks from the plugins admin page on one of my sites and it installed and activated without the error. This error happens when woo-gutenberg-product-blocks/vendor/autoload_packages.php is not readable in the environment the plugin is installed in. We have this check in place in case people install the development version of the plugin from Github (which needs to be built before it can be used).
I verified this file is available in the plugin on WordPress.org. So there’s a few possibilities for why you are seeing this error.
1. You have a version of the blocks plugin on your site that came from Github and maybe you are activating that by mistake instead of what you downloaded from WordPress.org.
2. The server your site is hosted on has permission problems with files installed from WordPress.org. If vendor/autoload_packages.php can be found in you installed copy of the plugin, then you’ll want to check with your host for why it’s not readable.
3. Something went wrong with the install of the plugin from WordPress.org and the required file isn’t present (and possibly other missing files). You could try deleting the plugin and re-installing.
There’s a very narrow set of scenarios that would produce that error. I hope one of the above helps resolve it for you.
Hi Phillip,
Where did you get the plugin from? Here on WordPress.org, through your WordPress Dashboard (plugins admin page), or Github?
Hi there,
This is the forum for Organize Series Core, not the Organize Series Grouping add-on. I see you’ve already created an issue in the repo for this add-on so I’m going to go ahead and close this.
Alternatively, you could use any of the available template functions to build your own dynamic series toc in your theme and customize to your liking.
It probably could be done with some custom code but it’s not something that is built-in.
If you’re familiar with WordPress filters and have some coding skills, you might be able to use the following filter (from the token_replace function) to accomplish what you want:
apply_filters('post_orgseries_token_replace', $replace, $referral, $id, $p_id, $ser_id);
A registered callback on that filter would receive:
– $replace The content being replaced.
– $referral Where the replacement is being triggered from (look at the function code to see what options these might be).
– $id – This is a dynamic value that might be post_id or series_id (better to use the following values)
– $p_id – the id of the post template being parsed.
– $ser_id – the id of the series template being parsed.
This should help you (or a developer if you aren’t a developer) get started on implementing something like what you want.
Isn’t that the Series TOC widget? If not, what is?
No it is not. The widget is found either via the widgets panel in the Customizer or in the Appearance->Widgets menu item.
Currently this field only affects the title for the post when displayed in the Series TOC widget. I just verified and it is picked up for the widget (but not any place else the post title is displayed). This is why the label is “Post title in widget”.
Hi Robin,
I do apologize but its still not clear exactly what you are wanting help with here. What I have gathered from your explanation here and the demo you linked to is that you want some way to the displayed items by an attribute that can be filtered by an accompanying filter controlled by the person viewing the items.
So for example, in the demo you linked to, you’d want to have a list of filters by “year of car” (which isn’t shown in the demo).
Since you’ve posted this as a support request in the WooCommerce Blocks repository I’m assuming your question is regarding the new All Products Block in combination with the various filtering blocks.
You can have multiple “Filter by Attributes” block setup for a page and each block instance can display terms from different product attribute taxonomies. So if “year of car” is a product attribute taxonomy, it should be available as an option for the block.
However, based on your question it appears you may be asking if you could use a custom taxonomy that is not a product attribute taxonomy for the filtering? If so, then currently there is no way to do this built-in or hooks available for injecting the custom taxonomy. The best approach here would be to build an additional Filter Block that is wired up to filter by your custom taxonomy.
Does what I wrote above indicate I’ve understood your request correctly?
Hi Lorenza,
You do not need to install the Gutenberg Plugin in order to use the WooCommerce Blocks plugin. The requirements are listed in the plugin description:
MINIMUM REQUIREMENTS
- WordPress 5.0
- WooCommerce 3.7 or greater
- PHP version 5.6 or greater (PHP 7.2 or greater is recommended)
- MySQL version 5.0 or greater (MySQL 5.6 or greater is recommended)
Visit the WooCommerce server requirements documentation for a detailed list of server requirements.
I hope that helps!
Hi @thibotus01,
If I understand correctly, you are wanting to add a paypal button on WooCommerce Products block so customers of your shop can click it to immediately purchase the specific product?
If I’m correct, currently the only ways to do this is to customize existing blocks by overwriting their registration or if you are fine with using the new All Products block, you can create a new block for your payment button and use the registerInnerBlock api to make that button available as an inner block for each product in the All Products Block output. We don’t have complete documentation for this extensibility yet, but you can see an example of it being used in this code.
Unfortunately, we can’t go into much more detail than that in this forum, but hopefully that is enough to get you started!
