Potential bug with my site

[[chrisB]]

I have created a new admin group, as I want to eventually give the ability to some members but without full admin access.

However, the user group created doesn't show in my TinyPortal settings, in the block permissions, meaning they cannot see any at all. Here's the SMF groups and TinyPortal permissions, please note I scrolled slightly to fit them all in.



The issue seems to be only when the new group has "admin" rights.


So, I tried with a test site I have setup.

I created a usergroup, which was normal at first. Then I checked if it was added to TinyPortal, it was and then I made it have all admin powers. It remained, and I was able to toggle what blocks to show.



The result, blocks are able to be set to show.



I don't recall what version I first used, but it was 2.3.0 to which I upgraded to 3.0.1c.

What should I do to try to fix this issue? Any help to resolve this issue would be greatly appreciated.

I made reference once to 2.2.2, so I assume it might have been 2.2.1. I experienced some personal problems and lost motivation, but here I am again. I searched the issue, and checked to see if I had mentioned this before as it seemed familiar but that issue was different. I am quite highly medicated and I sometimes struggle to read things as I messes with my understanding (not all the time) but if I ask a question, it's not because I'm being lazy and not reading the docs. Information can be overwhelming at times, and I say this just for consideration. I'm not trying to be demanding or awkward. I really do appreciate TinyPortal and the work which goes into it.

[@rjen]

What would help is if you would clarify exactly what the new usergroup was.
You examples are pretty confusing!

In your first example I see two admin groups: Senior Admin (?) and Admin
Based on the question mark I deduce that the Senior admin is the original admin group (group ID 1), with full access to the forum (you apparently renamed it), the one that says Admin is not a full admin I assume you added that yourself?

Then the settings in the block are correct: Senior admin does not show (group ID 1): it is a full admin group and therefor cannot be selected in de block permissions. Admin does show and can be limited

In your second example you are using a group "Pirates" in addition to the "Administrator (?)" group (group ID 1)
also here you do not see the full admin group in the block permissions

Membergroup with ID: 1 is always assumed by SMF to be the admin group and excluded in permission settings: you can change the name of the group but not the ID.
Tinyportal follows this SMF functionality, therefor it works as designed and I see no issue...

[[chrisB]]

In both scenarios, the created group is 'admins'.

I created two new user groups with full admin rights. On my test site, these groups show up and can access everything, including TinyPortal blocks. But on my live site, one of the new groups isn't showing up in TinyPortal's block settings and can't see the blocks, even though they have full permissions.

I also changed the names of some groups:

The group "Admin" (which I created) appears in TinyPortal settings but can't view the blocks, even with permissions enabled.

The group "Senior Admin" (renamed to "test") doesn't show up in TinyPortal's block settings, but the users in it can see the blocks.

So, why does my test site work fine, but my live site doesn't show the group in the block's permissions?

The one that says Admin is not a full admin I assume you added that yourself?

Yes, I added the group.

It does, however, have full permissions based on what I can grant.

The issue is that the user group isn't showing in the TinyPortal block settings.

My original post explained that I created two new groups, which I gave full admin rights to. My live site doesn't show the user group. Yet on my test site, the new group did.

------

I have changed the user group "admin", which I created, to a different username. This group is displayed in the settings of the TinyPortal block. It cannot view the blocks, even with the toggle ticked for the group to be able to see them.

The user group "senior admin" is the original admin account. I have renamed it "test", and this does not show in TinyPortal's block permissions. However, the users in the group have permission to see the blocks.

-----

How is this possible? How come my test site is able to give rights to a user group and see the blocks, but my live site doesn't, and that group is not showing in the block's permissions?

------

[@rjen]

You are confusing me even more now: the screenshots you posted do not match the description you gave.

Can you pm me an admin account to your production forum so I can inspect the actual groups?

[[chrisB]]

In straightforward terms, one user group is missing from the permissions section of the TinyPortal block. Meaning they are unable to view any of the blocks.

The first set of images shows this.

As for the second set, it shows everything perfectly fine in my test area.

I'll PM you shortly, I do appreciate you for looking into this.

[@rjen]

I just checked your site and I STILL do not see the issue you described.

You have these membergroups:

You cannot view this attachment.

Test: this is membergroup 1: the standard SMF admin usergroep which you obviously renamed. This has always ALL admin priviliges and is therefor NOT available in the block settings: as admin it will see all blocks UNLESS you have changed this tinyportal setting: "Admin can see all blocks" This is not activated and as a result the users in user groep "Test" will NOT see any blocks

Global Moderator, Moderator, Pirates and Subsicriber : these are regular membergroups and therefor show up in the block settings.

Hence: it works exactly as I described: admin usergroep 1 does not show in the block settings, all others do.

The admin user group does not see any blocks due to the Tinyportal setting.
You cannot view this attachment.

[[chrisB]]

After a fresh install, my test site allows both the default admin group (ID 1) and a new admin group to access the same blocks, with each account only in its primary group. There are no issues with blocks not showing, and you don't have the "Admin can see all blocks" setting enabled.

However, my live site has a permission issue with one of the admin accounts, resulting in no blocks being shown. While I can achieve the same block access with two admin accounts on my test site, the live site can't do this. The workaround involves creating two admin groups (three admin groups in total), one of which is invisible, to achieve the desired functionality without seeing guest blocks.

This permission issue could affect others, and three admin accounts to achieve the same functions as two makes no sense.

--

I thought at first it was due to the group not showing; however, since admin (ID 1) doesn't show in the block permissions. It would seem that the group can't view the blocks at all without the setting you mentioned, whereas a new install doesn't. 🤷🏻�♂️

[@rjen]

What I see in your production site seems correct to me.

I cannot help you any further, I am sorry

[@rjen]

You keep stating things in a very 'broad' sense, not being specific what exact block you are missing, where and also not WHICH admin account is now giving you issues. Please be very specific: what exact account, what exact membergroup and what page are you 'missing blocks'... and describe it for the production site, because that is the only one I can access..

I just checked your site again and made the user you gave me "Senior admin" without any additional groups.
The setting 'Admin can see all blocks'is set, and the site looks as expected: I am seeing all the existing blocks in the forum and on the frontpage. The "senior admin" group is NOT in the settings for the block permissions for the reason I explained before...

Then I switched OFF the setting "Admin can see all blocks" and checked the forum again: now the blocks are not showing to me, which is correct, because of the setting. Blocks WILL show whenever I assign an additional membergroup to this user. This is also as expected.
Now I find that with this setting the frontpage remain completely empty: no blocks are showing: this is correct too even though it looks a bit funny...

Is this what you are referring to as the 'permissions issue'?
Please confirm or explain the issue better

You cannot view this attachment.

After this I have made the user part of "Admin" (so not the group ID 1) without additional groups and checked the site again: now the blocks are showing because they are assigned to the "admin" group in the block settings, and the "Admin can see all blocks" does NOT affect that. That's as expected too, since the setting only affects group ID 1...

[[chrisB]]

Thank you for your detailed explanation. I appreciate your patience.

To be specific:

Exact Membergroup: This account is part of the "Senior admin" membergroup. < Admin default SMF group ID 1

Page: The blocks are missing on the forum page and the front page of the production site.

I understand the functionality of the 'Admin can see all blocks' setting. When this setting is enabled, the admin can view all blocks without needing a separate group for the default admin ID. This does give the impression that the live set is working correctly. However, when this setting is disabled, the issue arises.

On my test site, I have 'Admin can see all blocks' disabled for both the default admin group ID 1 and the manually created admin group. Despite this, both groups can see the blocks. This gave the impression that there was something wrong with my live site, but based on your response, it seems you are correct.

Specifically, when the 'Admin can see all blocks' setting is turned off:

On the forum page: Blocks do not appear.

On the front page: The page is completely empty, with no blocks showing.

This discrepancy between the enabled and disabled states of the setting seems to be causing our misunderstanding. Your explanation confirms the behavior we are seeing, which aligns with my observations.

Is my understanding correct?

Thank you again for your help.