Passing a Task to Standard Pages
PermalinkFor example, with single pages, you can do /path/to/page/-/taskToRun and rather than running the view function in the controller, it runs the taskToRun function.
Even more I guess than specifically how to get the requested task (I think I've got that figured out), I'd like to know if it's even possible to pass a task to regular pages in 5.4. It seems like in pre-5.4, you can add /-/taskToRun to regular pages, and it just loads the pages like normal. However, with 5.4, I get the 404 page when trying to do that. I know the method for passing tasks has changed (no dash needed), but I of course still get a 404 when passing it without the dash (I assume cause it's looking for a page named /path/to/page/taskToRun).
Anyways...anyone have any thoughts on this?

So really, I guess the question is, is it even possible to add additional information in the URL in 5.4.
http://www.concrete5.org/documentation/developers/pages/mvc-approac...
Have you written the controller for the page type you are using? If not, that is likely why it is not working. There's nothing to handle the task.
basically to accomplish this you would need to check to see if you are in the dashboard section(the reason for this not being as wild as it once was) and then using page_type controllers and some switching based on the request task and request task parameters.
here's some code as to what i had working before it changed, one could probably get it going by overriding the controller finding that by searching the project for $do404 i think
<?php class BlogController extends Controller{ protected $type; protected $year; protected $month; protected $day; protected $blog_post_requested; protected $blog_requested; //maybe later protected $rtask; protected $metaSet; function on_start(){ $html = Loader::helper('html'); $this->addHeaderItem($html->javascript('tiny_mce/tiny_mce.js')); $req = Request::get(); $this->set('request',$req);
and do a echo $this->action('method_name');
or $this->url('pathTopage','method_name');
for the form action stuff.
the method name absolutely has to exist in the controller as defined via myTask in your example and accept your parameters via reflection.
:-/