WooCommerce not displaying add to cart button – What can I do to narrow down?

Check you have a back-up before going much further.

Ensure the products not being added are visible, published, in-stock, enabled and not virtual.

‘bundled outdated copies of WooCommerce’ What could this mean?

Some themes include edited versions of the WooCommerce template files. These will be in:
wp-content/themes/your-theme/woocommerce/…
WooCommerce will use these in preference to the latest versions in
wp-content/plugins/woocommerce/…
When WooCommerce is updated, the theme author should update the theme versions of the template files. Ensure you have the latest version of the theme. Sometimes theme authors are busy elsewhere and don’t update their theme, in which case its time to look for another theme.

Other debugging steps to try:

Check the console (Chrome: control-shift-J) to check for javascript errors.

Deactivate all plugins except WooCommerce. If that fixes the problem, reactivate plugins one at a time to identify which one is causing the problem.

Some apparently deactived plugins can still be having an effect. Rename the plugins folder to say old_plugins, and reinstall WooCommerce.

Rebuild: Re-uploading all files & folders – except the wp-content folder and wp-config.php & root .htaccess files – from a fresh download of WordPress and plugins. Make sure that you delete the old copies of files & folder before uploading the new ones.

Post the url to the page so others can have a look.

I’ve checked for JS errors and deactivated all plugins except WC already..

By rebuild, do you mean delete all content and restore from a backup? This is an actively used WordPress that WAS working just fine – I have no idea how this could have happened. I’m terrified to make such a big change to her site.

– please post the url so others can have a look

– I’m not hopeful about this suggestion but I’m running low…
Repair the database by running the file at:
https://www.<mysite.com>/wp-admin/maint/repair.php
The first run gives instructions for the repair.

– consider hiring someone. Having full access makes fault finding easier.

– when you run out of things to try and go for a rebuild, the new site doesn’t have to be in the same place, so the old site can continue running. Create a subdirectory for the new site. Use a new database, fresh downloads of WP, WC and plugins. Export the pages, posts and products at Admin page / Tools / Export from the old site and import them into the new site. I’m sure getting it working will take time and effort. When it is working, see Pointing your home site’s URL to a subdirectory to switch the domain to the new site.

-Well I had a ‘coming soon’ plugin on but the url is prvtresidence.com. Temporarily disabled it for the next few hours.

-I’ll check out the db repair, but I’ve used this before and everything checked out so I’m not too hopeful…

-Gotta come clean with the embarrassing truth here.. I’m the guy that was hired. I’m a cocky sophomore CS student and I bit off way more than I can handle. Granted my quotes are always incredibly, incredibly cheap(sure aren’t going to draw them in with experience, yet) It’s the most stressful job I’ve ever done. I think I have to back out after I fix this issue and I am absolutely dreading writing that email.

you’ve been one of the most helpful resources I’ve gotten yet, and I’ve been dealing with this for weeks. Thanks a ton, lorro.

repair.php found no problems ??

Yep, bit of a steep learning curve but don’t let that put you off.

Your coming-soon plugin was activated before I could get to look at the site. If you would like to deactivate it, that may be helpful.

You’ve tried most/all of the debug steps, so ultimately you come to a point when there are no more things to try and rebuilding the site is a sensible option. As I say, rebuild it elsewhere so you don’t delete the original non-working site, then repoint the domain name.

When I got a bug I couldn’t fix, it took far less time to rebuild my site than I had spent trying to debug it.

Deactivated! Lemme know… Thanks

It looks like the theme is blanco version 2.8 but the current version is 2.9.2. The changelog says 2.9.2 adds compatibility with WP 3.9 and WC 2.1.7, so consider updating. Its always prudent to take a backup first. I can’t say updating will fix the problem.

Trying this out as soon as possible! Would have never thought of this!