• Hi Guys,

    After the update to 4.4.0 today the font is not being inherited from the main site font, the ‘Sale’ icon is showing as a complete square and the ‘Next’ and ‘Last’ buttons are displayed differently.

    Could you take a look and let me know if there’s something I should do?

    Many thanks,

    Martin.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi abledragon,

    For the font issue, could you please add the following CSS to the “Custom CSS” field by navigating to the “Catalogues” tab and selecting the catalog:

    
    body {
        font-family: "Raleway" !important;
    }
    

    We visited the link that you shared and found the “Sale” icon to be displaying correctly. Could you please check if you’re facing this issue with a particular browser or is it same for any browser? We tested with Google Chrome Version 69.0.3497.100 and the catalog displays correctly on this. Also, the “Next” and “Last” button appear to be
    the same as they should, what difference do you find in these from the previous ones?

    Thread Starter abledragon

    (@abledragon)

    Hi there,

    Thanks for getting back to me.

    Adding that font-family CSS to the Catalogue custom CSS field made no difference.

    As you can see from the screenshots I’ve uploaded below, the font selection is being corrupted outside of the UPC areas and on non catalogue pages as well as within UPC areas.

    The Sale icon and the next and back buttons are rendered incorrectly on both Firefox and Edge – see the screenshots below.

    On Chrome while the ‘Sale’ icon does not show up as a square there has been some additional padding added, moving the Sale icon away from the div edges. Also the back and next buttons are not appearing as before, and the font family selection has been corrupted both within and outside UPC areas.

    I have uploaded 6 screenshots for you to review:

    Screenshot of Almerispa Footer font with UPC Deactivated

    Screenshot of Almerisap footer font with UPC Activated

    Screenshot of non-catalogue page font with UPC activated

    (I can upload an image of this font with UPC deactivated if it would help)

    Screenshot of Sale icon and next buttons on Edge

    Screenshot of Sale Icon and next Buttons on Firefox

    Screenshot of Chrome UPC page

    Please note on the Chrome screenshot I forgot to circle the next and back buttons.

    Cheers,

    Martin.

    Hi abledragon,

    Thanks for your cooperation and for providing us with the extra information t help us troubleshoot this issue faster. We tried adding the custom CSS we gave you previously via the browser console and it made UPCP to switch to the said font. You could try adding the following custom CSS bu navigating to the “Catalogues” tab and selecting the catalog and see if that makes a difference. Also, to make the font available for all the elements on the page,we recommend adding the following Custom CSS and see if this fixed the issues:

    
    html, .prod-cat-container {
        font-family: "Raleway" !important;
    }
    

    Since the page renders correctly on Google Chrome(we tried with Version 69.0.3497.100) but not on Edge, Firefox or IE, so the issue seems to be browser specific. We’ll take a more deeper look into the issue and add a fix for this in a future update to the plugin.

    Thread Starter abledragon

    (@abledragon)

    Hi there,

    Many thanks…

    I added the CSS to the catalogue’s custom CSS field. This does fix the font problem for all elements on the catalogue page, but not on the other pages on the site. I can send screenshots again if you like.

    This affects Chrome, Firefox and Edge – all non-catalogue pages are rendering with the browser default font for body text, menu and footer areas in all of those browsers. H elements are not affected – they are rendered in the correct font.

    Just an observation: the CSS you sent me defines the font that I’m using on that site, but not everyone is using the same font – so that is not a universal fix.

    Also, just to confirm re Chrome: as well as the incorrect font style on the non-catalogue pages, the page still does not render correctly, because the next/back buttons are not rendering with the box and shadow around them. I have rolled back to 4.3.11 on the other UPC sites that I’m managing and the screenshots below compare the two versions:

    Next-Back Buttons Version 4.3.11

    Next-Back-Buttons Version 4.4.0

    Cheers,

    Martin.

    Thread Starter abledragon

    (@abledragon)

    Hi guys,

    Just to let you know that I’ve now rolled back to 4.3.11 on the Almerispa site as well.

    If you need me to update to 4.4.0 to check on fixes, let me know.

    Cheers,

    Martin.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Some problems after update to 4.4.0’ is closed to new replies.