October 5, 2012 at 11:04 pm #16856
I use WP 3.4.2, WC 18.104.22.168 and the latest Propulsion theme.
I have some positioning/customization and duplication issues on my product detail page (see link at bottom) as follows:
1. How do I remove all or portions of the SKU/Category/Tag line? For example, say I just want to show the SKU or SKU and tags.
2. I have used some of the fine support code found on this site to remove the display of related products (since they weren’t related to my liking). I also found the code to eliminate the related products and line separater graphic. Now I find the remaining upsells block needs additional white space to look better underneath the SKU/Category/Tags line. How is this extra space best accomplished?
3. When I recently upgraded to the 1.6.5 series of WooCommerce I started getting duplicate upsells that had bigger images than the upsells I was getting right after the SKU Line. I have tried Dude’s suggested code from Support Forum>Propulsion UPSELLS/RELATED PRODUCTS SHOW DUPLICATE AFTER UPDATE PLUGIN WOOCOMMERCE topic but this made no difference that I can see. How do I eliminate these oversize upsell duplicates on each product page that has upsells?
4. Can the question 3 fix be fixed in a manner that won’t break when the Woocomerce plug-in is upgraded again?
5. Will this duplicate upsells issue be fixed in a new Propulsion update? Timing on update?
Thanks in advance! This site is a great resource and makes me glad I purchased your theme.
Link to screenshot of product detail page outlining the issues and summarizing main issues/questions follows:
GregOctober 8, 2012 at 12:56 pm #93144
Once installed, this easy to follow video will show you the basics of Firebug – http://vimeo.com/20917974 and get you on your way to customizing your theme any way you want.
1) Without looking at the HTML code through Chrome Developer Tools or Firebug, it’s not easy to tell where anything is. Please look at this 6min video, and I guarantee you will be able to solve question 1 instantly by looking at your code. It’s easy.
2) After installing firebug or chrome developer tools, right click on the place you want to add more space to, and select Firebug from the right click menu. You will instantly see the selector name and margin-down: 20px; will do the trick. I am sorry, without looking at the code, it’s a guessing game.
3) Can you please show us the page where this is taking place? Once I look at the page I find the selectors and get to the right template file in order to investigate the issue.
4) Woo is an independent company. We can not dictate or forecast the future direction they will take , but be sure that we are here to support you. Also please understand that the direction Woo is taking is likely to benefit you in the long-run despite any short term inconvenience.
5) Once I see this issue first hand, I promise you that I will (a) document it (b) will do my best to fix it (c) send a full report to Kriesi, who undoubtedly is already aware of the issue from another support team member.
NickOctober 8, 2012 at 9:31 pm #93145
This is my first attempt to seek assistance on this site. I am not a developer. I am just trying to apply what I can from combing through this support site to fix some of the problems I have uncovered while trying to get my site prepared for launch. Where I can’t find answer on the support site my plan is to ask questions and seek answers and support where I can.
My site is not in production so it is unclear to me how I share my code/site with you. How is this accomplished in a secure manner? What kind of access do you need to investigate further? How do I show you the page or the code. This is all new to me.
Is the annotated screenshot I provided inadequate to see all the issues raised?
GregOctober 8, 2012 at 11:25 pm #93146
I don’t need backend access. But I do need to browse it as a regular visitor would, in order to see the code and tell you the css fixes to apply. Otherwise I have to create a demo version of the site based on your specification and hope that I put it together in the same manner as you did.
You can put it up in a separate directory, make the site private to keep google out, and hide the url in a url shortner or email me the url where i can see the pages u describe above via Firebug.
NickOctober 9, 2012 at 4:10 pm #93147
You can email me your email address at (Email address hidden if logged out) . While you send me that I will figure out how to gain you the access you require.
My issue 3 (the duplicate upsells) began after I upgraded WooCommerce to 1.6.4. Ever since that update I get the duplicate upsells displaying using Propulsion. I have seen others mention this issue on the support site also. Is there a fix for this or do I have to go back to using 1.6.2 or 1.6.3 WooCommerce and lose the other enhancements these newer versions provided? My other option would be to change themes, but I purchased Propulsion and want to continue using it, but this apparent incompatibility between the latest Propulsion and WooCommerce 1.6.4 and newer is really frustrating.
GregOctober 9, 2012 at 6:54 pm #93148
My email is usjahm (at) gmail.com . I don’t meed login/pw, just a url to see front end pages.
I understand about the hassle that sometimes the updates cause. There is absolutely no reason for you to immediately upgrade the live site after the release. Its often better to wait and see if there are any problems first. It’s never a good idea to install a plugin on a live site without testing it first on a clone of your live site where you do the development.
NickOctober 10, 2012 at 4:15 pm #93149
I have sent you an e-mail to arrange the access that you require. My site is not live yet so applying these upgrades has been more of a learning experience and delay so far and not a catastrophe. Now I see what can go wrong when WooCommerce makes changes that break parts of a theme that is non-Woo. The balance among all of the moving parts is more fragile than I thought it would be. This seems especially true between the theme and the e-commerce backend.
GregOctober 10, 2012 at 10:28 pm #93150
The topic ‘SKU/Category/Tag line, Upsell Block Spacing and Duplicate Upsell Elimination’ is closed to new replies.