Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
A fix to prevent allowedActions() from failing with a warning when th…
…e main class doesn't have an allowed_actions array, but one or more of its extensions does. Background: I created a DataObjectDecorator for a form object that added an action. However, it refused to execute the action, giving an "action not allowed" error. Adding an allowed_actions array to the decorator was the only option, but caused RequestHandler::allowedActions() to fail with the following error: "Argument silverstripe#1 is not an array". This small patch eliminates the error. NOTES: - The reason why the new code is where it is, is so that the function still returns nothing (not even an empty array) if no actions are found - The master branch appears to also have the same defect, so it's worth checking that too, and fixing it if necessary
- Loading branch information