Nathan Explosion

For the app icon? Pretty sure that's a nope and not supported on iOS and Android. Use a PNG.

Correct link - do not upload those dev tools

Install beta 1 (excluded from video, because it's boring and I'm not showing you my license key) Create a template hook in your theme on front/system/globalTemplate Go to site, view page source prior to </head> Upgrade to beta 2 Go to site, view page source prior to </head> After step 3 After step 4: Video: Dashboard — Mozilla Firefox 2024-10-24 23-18-14.zip

If you need specific reproduction steps then I can do them tomorrow.

Which works as expected in Beta 1: And ceases to work in Beta 2: A behaviour that leads to:

I know. I am just providing more flesh on the paltry bones of the original report of the issue for v4 so it can be fixed there.

v4.7.18 via Chrome, current release, windows Members - Google Chrome 2024-10-19 19-27-39.mp4

So, I approach issues differently to Randy. Instead of 'jumping to cause', I try to understand what you actually did instead of making assumptions on what you did: When you say you've enabled it, did you do the following: Enable it? Then create an API key as directed? Was it approved by GIPHY? Did you then enter it in the ACP, and save it? Because only then would you get the icon in the editor that provides the integration (which, by the way, is theme independent as it is a CKEditor plugin): Did you then use that button to search for your chosen GIF? Or did you manually paste in the URL for the GIF?

Join the club...

You should always test on current release and remove any customisations you have made...ahem.

I haven't...it's your own menu manager as-is I give up.

@Marc - just spotting you specifically mentioning 'Store' there, and it appears you have been led easily by my indicator arrow. I'm not only referring to the 'Store' here. Look at the icon to the left of each of the top-level menu items. Without any added icons (just the defaults) the 'default' for them all is file-image With me adding icons: For reference only, if I do this IN_DEV then the store icon appears fine. Adding a var_dump on navBarItems, the $roots for those 3 menu items are: C:\wamp64\www\dev\ips_50_dev_a\system\Theme\Theme.php(3678) : eval()'d code:15: array (size=3) 1 => object(IPS\core\extensions\core\FrontNavigation\CustomItem)[215] public string 'defaultIcon' => *uninitialized* protected ?array 'subItems' => null protected array 'configuration' => array (size=2) 'menu_custom_item_url' => string 'https://localhost/dev/ips_50_dev_a/' (length=35) 'menu_custom_item_target_blank' => boolean false public ?int 'id' => int 1 public array|string|null 'permissions' => string '*' (length=1) public string 'menuTypes' => string '*' (length=1) public ?array 'icon' => null public int 'parent' => int 0 2 => object(IPS\core\extensions\core\FrontNavigation\CustomItem)[251] public string 'defaultIcon' => *uninitialized* protected ?array 'subItems' => null protected array 'configuration' => array (size=4) 'menu_custom_item_url' => string 'app=core&module=discover&controller=streams' (length=43) 'menu_custom_item_target_blank' => boolean false 'internal' => string 'discover_all' (length=12) 'seoTitles' => array (size=0) public ?int 'id' => int 2 public array|string|null 'permissions' => string '*' (length=1) public string 'menuTypes' => string '*' (length=1) public ?array 'icon' => null public int 'parent' => int 0 16 => object(IPS\nexus\extensions\core\FrontNavigation\Store)[248] public string 'defaultIcon' => string '\f07a' (length=5) protected ?array 'subItems' => null protected array 'configuration' => array (size=0) empty public ?int 'id' => int 16 public array|string|null 'permissions' => null public string 'menuTypes' => string '*' (length=1) public ?array 'icon' => null public int 'parent' => int 0 That last one is Store - and looking at that IPS\nexus\extensions\core\FrontNavigation\StoreFrontNavigation extension, there is a defaultIcon value that is cart-shopping /** * @var string Default icon */ public string $defaultIcon = '\f07a'; But the 'Browse' and 'Activity' roots are generated from IPS\core\extensions\core\FrontNavigation\CustomItem, and there is no defaultIcon value in them so the file-image icon will be used for them.

It's your menu manager, as-is. If you're not seeing the issue, fine - I've reported it, I am happy.

Something like this would be more logical than the existing image: eye list-ul (which is the one used for some of the 'Activity' sub-menu items) cart-shopping (which is the one used for the 'Store' sub-menu item)

Aware of that, yes but I'm reporting a bug with the front-end functionality - if the above is a requirement for it to display an icon correctly then the front-end should alert to that being a requirement. Additionally, the ACP icon advice is: "You may pick a custom icon for this menu item. If none is selected, a context relevant default icon may be used" "May" implies a choice "Must" would imply a requirement. And as none is selected (because it isn't a requirement) then the 'context relevant default icon' should be a 'context relevant' icon, not what appears (to a layman) to be a broken FA icon (it's actually just the one indicated) considering that the sub-menu items all have a 'context relevant' icon.

I always clear cache before submitting, so already done.

OK - your actual issue has now been fleshed out to be clearer. Good luck - sounds to me like you may have an issue with static\templates\core_front_global.php not containing the correct template information for beta 1. If I was you, I'd ensure that all of your files are replaced with the ones in the current beta 1 download package.

And you're on beta 1, yes? Are you using IN_DEV? Yes or no.

So maybe you could actually provide a screenshot of what you DO see, so people don't have to guess what you are seeing? Anyway...here it is, in all it's glory, in the listing of available hooks for System on a test installation of Beta 1

I'll add in the 2 steps, if you wish to use a custom template. But you really only need to do one, which is adding your code in as a HOOK directly in the place you want it. Anyway... Step 1: custom template Step 2: adding it in before the </head>