Project

General

Profile

Actions

Bug #25075

closed

Module loader. No module found. If this is a temporary error, please reload the Backend! - SEO Doctor

Added by Henrik Ziegenhain about 13 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2011-02-18
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

It`s not possible to log in to Backend if the following conditions match:

- using Firefox
- having FF-Extension "SEO Doctor" installed
- have not created a robots.txt

I don`t know if, and how, this is related to TYPO3.
We found this because of a error report - the protocol is a very useful module :)

While logging in some of the following entries are made in the logs:
"Core: Exception handler (WEB): Uncaught TYPO3 Exception: Reason: File "robots.txt" was not found (1)! | RuntimeException thrown in file /kunden/server/webseiten/typo3_src-4.5.0/typo3/sysext/cms/tslib/class.tslib_fe.php in line 1572"

Creating a robots.txt OR deactivating the SEO Doctor solves the problem, the backend comes as expected.

This is in some way related to 0017512
(issue imported from #M17639)

Actions #1

Updated by Daniel Lienert about 13 years ago

I have the same problem and it occurs under TYPO3 4.5.2 and Firefox 3.6.13 / Chrome 9.0. No SEO tools are installed, creating a robots.txt file does not solve the problem.

I solved the problem, it was a mysql error concerning the cache tables. So i t seems the message only indicates that something went wrong ...

Actions #2

Updated by Rafal Brzeski about 13 years ago

after deactivating SEO doctor the problem is gone,
thanks Henrik

Actions #3

Updated by Philipp Metzler over 12 years ago

Same problem here - no SEO doctor installed. Doesn't occur all the time in Firefox 5.0.1 but sometimes.

Actions #4

Updated by Steffen Gebert over 12 years ago

  • Target version deleted (0)

Philipp, please open a new bug report.

The OP mixed several things up. Having no robots.txt results in the Log entries. But it can't be the cause for the module loader problem. But extensions could cause such trouble.

Actions

Also available in: Atom PDF