Skip Navigation

[Resolved] woocommerce product archive page doesn’t show all products

This thread is resolved. Here is a description of the problem and solution.

Problem:
woocommerce product archive page doesn't show all products

Solution:
WooCommerce 3.3 introduces some changes in its API, which require, for example, that a theme declares compatibility in order to do something right. That includes, for example, a legacy way of managing their own product and taxonomy archives, and the product single page.

To do that, please add this line to your active theme:
add_theme_support( 'woocommerce' );

This support ticket is created 6 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 10:00 - - - - -
- - - - - - -

Supporter timezone: Africa/Cairo (GMT+02:00)

This topic contains 93 replies, has 4 voices.

Last updated by wabw media group 6 years, 7 months ago.

Assisted by: Mohammed.

Author
Posts
#693194
right.jpg

ok literally only two things change. I rolled back woocommerce to v 3.2.6 and rolled back toolset wcviews to v2.7.3 not a single other change was made whatsoever. now it works

the problem is with new WC and new wcviews. there is something not working in the hook.

#694205

do you see what i was saying?

#694366

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hello,

I'm able to see what you're saying Clearly now.

I went ahead and escalated your ticket to our 2nd tier supporters for further debugging.

Thanks,
Shane

#694413

sweet 2 weeks and we finally get someone to look at it.

#694416

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

I must apologize for taking so long as our forum has been quite busy.

However I did Identify that the issue is coming from Woocommerce, there must've been a change in how they do things because our Latest version of Woocommerce views works fine with Woocommerce 3.2.6 but it seems 3.3.5 mustve change something.

Thanks for your continued patience.

#697897

Lol agreed but thats what I said to begin with. I spoke with woocommerce before even opening a ticket here. its an issue with the wcviews hook not asking for the right information. hopefully you can provide me with a hotfix

#705704

It's me again.

I tried all ways to replicate what Shane sent me, and basically, the Database I received does not hold all the native mandatory WordPress tables, it has different prefixes, and throws errors on import.

It cannot be that your minimal WordPress install has a Database like this. No WordPress install can work with it.
See screenshot.

I allowed myself to install a Plugin on the site you provided (hidden link) and grabbed a copy, as there the database is intact.
I uninstalled the plugin again to leave no trace.

Your database still features at least 2 prefixes.
wpv3_ and wp_
Most are in the wpv3_ so I used that one.
wp_ prefix doesnt work.

However, if I disable all plugins but Toolset, WooCommerce and the WooCommerce Views, and make sure the setting in WooCommerce Views is correct (actually, it does not matter which) and load the URL hidden link I see a row of errors, related all to the themes/bootstrap-basic-child/functions.php.
Deprecated: Function create_function() is deprecated
Call to undefined function masterslider()
Call to undefined function masterslider()

So the situation is, that while Shane was able to see the issue on your live site, and I probably will see the same when I update the plugins on your live site, locally your site presents issues that make it impossible to debug.

What is also pointing to an exception is that no other user reports this issue, nor do we see it when we create our Reference Sites.

What we need to help you is a copy of a site that is built with Toolset and WooCommerce which uses native WordPress Databases, has no fatal errors in the custom codes of the Theme and uses a supported Theme.
The Theme you use is based on a public Theme, but we do not support Child Themes - with this I mean, we do not debug or add compatibility to child themes.

However, I see that you report this same issue for many sites and I understand that this points to a replicable issue.
But, no one of us can say how to replicate it.

All I know is that updating 2 plugins on a site that has an altered database, PHP fatal errors and several other plugins active, fails with a wrong output on the front end.
This site is not replicable properly locally due to the database issues.
If you have hardened your Database we need to know this.

Now, to help you in the best way possible I would like to involve the DEV in this straight away.
But, as well he won't be able to guess what happens. He needs to see it, and locally.

What I need is a Copy of a Database and a ZIP of a WordPress install where the issue is NOT yet visible.
Hence, like your site you provided here recently.
Where the issue is not yet visible because the plugins are not updated.

I need to be easily able to replicate this site.
Then, I need a link to the page where the issue should be visible and there should not be any errors related to other code.
I think we can use hidden link but we need to solve those errors there first.

Or, if you can outline me the steps you take to make this issue happen, then I can try to replicate it, but as previously was shown, it's not replicable if the steps are followed.

Let's not lose time in discussing what we see and get a copy for the developers ready.

Do you have a copy of a site which is not customized in this way?

I apologise that I need this, but even a experienced Developer will not be able to dig this issue without something to put his hands on.

#716334

Beda,

Those issues are not relevant to the problem. If you wish to recreate the issue. feel free here are the steps you can follow

1. create a fresh wordpress install
2. add any theme your heart desires\
2a. create child theme of said theme
3. install woocommerce
3a. add several products and categories
4. install toolset and wcviews
5. go to the child theme folder and create the woocommerce sub folder
6. create archive-product.php
7. go to wc views and select the use child theme custom template

reload your page
see no products

#733107

Let's keep in mind that with Toolset Layouts active, it does not pick up those templates - they cannot be chosen in the related settings in WooCommerce Views.
If you disable toolset Layouts you can pick them up.

Just noting this here in case someone else reads the post too.

And when I do that, then the archive (Shop) displays what I added to my child's theme archive-product.php file.
And, when I add a WordPress Archive View for the Shop, it applies.

I see all results, I can add their detail by shortcode, there are no issues with this.

I prepared a Duplicator for you to deploy on your local server - please edit it in a way that makes the issue happen, and send it back to me if required.

Although I cannot see how I can make this issue happen.
The child theme is a simple child of 2017 Theme, and there is just the one custom template in my child theme.
Then I applied the WordPress archive styled by Toolset and it's visible on /shop
hidden link

Please let me know what I missed.

#734300

We dont use toolset layouts and not sure how to install this duplicator to even see what you're on about. Please let me know how to install the duplicator so i can see what you have.

#734348

To install a Duplicator Package, you can download the folder I shared.
Then, you unzip it and will find two files, an archive.zip and an installer.php

These 2 files you place where you usually place a WordPress Install.
For example, in a local install under "htdocs" in a folder where your website lives.

Then you call your-site.tld/installer.php and follow the GUI steps.

There is a DOC about it here:
https://wordpress.org/plugins/duplicator/

If you are more familiar with Database manual editing you can find the SQL file within the Archive.zip.

#734398

looking now

#741006

Where you successful deploying that site?

#743492

yes also. if you want me to create the issue on stellamarisbooks.com i can. its easy to fix i can update the plugin and then revert it to fix the issue.

#743562

I don't understand.

Where you able to replicate the issue on the Duplicator that I sent you?

Please then just "Duplicate it back".
You can use the Plugin that is installed there.
It creates a tab where you can create packages. Those then need to be uploaded to a Google Drive Folder that you can "share with anyone who has this link".

Since the reply will be private, only me and you have access to it.

I want to solve this for you as fast as possible, but we cannot replicate the problem or a site where this happens.
The steps outlined did not lead to the issue.

I can ask a Developer if they are willing to look directly at your site if this is not replicable - but I fear they will not have much more success (and time).
But I can try.