linux4me2

It will take some work, but I think it’s going to be easier than adding a price field to the database for a restaurant plugin and altering the layout. For WooCommerce, it will just be a matter of altering the layout.

Note that WooCommerce has moved some of the layout settings to Appearance -> Customize -> WooCommerce instead of including them in WooCommerce -> Settings.

There is some documentation here that may help you. If you can’t accomplish all you need to with settings, CSS, filters, and hooks, you can also override WooCommerce template files by adding your own with the same names to your child theme’s folder.

It’s difficult–if not impossible–to help you without being able to see the site, but what is probably even better than having someone else give you the CSS is learning to use the developer tools in your browser of choice to view and change the CSS to get what you want, then add it to your site.

I don’t know what browser you’re using, but I’ll guess it’s Chrome since they have the largest market share. If you’re using Chrome, you can find a tutorial on their Developer Tools here. Firefox also has developer tools. Either will allow you to right-click an element on the page and “inspect” it to see what CSS it uses. You can alter the CSS live to see what happens and figure out what you need.

One suggestion, your changes for the Search page won’t be restricted to only the Search page the way you have them written, they’ll affect every page that has an h2 entry-title hyperlink. To restrict to a given page in CSS, you can use the page id, visible with the developer tools, to limit your changes to that page; e.g.:

.page-id-x h2.entry-title a {
  ...
}

replacing the “x” with the ID of the page, which your theme hopefully uses.

You might want to take a look at Year Make Model Search for WooCommerce. I haven’t used it, but I noticed it the other day when I was looking for something else. It seems like it might work, or serve as the starting point to develop your own.

@leander8890 The first thing I’d do is install the Health Check Plugin, which allows you to switch to a default theme–or the Storefront theme, since you’re using WooCommerce–for your user only, without affecting the production site to see if it is indeed a theme-related issue. The TwentySixteen theme is a good alternative for testing a default theme with WooCommerce. I know it doesn’t have the issue with images that you’re encountering with UShop.

The Health Check Plugin also lets you disable plugins to test. In your case, you’d have to disable everything but WooCommerce.

I will defer to Bogdan here because I don’t know what might be causing this, but it seems like the issue is with the server where you have MainWP installed, since it appears the updates are occurring on the child sites but your MainWP Dashboard isn’t keeping up via the Progress screen.

I would make sure you are not exceeding the defaults set for the MainWP -> Advanced Settings, Cross IP Settings, Per IP Settings, and Frontend Request Settings. Take a look at the Documentation for more explanation of each setting.

I’m wondering if there isn’t some other issue with the server MainWP is on that may be causing the issue. Is there anything showing up in the server or PHP error logs of the server that hosts your MainWP Dashboard when you try to update the child sites? For example, timeouts, exceeding memory, etc.?