Hi PlanZbyZola! Unfortunately, we are not able to replicate the problem, with a Posts module, Query on Taxonomies (example “Black”) and everything is fine: https://undsgn.d.pr/mW7wos
Can you please give us more info to understand the scenario?

What version of wordpress are you using in the example?

It’s visible in the first second of the video: WordPress 5.3.

The problem turned out to be caused if the products “Catalog visibility” is set to “Shop Only”, when changed to “Shop and Search Results” the build query functions for products of the designated taxonomy. This wasn’t the case in Uncode v2.1.0.

When using the Posts module with Query to Products the WooCommerce settings are not influential, anyway, if you think this is a bug please explain all the steps to replicate the scenario and the issue. Thank you!

ps: tried to replicate but probably we are in different scenarios.

Hello, I made a new WP site with nothing in it and have the same results. WP v532,Woo v381, Uncode v226, Uncode Core v224. If a simple products Catalog Visibility is set to Shop Only and I have a page using a build query in the posts module for products of the relevant Taxonomies, the page says “Nothing Found.” If I switch the products Catalog Visibility to Shop and Search Results, then the build query is successful and the product displays correctly.

Hi PlanZbyZola! Ok issue replicated but it’s not something we can suggest a quick fix here, from the new main update of Uncode there will be a new option inside the Build Query option to control the Product Visibility settings. Right now if you want to revert the functionality in uncode-core/includes/vc_extend/modules/uncode-index/extend.php, change about line 263:

$terms_to_exclude = ( 'yes' === get_option( 'woocommerce_hide_out_of_stock_items' ) ) ? array( 'exclude-from-catalog', 'exclude-from-search', 'outofstock' ) : array( 'exclude-from-catalog', 'exclude-from-search' );

to:

$terms_to_exclude = ( 'yes' === get_option( 'woocommerce_hide_out_of_stock_items' ) ) ? array( 'outofstock' ) : array();

got it thanks

Hi PlanZbyZola and thank you for the confirmation!

ps: if you are interested to test this before the public release please drop us a message from our profile page https://themeforest.net/user/undsgn

Yep that fixed it, thx

I am on Uncode 2.2.3

I have deleted that old Envato plugin and I think that fixed it, for anyone else having this problem. Also updated all of my plugins.

Hello,
if you run an old version of Uncode, you can’t use the patch, since it is released for Uncode 2.2.2, and it isn’t compatible with other versions.

If you run a child theme, you have to check that the changes you made in your child theme are compatible with the updates included in Uncode: if you call functions no more available in Uncode, for instance, you will find some issues. I can only recommend to check the differences between the file in your child theme and the original ones and check what has changed.

Anyway let me kindly remind you that if you need support for this kind of things it is offered in our Help Center, there we have a completely dedicated support team, please submit a ticket so we can check your installation and support the solution privately! Thank you! https://support.undsgn.com/hc

Hi,

So what are you saying; that we pay you for a theme, WordPress releases an update, which in turn causes the theme to break…and now we have to pay you again for the support to fix it? As we have no way of updating it in the normal way, as paid for in the first instance?

That doesn’t seem fair to the customer.

David

No, I haven’t said that, sorry: the update is completely free, lifetime, but if you need further support for extra customizations you made to the child theme, we can’t provide support here unfortunately. I hope this time is clearer and sorry for the confusion

You’re free to update Uncode by following the instructions available here: https://support.undsgn.com/hc/en-us/articles/214001205-Theme-Update

Let me know, best

Ok, but that update option is not showing there though, which is why this site is still on Uncode 1.7.6.1….hence why this isn’t making much sense? It just says ‘Themes up to date’

We haven’t edited the Child theme for this, just used it to edit Theme Settings, as is standard practice right? Besides, when I switch it now from Uncode Child Theme to Uncode there’s no difference front end.

We just want to get this updated to the latest Uncode version, register our Purchase of it, get auto updates and get this patch to fix the logo/image issue…but I can’t see any way of doing that!

Hello again.
I can’t know, from here, the reason why you don’t see the update unfortunately, however in the article I provided above it is also explained how to update via FTP, so that could be a solution

About standard practices: you can edit a theme with a child theme, sure, but after each update you have to make sure your changes are compatible with the update itself, otherwise you can’t update neither the theme nor Wordpress… nor the plugins. We do the same with our WooCommerce customizations: after each WooCommerce update we check that the customizations we made in Uncode are compatible with the new update of WooCommerce, since they could have changed some functions. The working of a child theme is the same.

Ok great, thanks. So if we switch it to the Uncode Parent Theme, update that, the auto updates will continue over time after the theme purchase is verified right?

Hello
You don’t need to switch to the parent theme. Child theme inherits the functions it needs to be updated. And yes, once you register your purchase code, you’ll be notified when a new update is available and you’ll be able to update. But, once again, only if your child theme is well developed and it doesn’t block the behaviours of the parent one.

We haven’t made any changes to functions.php or anything like that for the Child theme. We have only edited Uncode theme settings. So therefore we should just use the parent theme right?

I switched to Parent theme, updated to the new Uncode and successfully verified the theme purchase. The site looks normal now, so theoretically we don’t need to use the Child theme right? I can just leave it set to the Parent theme.

Yes, for sure, if your child theme didn’t contain any customization you can definitely use parent theme. Glad to read that everything works fine now.

Thanks for this.

Although, does the verification cause an issue for migration? Our other themes haven’t, but the Uncode site is causing a 504 gateway error after migration.

I’ve tried Exporting the site both with and without the Purchase Code entered but the homepage of the website can’t be accessed. It just causes a 504 error, while all other pages are accessible. The backend works and it is only Uncode plugins that cause the problem when they are activated.

Please let me know, we just want to get this site transferred over asap.

David

Hi david_h__! No the Registration doesn’t cause an issue like this. Unfortunately, we don’t have other users reporting the same and I don’t have previous test cases, the 504 is not an error of the theme. The only reference I have about 504 was a user that got this error with Google Fonts. “The 504 Gateway Timeout error is an HTTP status code that means that one server did not receive a timely response from another server that it was accessing while attempting to load the web page or fill another request by the browser.”. What method you used to migrate the site? Did you activate the debug mode?

Yeah it’s a strange one. I’ve narrowed it right down to the Uncode WPBakery Page Builder plugin, when that’s activated is when the 504 error on the homepage occurs. Which I guess makes sense with what you’re saying as it’s coming from an external source/server possibly?

Is there a built in debugger? I tried the wp-config file method using: define( ‘WP_DEBUG’, true )

This just takes the 504 error away and shows a totally white screen! :s

It’s not what I’m saying, the one above it’s the official Google definition of 504 error. Did you try to change for a while on the homepage to verify the problem is not some element in the actual homepage?

So yeah you’re right it was an element from the homepage. I methodically went through and rebuilt the page block for block, turns out it was the Author Profile avatar element…as it was set to use the Gravatar profile image of the page author. I suppose the external source was Gravatar itself on this occasion?

I switched this to just be a custom image to replicate Gravatar, so I don’t think the end users will notice for now! But any idea why that would be happening? Seems pretty odd. I’ve gone ahead and completed the migration via DNS as normal which went through as expected this time.

Hi brousse! Did you update to the last Uncode 2.2.3 if you updated to WordPress 5.3? Please install the update or apply the quick patch here: https://support.undsgn.com/hc/en-us/articles/214092169

thx. but the update does not work. And I do not know how to do the quick fixes. I do not code

Hello leoro123,
very strange issue, nobody else reported it so far. Please, if possibile, put this PHP code in the file functions.php of your child theme:

add_action( 'init', 'uncode_support_add_tinymce_shortcut_plugin', 1000 );
function uncode_support_add_tinymce_shortcut_plugin(){
    remove_filter( 'mce_external_plugins', 'uncode_add_tinymce_shortcut_plugin' );
}

and contact our help center https://support.undsgn.com/hc (ask to be escalated to a developer) so we can better check, since we are not able to replicate your problem, even if we guess it is related to the function suggested here above.

Let me know, best