Contents
How to invoke a controller action in craft?
To invoke a controller action, send a POST request to Craft, with an action param set to the desired action path, either in the request body or query string. Saves an entry. This can be used to save a new or existing entry, determined by the sourceId param.
How to create custom URL for craft controller?
Create your own endpoint for requests with a custom URL rule that resolves to your controller action. For example, in config/routes.php: By default, Craft makes an actions/ route available for appending any valid action path. This can be customized with the actionTrigger config setting.
Can a craft plugin continue after a controller call?
Craft has system Controller actions for core actions, but plugins may also have Controllers that define their own custom actions. The request doesn’t necessarily end after a controller call. The controller may allow it to keep going. Is it an element request?
What does the URL begin with in craft?
Action requests either have a URL that begins with actions/ (or whatever your actionTrigger config setting is set to), or an action parameter in the POST request or the query string. Craft routes action requests to a controller action that perform actions.
Where do the controllers live in craft CMS?
Controllers should live within a controllers/ folder within the plugin or modules’s base source folder, and be named in the format FooBarController.php (the Controller suffix is required). as a starting point. . (An active user session is required by default.)
When does a controller return a contentresult?
If a controller action returns a result that is not an action result – for example, a date or an integer – then the result is wrapped in a ContentResult automatically. For example, when the Index () action of the WorkController in Listing 5 is invoked, the date is returned as a ContentResult automatically.