Style issue since last update #2 - by Bas Kling

Solved3 replies2 participantsUpdated by Rose Tyler

  • Avatar: Bas_Kling
    Bas Kling
    Participant

    Hi,

    since updating from before XCore 3.2.4, I’m faced with my styled wishlist button, as shown by these screenshots on mobile (Galaxy s9+, Android v10, Chrome 88.0.4324.93):
    Old version (all was fine):https://prnt.sc/xtqgjq
    After update to 7.2.4.1: https://prnt.sc/xtqi5w and https://prnt.sc/xtqjsg

    I cannot find the reason why nor can I fix it. Can you please have a look?
    Credentials in private

    Please, contact administrator
    for this information.

    3 Answers

    Avatar: Rose Tyler
    Rose Tyler
    Support staff

    Hi,

    You positioned the button using custom CSS code. We’ve changed the code – https://prnt.sc/xuvskc , check the button now.

    Regards

    Avatar: Bas_Kling
    Bas Kling
    Participant

    Hi Rose,

    thanks.
    Yes. Because your form cart element collates everything from Woocommerce (variation, stock, cart button) within that block, we needed to use code to reposition some elements and align with wishlist. But we couldn’t make out why everything was working fine in the previous version of XCore and fumbled up afterwards.

    Is there any appetite to offer Xstore users more control over these elements in the (near) future? I’ve submitted a feature request about a year ago with little response, but I doubt that anyone really understood what it was for. Particularly on mobile, the standard element alignment does’t paint a pretty (enough) picture…

    Avatar: Rose Tyler
    Rose Tyler
    Support staff

    Hi,

    Please post this request and explanation here – https://www.8theme.com/taskboard/ Support team can’t affect the work of dev team, do it all depends on the requests on the taskboard. Jack Richardson is our dev team member, so you need to consider this with him – https://www.8theme.com/taskboard/

    Regards

The issue related to '‘Style issue since last update #2’' has been successfully resolved, and the topic is now closed for further responses