Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on startup when called for the second time #10

Open
kludikovsky opened this issue Jan 22, 2016 · 4 comments
Open

Error on startup when called for the second time #10

kludikovsky opened this issue Jan 22, 2016 · 4 comments
Assignees
Labels

Comments

@kludikovsky
Copy link

Whenever I call phpMyAdmin from within T3 the second time I get the error:

Error
Unable to determine TYPO3_MODE.

This is regardless if I do a logout before or not (which in most cases I do following a timed out session)
When I manually delete the phpMyAdmin cookies the system can be called without any issue.

T3: 7.6.2
pMA: 5.1.4

@abeutel abeutel added the bug label Jan 28, 2016
@abeutel abeutel added this to the phpMyAdmin 5.1.6 milestone Jan 28, 2016
@abeutel abeutel self-assigned this Jan 28, 2016
@kludikovsky
Copy link
Author

kludikovsky commented Dec 29, 2016

Just for feeedback as i assume it has not yet been closed.

I still experience this still with
T3: 7.6.12
pMA: 5.1.8

But the workaround did not work now.

@kludikovsky
Copy link
Author

I still experience this with
T3: 7.6.15
pMA: 5.1.8

@kludikovsky
Copy link
Author

Is there any update on this?
It is now happening on all browsers I use (Op, FF, Vivaldi, Chr)
Just remoding the cookies does not help anymore.
And deleting all local data is not an option.

BY THE WAY:
The statements to check the BE_Mode:

if ( !defined('TYPO3_MODE') ) {
	die ('<h1>Error</h1><p>Unable to determine TYPO3_MODE.</p>');
} else {

are in all modules I visited at the very beginning (line 2) of the script. Not so with the PMA-Module, where they are at the end, following the class defintion and some statements. I am not deep enough in to judge this, but might this be a reason?

@abeutel
Copy link
Member

abeutel commented Apr 7, 2017

We will check and try to reproduce this issue since we were unable to reproduce it until now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants