The call of TagManager not include the {$ROOT_URL}plugins/AdminTools/template/admin_style.css correctly. The webpages shows following:
The Problem is, the stylesheet of the admin_tools was not loaded. I can fix the problem as workaround, with a manual load in the admin/thmes/default/template/header.tpl file
(add the line
).
I have test with Firefox and Chrome.
I think on both pages there is a small irregularity which causes Smarty not to correctly load the AdminTols CCS. On the other pages it works.
The call of TagManager not include the {$ROOT_URL}plugins/AdminTools/template/admin_style.css correctly. The webpages shows following:

The Problem is, the stylesheet of the admin_tools was not loaded. I can fix the problem as workaround, with a manual load in the admin/thmes/default/template/header.tpl file
(add the line
<link rel="stylesheet" type="text/css" href="{$ROOT_URL}plugins/AdminTools/template/admin_style.css">
).
I have test with Firefox and Chrome.
I think on both pages there is a small irregularity which causes Smarty not to correctly load the AdminTols CCS. On the other pages it works.
<!-- github-sync-id:830902417 -->
@dawsk-2021 there is indeed something missing in your post ;)
(add the line
).
I have test with Firefox and Chrome.
@dawsk-2021 there is indeed something missing in your post ;)
> (add the line
> ).
>
> I have test with Firefox and Chrome.
<!-- github-comment-id:799388920 -->
I am aware that this is not a good solution since I am directly embedding a plugin at this point.
Please replace ** with < or >
Sorry my mistake, add the import of stylesheet of admin_style.css
`<meta charset="{$CONTENT_ENCODING}">
<title>{$GALLERY_TITLE} :: {$PAGE_TITLE}</title>
**link rel="shortcut icon" type="image/x-icon" href="{$ROOT_URL}{$themeconf.icon_dir}/favicon.ico"**
**link rel="stylesheet" type="text/css" href="{$ROOT_URL}admin/themes/default/fonts/open-sans/open-sans.css"**
**link rel="stylesheet" type="text/css" href="{$ROOT_URL}plugins/AdminTools/template/admin_style.css">**
{strip}
{combine_css path="admin/themes/default/fontello/css/fontello.css" order=-10}
{assign "theme_id" ""}`
I am aware that this is not a good solution since I am directly embedding a plugin at this point.
Please replace ** with < or >
<!-- github-comment-id:801333330 -->
AdminTools/template/admin_style.css is loaded, actually. That's not the real problem in my opinion. There is something, javascript related, that causes the issue.
`AdminTools/template/admin_style.css` is loaded, actually. That's not the real problem in my opinion. There is something, javascript related, that causes the issue.
<!-- github-comment-id:828331952 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The call of TagManager not include the {$ROOT_URL}plugins/AdminTools/template/admin_style.css correctly. The webpages shows following:
The Problem is, the stylesheet of the admin_tools was not loaded. I can fix the problem as workaround, with a manual load in the admin/thmes/default/template/header.tpl file
).(add the line
I have test with Firefox and Chrome.
I think on both pages there is a small irregularity which causes Smarty not to correctly load the AdminTols CCS. On the other pages it works.
You say "add the line", but I see nothing :-/
@dawsk-2021 there is indeed something missing in your post ;)
Sorry my mistake, add the import of stylesheet of admin_style.css
`
**link rel="shortcut icon" type="image/x-icon" href="{$ROOT_URL}{$themeconf.icon_dir}/favicon.ico"** **link rel="stylesheet" type="text/css" href="{$ROOT_URL}admin/themes/default/fonts/open-sans/open-sans.css"** **link rel="stylesheet" type="text/css" href="{$ROOT_URL}plugins/AdminTools/template/admin_style.css">**{strip}
{combine_css path="admin/themes/default/fontello/css/fontello.css" order=-10}
{assign "theme_id" ""}`
I am aware that this is not a good solution since I am directly embedding a plugin at this point.
Please replace ** with < or >
AdminTools/template/admin_style.cssis loaded, actually. That's not the real problem in my opinion. There is something, javascript related, that causes the issue.Actually, myself from the past already had found the problem... See #1080