Support » Theme: Bento » Admin vs. Visitor

  • rhondelon

    (@rhondelon)


    We are experiencing a different view after upgrading from 1.8 to 2.2. This different view does not occur to the average user viewing the website, it only occurs when logged in as an admin using a WYSIWIG style editor. I assume that this is either a difference in processing order for admin.php or possibly a style conflict. If you could point me in the right direction.

    Thanks,
    Brian

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Theme Author satoristudio

    (@satoristudio)

    Hello Brian, thanks for choosing Bento! Could you please attach a screenshot of the part(s) which look different for the loggen-in users?

    rhondelon

    (@rhondelon)

    I’m going to revise. The difference between the two appears to be in Chrome, in normal mode vs. Incognito and a colleague reports the same in Firefox.

    Incognito it appears fine and also in Edge it appears fine as shown in this picture
    https://marklandia.cf/wp-content/uploads/2019/09/incognito.png

    However, in normal Chrome, it gets a java error and is missing an element as well as the down carrot on menus.
    https://marklandia.cf/wp-content/uploads/2019/09/logged-out.png

    I also noticed that there are a few errors in the JS related to the missing picture element.

    Uncaught TypeError: $bento_isocontainer.imagesLoaded is not a function
        at HTMLDocument.<anonymous> (theme-scripts.js?ver=5.2.3:203)
        at i (jquery.js?ver=1.12.4-wp:2)
        at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
        at Function.ready (jquery.js?ver=1.12.4-wp:2)
        at HTMLDocument.J (jquery.js?ver=1.12.4-wp:2)
    Theme Author satoristudio

    (@satoristudio)

    Both features work as intended on any of the browsers/machines where I’ve tried opening them, which hints that the issue most probably stems from caching – please purchase any plugin caches (if you’re using any third-party plugins like WP Super Cache etc), hard-refresh the browser and see if the issues persist. In case they do, please let me know, I’ll troubleshoot further. Thanks for your patience!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.