Project

General

Profile

Actions

Bug #57424

closed

/typo3/null was not found on the server

Added by Anonymous over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2014-03-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

After update from 6.1.6 to 6.2.0 some Modul links in Backend brings "The requested URL /typo3/null was not found on the server"


Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Bug #57678: After update 6.1.7 -> 6.2 BE 404 errors; Extension vidiClosed2014-04-05

Actions
Actions #1

Updated by Markus Klein over 10 years ago

That is really strange. Which modules are affected?

Actions #2

Updated by Anonymous over 10 years ago

SEO from tq_seo
News from news
Workspace
View
Media from media
FE User (don't know the extension)
FE Group (don't know the extension)
Extensionmanager
Language
Extension Builder
Backend User
Install
Log
Reports

Actions #3

Updated by Markus Klein over 10 years ago

  • Status changed from New to Needs Feedback

I suspect that one of your extensions is causing this.
Can you please try to remove all 3rd party extensions one by one to see it gets working at some point?

Actions #4

Updated by Anonymous over 10 years ago

Deactivated all extension in LocalConfiguration.php but no change.

Actions #5

Updated by my darkness over 10 years ago

I've done an update from 6.1.7 to 6.2.0 and have the same issue with PHP 5.4.4

Actions #6

Updated by Markus Klein over 10 years ago

Does that also happen on the same server, if you install a blank new installation of 6.2?
We need to find out whether this is a configuration problem of the webserver/PHP (which has to be documented) or if we really have a well hidden bug in the TYPO3 Core.

Additionally, you should consider using the Dev-Preset in the Install Tool for that updated instance and look out for errors issued somewhere.

Actions #7

Updated by Anonymous over 10 years ago

Today I tried the upgrade wizzard in the install tool several times again and now all modules works for me.
Maybe the em extension from an earlier version caused the problem or the cache delete option in the install tool is much more powerfull than in backend.

Actions #8

Updated by Markus Klein over 10 years ago

  • Status changed from Needs Feedback to Closed

Great. Yes the "clear all cache" in the install tool is the most rigorous tool. It goes even beyond the "clear system cache" command of the backend.

Closing this ticket.

Actions #9

Updated by Asger no-lastname-given over 10 years ago

Hello,

I have the same problem, but I found the reason: it is the extension VIDI and the Media-extension is dependent of VIDI.... - I found the relation, because menu-items rendered after the "FE User" and "FE Group"-items has the typo3/null-links and the wierd links be normal again when removing VIDI...

Regards
Asger Frisgård

Actions

Also available in: Atom PDF