Forum Replies Created

Viewing 30 posts - 1 through 30 (of 30 total)
  • Avatar: calebweeks
    calebweeks
    Participant
    June 30, 2017 at 06:26

    Hi Rose – I appreciate your reply (as always)!

    I know you’ve had to copy/paste your reply about “Unfortunately, it is not possible to show attributes in the old style, because it was changed by woocommerce. But you can change http://prnt.sc/f5fgm0 to http://prnt.sc/f5fh1a in /legenda/woocommerce/cart/cart.php.” – I’ve seen it in other answers on the support forum.

    What is odd about this, however, is that the Variations ARE showing up for some products and not for others (which are the exact same type of product: a Variable product).

    So in our case, it is possible to show attributes in the old style as they are still showing for many of the products (screenshot)

    Do you have any idea why it is showing for some and not for others(?) and if there is anything we might do about that to have it show for all?

    Thank you so much!

    Avatar: calebweeks
    calebweeks
    Participant
    June 27, 2017 at 18:58

    Thanks, Rose – that did it!

    Thank you so much! 🙂

    Avatar: calebweeks
    calebweeks
    Participant
    June 26, 2017 at 19:02

    P.S. Private content includes SCREENCAST which shows what is going on. Thank you!

    Please, contact administrator
    for this information.
    Avatar: calebweeks
    calebweeks
    Participant
    June 26, 2017 at 19:00

    The Subject line on the above post is un-related and was accidentally posted – I was unable to edit or re-post! The content of the post, however, is still accurate and requires attention as able. Thank you!

    Avatar: calebweeks
    calebweeks
    Participant
    June 26, 2017 at 18:22

    Hi again, 8Theme Team,

    I inspected the legenda > woocommerce > archive-product.php file in the theme files. Do you think this has to do with this code:

    <?php if ($page_heading != 'disable' && ($page_slider == 'no_slider' || $page_slider == '')): ?>
    	<?php et_page_heading(); ?>
    <?php endif ?>
    
    <?php if($page_slider != 'no_slider' && $page_slider != ''): ?>
    	
    	<?php echo do_shortcode('[rev_slider_vc alias="'.$page_slider.'"]'); ?>
    
    <?php endif; ?>

    Is that code supposed to be in there for product archive pages? I don’t see any way to “disable” the “Page Heading” or where to control the rev_slider_vc alias=”‘.$page_slider.'”

    Thanks so much for writing when able!

    Avatar: calebweeks
    calebweeks
    Participant
    May 23, 2017 at 04:03

    Hi Rose,
    Thanks, yes – it looks like all is well!
    Did you guys change something? I don’t recall changing anything – it just started working/showing again.
    Thank you either way – we are all set!

    Avatar: calebweeks
    calebweeks
    Participant
    April 29, 2017 at 04:47

    Hi 8Theme,

    Update: The “No Products Were Found” error was connected to the WooCommerce Point Of Sale Plugin.

    Comment: The Ajax search is still showing “Hidden” Products, though – any idea if this can be reversed?

    Thanks, guys!

    Avatar: calebweeks
    calebweeks
    Participant
    April 20, 2017 at 19:47

    Thanks for the update, Jack. We’ll look forward to using it when it arrives!

    Avatar: calebweeks
    calebweeks
    Participant
    April 18, 2017 at 17:45

    Hi Rose – thank you, again, for your kind and quick replies to our thread 2 weeks ago! I am also a license holder for Xstore, so I really appreciated the immediately update to Xstore for WooCommerce 3.0 compatability, etc.

    Any news on Legenda?

    Thanks for writing when able!

    Avatar: calebweeks
    calebweeks
    Participant
    April 7, 2017 at 04:19

    Hello again,

    WooCommerce just pushed out an update (3.0.1) which fixed this issue. Consider it resolved ??

    Thank you!

    Avatar: calebweeks
    calebweeks
    Participant
    April 5, 2017 at 16:37

    Hi Rose – thanks so much for the update.

    Question: Is there any way Legenda could keep up-to-date with WooCommerce releases in the future?

    I know the WooCommerce 3.0 has been in development since August and had 4 beta versions since December (4 months ago) along with 3 Release Candidates in March with an upgrade date of April 4th.

    Question: Does the 8Theme team wait for the actual release to test compatibility?

    I ask because I am aware of the challenges in theme compatibility but also mindful of other theme developers who worked with the release candidates to introduce WooCommerce 3.0 compatibility before the release came out.

    Also, with WooCommerce 3.0 running a content update, is it even possible to “downgrade” or rollback to WooCommerce 2.6.14 without restoring from a backup?

    Thanks for any replies you can give, and thanks, of course, for Legenda, XStore, etc.! 🙂

    Avatar: calebweeks
    calebweeks
    Participant
    March 28, 2017 at 17:54

    Hi Olga,

    Thank you – so sorry to bother you on such a simple Theme Options setting!

    Thanks so much for taking the time to reply and send a screenshot.

    I’m all set. 🙂

    Avatar: calebweeks
    calebweeks
    Participant
    March 28, 2017 at 01:49

    Thank you, Olga! That worked. Really appreciate it!

    Avatar: calebweeks
    calebweeks
    Participant
    February 26, 2016 at 15:24

    Hi Eva,

    That seems to do the trick now for what I need. The Ken Burns effect doesn’t seem to acknowledge/calculate the boxed width but having a static image is all we need so that’ll do.

    Thanks again. We can consider this ticket resolved. 🙂

    Avatar: calebweeks
    calebweeks
    Participant
    February 23, 2016 at 22:38

    The “display: inline-block;” did it. Thanks, Robert!

    P.S. Do you think Royal will add this as a default in a future theme update? It seems like the thing (have the text centered like the right nav-bar element but no worries if we just do it manually.

    Thanks, guys! We can close this ticket.

    Avatar: calebweeks
    calebweeks
    Participant
    February 23, 2016 at 15:12

    Thanks, Eva.

    Is it strange that it is needs a “margin-left: 40px;” in order to give the appearance of being centered? I would have figured it would be able to receive a “text-align: center;” – I will use the margin-left but do you know why it is not taking the text-align: center rule?

    Thanks again!

    Avatar: calebweeks
    calebweeks
    Participant
    February 18, 2016 at 21:58

    Link to screenshots:

    • 27″ wide display: http://cl.ly/1Y1W032y1t0U – background image is stretched way too far
    • laptop width: http://cl.ly/1R363A2Q0t1M – background image is at more appropriate size but just illustrates that the calculation is not taking into account the 1200px and is using instead the window size

    The max-width the slider should be is 1200px and then it should calculate the background image size from there (not the browser window size).

    Avatar: calebweeks
    calebweeks
    Participant
    February 18, 2016 at 21:57

    Hi Eva,

    Thanks – yes, happy to take some screenshots.

    Attached are 2 screenshots: the first is taken on a wide display (27″) and the second on a laptop width. You’ll notice that the background image gets stretched way too far on the wide display but is more appropriate on the laptop display (though still not according to the 1200px boxed width).

    Does that help a little better?

    Basically, the Slider Revolution should should be contained within the content, just like the Slider that is below the example that I am using: it is contained within the padding of the Visual Composer Row. Usually I would say, “Stretch Row” and it would just stretch to the edge, but this isn’t working for Slider Revolution.

    Thanks for any insight you can give (now that you see what I mean, hopefully a little better).

    Thanks again!

    Avatar: calebweeks
    calebweeks
    Participant
    February 18, 2016 at 15:16

    Hi guys,

    Thanks for your reply! I’ll do my best to clarify just a little bit more and have added credentials to the section below.

    Comment: So on a larger display (an iMac 27″ for instance), the top slider background image gets stretched too large – it seems to be calculating it’s width based on the “stretch content” width instead of just 1200px. The slider below this, of course, doesn’t have the row stretched but therefore has the padding around it which is what I am trying to get rid of by selecting “Stretch Row” in the Visual Composer Row Settings.

    Thanks for having a look and seeing what you can do!

    As a reference, the slider in the Page Title/Page Heading area (at the top of the Page) is performing perfectly – that’s what I’d love to see the sliders within the page content do, if possible.

    Thanks again, 8theme!

    Please, contact administrator
    for this information.
    Avatar: calebweeks
    calebweeks
    Participant
    February 11, 2016 at 17:45

    Perfect – works great. Thank you, Robert!

    Thank you, 8Theme!

    Avatar: calebweeks
    calebweeks
    Participant
    September 4, 2015 at 23:27

    Hi sandro7555,

    Removing the file in legenda/woocommerce/single-product/add-to-cart/variable.php is what did it for me.

    Do you see that file in your install?

    Avatar: calebweeks
    calebweeks
    Participant
    September 3, 2015 at 14:57

    Thanks, Jack!

    I’ll leave the cart-item-data.php file in there and look forward to the next Legenda update.

    Thanks again for great your great support!

    Avatar: calebweeks
    calebweeks
    Participant
    September 2, 2015 at 23:20

    Hi Eva,

    Wow – that fixed it!

    But I am equally embarrassed that the file was still in there – I don’t know how I overlooked it! And I am sorry you had to login yourself via FTP to help when that should have been something I could handle.

    Thank you again. Everything is working.

    As to the other file and why these did not get removed: why did these files not get removed (do you know) when I updated via the Envato Toolkit plugin?

    Lastly, do I need to delete the other file that was not removed: the cart-item-data.php? Do the screenshots I attached in #83851 indicate it would be more helpful to leave that file in there (as it is still presently in there)?

    Thanks again for all your help, and great work knowing what this was and fixing it right away for me/us!

    Avatar: calebweeks
    calebweeks
    Participant
    September 2, 2015 at 12:54

    Supplied. Thanks guys!

    Please, contact administrator
    for this information.
    Avatar: calebweeks
    calebweeks
    Participant
    September 2, 2015 at 09:23

    Hi Eva,

    I do the Theme Updates through the Envato Toolkit.

    I do see that in version 2.9 (August 15th) you indicated in the changelog: “DELETED legenda/woocommerce/cart/cart-item-data.php”. That file, however, is still present in my copy of Legenda 2.9 when upgrading via the Envato WordPress Toolkit.

    The other file, “legenda/woocommerce/single-product/add-to-cart/variable.php” is not present in my copy of Legenda 2.9.

    In order to test, I removed the “cart-item-data.php” file and tested the variable products, but the products were still not working (as described above). Also, without without the “cart-item-data.php” file in my version of Legenda 2.9, the mini-cart was displaying funny (see screenshots: WITH cart-item-data.php file and Without cart-item-data.php file). Can you re-create this on your end?

    Thanks (again) for writing when able! The main goal is to have the Variable products working with their attributes, just like they have been all these months as I can’t seem to find any indication that WooCommerce no longer permits custom attributes (as described in prior messages in this thread above).

    Avatar: calebweeks
    calebweeks
    Participant
    September 1, 2015 at 20:29

    Hi Eva,

    Can you explain a little more about where this changed in a recent WooCommerce update?

    I could not find where it is documented that they no longer accept custom Attributes. It still appears as an option even with WooCommerce 2.4.6.

    For instance: Add New Product > Attributes > Custom product attributes > Add then gives the “Name” field and “Value(s):” field with the instruction: “Enter some text, or some attributes by “|” separating values”

    This is all we’ve done. Our Attributes are entered this way – why would I need to go back and change this if it is still an option in WooCommerce 2.4.6? I don’t see why or where this was/would be changed in WooCommerce 2.4.x.

    Thanks again for your help!

    Avatar: calebweeks
    calebweeks
    Participant
    September 1, 2015 at 17:11

    Thanks, Jack for your reply.

    Will this be fixed in a future version of Legenda do you know?

    Thanks again for writing when able! 🙂

    Avatar: calebweeks
    calebweeks
    Participant
    September 1, 2015 at 15:48

    Hi Eva – thank you for the quick reply and temporary solution to the Attributes/Variations.

    Question: Do I need to go in and do this for all Variable products? Is this loss of functionality due to a coming update from 8Theme for Legenda?

    Do you know if the 8Theme Team will be updating Legenda so that the Attributes & Variations work again (without having to create them all in the Products > Attributes section and then re-adding them)?

    We have 62 Variable products so this could take a while if I have to do each one manually.

    Thanks for letting me know when able!

    Avatar: calebweeks
    calebweeks
    Participant
    September 1, 2015 at 09:00

    Thanks, Eva – it seems to have gone away. What did you end up doing to fix it?

    Avatar: calebweeks
    calebweeks
    Participant
    June 12, 2014 at 19:07

    Hi Eva – thank you for such a quick response!

    If I have the Settings > Visual Composer > Design Options enabled (and set to 35px), can you think of a reason why the Elements bottom margin would not be 35px on the site, thus requiring the Separator element be included?

    It would be preferable for me to not have to do the Separator but instead have the global setting apply. For some reason it is not applying. I have cleared the cache, etc. etc.

    Thank you for any ideas (if you have any) or a reply when able! 🙂

  • Viewing 30 results - 1 through 30 (of 30 total)
Viewing 30 posts - 1 through 30 (of 30 total)
We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.