[
https://issues.apache.org/jira/browse/OPENMEETINGS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jack updated OPENMEETINGS-672:
------------------------------
Description:
hello all
i dont think this is an important mistake,but i cant judge this is a bug of
openmeetings or i make something wrong configuration when a user in recordings
page ,he cant logout through click the logout link on the top,he can logout
only after change the page.
i have changed the users level,computer,the browser, but have no effect
this is not important,but my boss may take note of this ,i should solve the
problem
thanks for help
was:
hello all
i dont think this is an important mistake,but i cant judge this is a bug of
openmeetings or i make something wrong configuration when a user in recordings
page ,he cant logout through click the logout link on the top,he can logout
only after change the page.
this is not important,but my boss may take note of this ,i should solve the
problem
thanks for help
Summary: in recordings page ,people cant logout (was: in recordings
page cant logout)
> in recordings page ,people cant logout
> --------------------------------------
>
> Key: OPENMEETINGS-672
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-672
> Project: Openmeetings
> Issue Type: Bug
> Components: UI
> Environment: windows 7 64 bit , openmeetings 2.1 , intel i5 ,4G ram
> ,ie10 ,chrome
> Reporter: jack
> Assignee: SebastianWagner
> Priority: Trivial
> Labels: logout, recording
>
> hello all
> i dont think this is an important mistake,but i cant judge this is a bug of
> openmeetings or i make something wrong configuration when a user in
> recordings page ,he cant logout through click the logout link on the top,he
> can logout only after change the page.
> i have changed the users level,computer,the browser, but have no effect
> this is not important,but my boss may take note of this ,i should solve the
> problem
> thanks for help
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
