Pro's woocommerce.php file is just gone now? huh?

Support
#1

So apparently after the update to 4.3.2, the file in the parent theme ‘woocommerce.php’ is just gone from existence now. The code in that file used to get the stack and then load the correct woo stuff - stuff I overwrite all the time in the child theme using the parallel file. So now that that file is gone from the parent, the child’s file doesn’t even load. Why on earth would you change something so fundamental to the way things work? The structure of those files is key to how at least one site for a major client functions and it is just rendered completely broken now.

This is madness. These latest updates are breaking all manner of things that have worked forever. Pretty disappointed in this to say the least. Can you please explain why this move was made and how it can be fixed? With an emphasis on the fixing part…

Just crazy…

UPDATE
So adding your old woocommerce.php file to the root directory of the child theme fixed my issue. The one that used to do this:
x_get_view( x_get_stack(), 'woocommerce' );

Now that I have placed that in the child theme, things work as they used to.

Still pretty shocked by this move to delete that file from the parent… Same questions apply from above still.

#2

Hello @simeoned,

Thanks for writing in! We have removed the file because, in the latest version, it is already redundant and adds file size to the whole theme. If you have modified the WooCommerce template files in your child theme, you will have to add the woocommerce.php file in your child theme which is why it works in your case.

Best Regards.

#3

Forgive me but… are you saying you eliminated a file which breaks how woo customizations worked in the past to save 4KB? Really?

Can you elaborate on the redundancy part of this please?

#4

Hello @simeoned,

The woocommerce.php file was needed in the previous versions because of how the stacks were built. We have rebuilt the theme from the ground up and in the latest version, the file is no longer needed. In your case, it created an issue because you have added custom WooCommerce modifications in the child theme that uses that legacy file. The woocommerce.php file is no longer needed because, with the new version of WooCommerce, you just have to declare WooCommerce support in the theme. You can check out the updated this updated documentation:

Best Regards.

#5

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.