Bug #21912
closed
USER_INT Plugin not rendered when logged into BE as editor (non-admin)
Added by Jochen Rieger over 14 years ago.
Updated over 12 years ago.
Priority:
Won't have this time
Description
Tested with air_filemanager... If I'm logged into BE as admin or not logged in at all then the plugin renders its content correctly.
But if you log in as an editor (non-admin) the plugin won't be rendered (even main function won't be called at all!).
Using a debugger I narrowed this down to class.tslib_content.php function USER:
switch ($ext) {
case 'INT':
// ...
break;
default:
// ...
break;
}
Strangely it's working when not logged in - then it'll jump into the default case and the content is rendered. If logged in as editor in BE it'll jump into the 'INT' case and nothing will be rendered.
(issue imported from #M13152)
Can you please give a short note how one can reproduce this step by step? Thanks!
Hi Oliver,
I think we can close this one... there IS a strange behaviour though. But it might have to do with TemplaVoilia.
What I found out in this special case:
When logged in as an editor (not admin), then always the FIRST content element on the page won't be rendered.
Very strange... I'll observe this further and would file a new and detailed bug report if it turns out to be a bug.
But anyway it would be more concerning TV, I guess... so go ahead an close this one.
Thanks,
Jochen
Another hint:
The first element ist shown if the page will have no BE group set in "Access" module!!!
So ... must be something concerning be user rights. The cases:
1) logged in as BE User with Admin rights
> OK
2) not logged into BE at all
> OK
3) logged into BE as Editor (non-admin)
3.1) page has NO group set in "Access" module
> OK
3.2) page has set a BE group in "Access" moduole
> first content element on page is not rendered
Btw: The group that is set is also set in the be user record of the editor.
- Status changed from New to Closed
- Priority changed from Should have to Won't have this time
- Target version deleted (
0)
That happens when USER_INT config is not set correctly (and yes, it happens only for non-admin users in case of a wrong config due to the way how TS is rendered in the presence of the BE user). Too long to explain, so closing the issue because it is not a bug.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by