[iamlard]

Thanks David!

I’ve amended the WordPress URL’s to ‘https’ and it seems to have solved it! If I get the same issue i’ll try your other suggestions – thanks!!

[iamlard]

Hi David,

Thanks for getting back to me – Can you confirm that you’re seeing ‘You may also like’ on our product pages? Sample page address is http://cloudsandcurrents.com/product/set-of-cherry-cocktail-stirrers/

Many Thanks!

[iamlard]

Hi,

I just updated to Neighbourhood 3.2.5 and, before the update, I was running the following additional css code alongside that generated automatically by the theme. I am trying to remove the related items and show just the ‘you may also like…’ section. The ‘you may also like’ section was displaying fine before I updated so just wondered if I now need additional code (or to change some of the following) after the update.

—-

Additional coding to custom style.css

figure .overlay {
display: none;
}
.product_meta .posted_in, .product_meta .tagged_as {
display: none;
}
#header-section #header{
background:url(‘http://cloudsandcurrents.com/cms/wp-content/uploads/2015/10/Header-Background-Image-1138.png’) no-repeat center top !important;
}
.posted_in{
display:none !important;
}
#header-section .header-menu .menu > .tb-welcome {
display: none;
}
.single-product .product-carousel.spb_content_element {
display: none;
}
#product-accordion .accordion-group:first-child {
display: none;
}
.woocommerce ul.products li.product figure figcaption {
display: none;
}

——–

And additional coding at the bottom of the Functions.php

/*
* wc_remove_related_products
*
* Clear the query arguments for related products so none show.
* Add this code to your theme functions.php file.
*/
function wc_remove_related_products( $args ) {
return array();
}
add_filter(‘woocommerce_related_products_args’,’wc_remove_related_products’, 10);

——–

Many Thanks!

[iamlard]

Thanks Kyle!

[iamlard]

Hi Kyle,

I’ve made the same error as Gaspard in updating Woocommerce before the theme.

I’ve just downgraded to Woocommerce 2.4 but still getting the image errors. Any ideas which file(s) relate to this image glitch? I’m guessing it’s something like ‘product-cat’ so I can just check that these individual php files are properly downgraded?! I’ve posted an image of what this looks like at present. Any ideas when the theme will become 2.5 compliant?

Many Thanks!

Attachments:

You must be logged in to view attached files.

[iamlard]

Hi again – I’ve used a backup of a functions.php file from my hosting so problem solved!

[iamlard]

Hi,

Sorry to reopen the same topic but i’ve just been amending the functions.php file and am now getting a parse syntax error also. I’ve had a good look but can’t see where my error lies…Is anyone able to take a quick look at my code please?

Many Thanks!

[iamlard]

Hi Rui,

Apologies for the delay in getting back to you – I passed this over to my hosting company who amended some settings in the back end of my site and it seems to be functioning perfectly now!

Many Thanks!

[iamlard]

Hi David,

Thanks for the info – I changed the URL’s to https:// and, having hit ‘Save Changes’, I got an error message saying that the browser couldn’t load the page. I haven’t been able to access the wp-admin screen since! I’ve contacted my host to revert to a backup of the database but that still won’t have solved the initial problem…

Many Thanks

[iamlard]

I didn’t have the plugin installed but I do now 🙂 Are there any specific settings within the plugin that need to be used in connection with the theme?

Also, I noticed when I received the mixed content warnings that the plugin ‘Google Tag Manager’ was causing a fatal error with the checkout. I’ve disabled this plugin which has fixed the problem but have you noticed any issues arising from using this plugin with the theme?

Thanks!

[iamlard]

Hi Kyle,

I’ve contacted Woocommerce and they’ve told me that a mixed content warning on the checkout page is telling Stripe that the page isn’t secure, hence why it’s not appearing. I’ve got an SSL certificate that’s been operational for over two years now but i’ve recently switched back to the original Neighborhood theme from a child theme that was externally coded. I’ve had ‘Force SSL’ option selected in Woocommerce checkout since the site began but now getting the following mixed content warnings from the Google Console:

Mixed Content: The page at ‘https://cloudsandcurrents.com/checkout/’ was loaded over HTTPS, but requested an insecure image ‘http://cloudsandcurrents.com/cms/wp-content/uploads/2015/02/original_engraved-wedding-hanger-120×178.jpg’. This content should also be served over HTTPS.

The insecure image referred to in the error is a generic product image dependent upon which product you’ve selected at the checkout, which has always worked, until now!

Any ideas as to how I can fix this?
Many Thanks!

[iamlard]

Brilliant!
Thanks very much Rui

[iamlard]

This reply has been marked as private.

[iamlard]

Hello,

I’m also getting fatal errors when trying to install the Neighborhood demo content. Error message looks like this:

Fatal error: Cannot redeclare class Swift_Import in /var/sites/c/cloudsandcurrents.com/public_html/cms/wp-content/plugins/neighborhood-importer/neighborhood-importer.php on line 303

Is this a server issue?

Also getting a message telling me that the Revolution Slider plugin needs updating for the demo content to function properly at the top of my screen but no update is available in plugins screen.

Any ideas?

Many Thanks!

[iamlard]

Hi Kyle,

Thanks – I haven’t changed any settings since making the update so i’ll see what woocommerce say