Bug #3699: Misleading error message when calling inactive package - TYPO3.Flow - TYPO3 Forge

TYPO3 Flow Base Distribution TYPO3.Eel TYPO3.Flow TYPO3.Fluid TYPO3.Kickstart TYPO3.Welcome Packages Applications

Bug #3699

Misleading error message when calling inactive package

Added by Karsten Dambekalns about 6 years ago. Updated almost 5 years ago.

Status:

Resolved

Start date:

2009-06-18

Priority:

Should have

Due date:

Assigned To:

Karsten Dambekalns

% Done:

100%

Category:

MVC

Target version:

TYPO3 Flow Base Distribution - 1.0 alpha 3

PHP Version:

Complexity:

Has patch:

Affected Flow version:

Description

When trying to use an inactive package you currently get a "404 Not Found - No controller could be resolved which would match your request."

It would be awesome to get a hint at package activation, the message should inform about the package not being available/active. After all that's different from the package being available but the controller not.

FLOW3_misleading_error_message_when_calling_inactive_package_1.patch (34.7 kB) Bastian Waidelich, 2009-07-05 23:50

Associated revisions

Revision 33d98450
Added by Karsten Dambekalns about 6 years ago

[+BUGFIX] FLOW3 (MVC): When calling a controller on an inactive package the user no longer simply get's a 404 but a helpful hint. Fixes #3699.

History

#1 Updated by Bastian Waidelich about 6 years ago

Assigned To set to Bastian Waidelich

I'll upload a patch with a suggested solution tomorrow.

#2 Updated by Bastian Waidelich about 6 years ago

File FLOW3_misleading_error_message_when_calling_inactive_package_1.patch added
Status changed from New to Needs Feedback
Assigned To deleted (~~Bastian Waidelich~~)

Please have a look at the attached patch.
It brings some extensive changes to the way the controller is resolved and I'm not perfectly sure about the implementation.
But IMO the request was involved too much in package/controller determination anyways...
Maybe the request should have no dependency to the PackageManager at all!?