Bug #9985
Fatal error: Wrong parameters for Exception in Tx_Formhandler_Controller_Listing
| Status: | Closed | Start date: | 2010-09-30 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Reinhard Führicht | % Done: | 0% |
|
| Category: | Controller | |||
| Target version: | Stable v1.0 | |||
| Votes: | 0 |
Description
Tx_Formhandler_Controller_Listing.php contains the following code:
if(!$table || !$this->mapping) {
throw new Exception('insufficient_config', 'Tx_Formhandler_Controller_Listing');
}
The second parameter needs to be an integer.
Associated revisions
Fixed bug #9985: Simplify template object selection for pages and FCE
History
Updated by Christian Weiske over 2 years ago
The error message should also tell us what is missing - mapping and table name.
Updated by Reinhard Führicht over 2 years ago
- Category set to Controller
- Assignee set to Reinhard Führicht
- Target version set to Stable v1.0
Changing it to
Tx_Formhandler_StaticFuncs::throwException('insufficient_config', 'Tx_Formhandler_Controller_Listing');
fixes the problem, right?
Updated by Christian Weiske over 2 years ago
Tx_Formhandler_StaticFuncs::throwException() only accepts one parameter.
Updated by Reinhard Führicht over 2 years ago
No, it accepts more than one parameter.
if(func_num_args() > 1) {
$args = func_get_args();
array_shift($args);
$message = vsprintf($message, $args);
}
This way you can add any count of parameters to the method call. The first parameter is the key in the translation file, all other parameters are used for printf.
Updated by Christian Weiske over 2 years ago
ok, I only looked at the method signature. So yep, your suggestion would fix the bug.
Updated by Reinhard Führicht over 2 years ago
- Status changed from New to Closed
Listing got removed completely, so this issue is obsolete.