- June 15, 2018 at 12:38 pm #169282
Colorlib Support – we established it was the newer versions of woocommerce plugin right from the start that wasn’t compatible with the theme. Hence the title of the thread “Woocommerce sidebar moves to side”.
kkr17 – Your help on this is awesome. I will try your suggestions later (when I get 5 minutes) but it sounds like you’ve sorted it. Many many thanks. I will report back.June 15, 2018 at 6:36 pm #169339
Firstly thank you for the pointers. On my website I found the following happened…
Firstly I followed your exact code suggestion and the main content area and sidebar became part of the footer (though they were next to each other so a good starting place).
After experimenting a bit I found if I just used
<main id="main" class="site-main" role="main"> <header class="woocommerce-products-header">
and didn’t include
<div id=”primary” class=”content-area <?php echo of_get_option( ‘site_layout’ ); ?>”>then it works. All good, archive pages fixed!
Not such good news. Adding your exact code displayed the content area twice (one under the other) with the sidebar next to the bottom one. I have played with it for a couple of hours and can’t get this one to display properly.
Any further suggestions on fixing single-product.php would be very gratefully received… please!June 16, 2018 at 11:15 am #169395
Just add the bits that worked for you on the archive page to the single product page
I enclose my changed php files I simply added them to the woocomerce folder within my child theme
hope it helpsJune 16, 2018 at 11:17 am #169396
Well unfortunately it won’t let me upload the 2 files… but again.. just reproduce what you did on the archive page to the single-product page.. then everything will work.
Hope your problems are solved now 🙂June 16, 2018 at 11:46 am #169397
Unfortunately no. I’ve tried many combinations on the single-product page and I can’t get it working.
Here is the archive page (now working)
Here is the product page (still broken)
Any help much appreciated.June 16, 2018 at 7:08 pm #169463
Sorry I was out and about…
I took the following screenshots yourarchive… here you can see that the ::after appears after your sidebar
and yoursinglepage >> the ::after appears directly after main and before the sidebar
Try to switch the sidebarhook with the after main content hook – maybe that helps. Otherwise I have unfortunately no ideas – tried CSS but no success. You need to get the sidebar inside of your wrapper.
I hope I was of some help being no expert at all.. just another shop owner..
* woocommerce_after_main_content hook.
* @hooked woocommerce_output_content_wrapper_end – 10 (outputs closing divs for the content)
do_action( ‘woocommerce_after_main_content’ );
Attachments:June 17, 2018 at 4:41 pm #169620
kkr17, you are an absolute diamond!
Switching the sidebar hook with the after main content hook has worked. I cannot thank you enough for your advice on this.
Now we have identified the problems it would be good if Colorlib can update the theme so it’s not necessary to manually override these two woocommerce files in order to get it working properly.
We should not mark this as resolved until the theme has been updated and is truly woocommerce compatible.June 17, 2018 at 4:50 pm #169621
I attach the two override files for everyone else who needs them.
Upload these to wp-content/themes/yourchildtheme/woocommerce folder.
Obviously change the file extensions from txt back to php
Attachments:June 17, 2018 at 5:53 pm #169623
you realy made my day calling me a diamond. Glad that I could help. Wish you all the best for the games tomorrow – may Great Britain play better than us germans today 🙂June 18, 2018 at 11:07 am #169807
@kkr17 Nice work providing the solution to this issue here.
Please feel free to contact us again in the future.
SupportJuly 15, 2018 at 10:05 pm #174436
Any news on a fix from the developer?
I see you’re still saying it works with WooCommerce on the Unite page https://colorlib.com/wp/unite/ which is not true.
Please chase the developer for a fix.July 16, 2018 at 10:35 am #174566
Thanks for keeping in touch with us.
We have already notified the developer about this but creating a fix for this kind of issue would take a bit of time as it needs to be tested on multiple browsers and tested with different plugins to ensure that the fix works properly with WordPress.
SupportJuly 16, 2018 at 5:23 pm #174614
The theme already works fine with WordPress as we’ve discussed, it’s the WooCommerce side of things that needs attention. Four months since this was raised as an issue and still no word from the developer, despite kkr17 and myself pointing out where the problem is.
As an interim measure you should remove the text from the Unite page that says it works with Woocommerce. Or at least change it to say works with WooCommerce up to version 3.2.6.July 17, 2018 at 5:18 am #174714
Sorry for this problem, it will be fixed definitely
Guys, you should not forget we are doing all this stuff absolutely for free, we have not 3 or 4 products and keeping them all time updated is not an easy job as seems 🙂
You must be logged in to reply to this topic.