Community Forums

Everything is back to normal now. Thank you!

Azam – I’m afraid I can’t fix it using that information. I need a little more guidance, eg. “Go to [file] and find [code] and change it to [new code].” Can you give me that, or is it too complicated?

Ludjon – thank you for your help, but unfortunately that didn’t work either. I still was not able to search backend Woocommerce orders.

I definitely didn’t expect you to spend the time to write new code for me! I was just hoping someone could tell me what code I needed to remove (or have someone take a look at) that was causing the theme to malfunction. Since I now know that it was the search code (trying to filter results to show only products, not blog posts,) that was causing the issue, I have simply removed that code from functions.php and the site is operating again.

Here is the code that was causing the issue below, in case anyone runs across this thread in the future:

//Only show products in the front-end search results
function lw_search_filter_pages($query) {
if ($query->is_search) {
$query->set(‘post_type’, ‘product’);
$query->set( ‘wc_query’, ‘product_query’ );
}
return $query;
}

Thanks!
Rebecca

Azam – I just deleted the entirety of the code in Tower-child CSS, and the issue still exists. Is the issue with something in the functions.php file? Or something else? I’d rather not delete everything in my Child Theme, if it’s just one thing causing the glitch.

I’ve spent hours going over all the code in my live site Child Theme, comparing it to the code in the staging site Child Theme, and I cannot find the difference. Can you please tell me what you changed/removed to make the staging site function? If you could please just point me in the right direction, I would be very grateful.

• This reply was modified 5 years, 8 months ago by rebeccaolson.

This must have been from long ago when the site was set up. All I’m asking if you can tell me which custom scripting is causing the conflict? Or do you not know?

Can you clarify *which* “custom scripting” you are referring to? I do not have a developer, so anything custom in my site has come from Tower to help address bugs/issues as they’ve come up over the years. Perhaps it isn’t necessary anymore, if you were able to fix it on the staging site – so I’m happy to remove the custom scripting that is causing the conflict, if you tell me what it is.