So you’re trying to use the default Fluid pagination widget via AJAX, correct?
I wonder how this could have worked with 2.2.3, because widgets must be configured to support AJAX and the pagination widget isn’t.
Could you please provide some more details on what you’re actually trying to achieve?
Also the log entry for that exception would be helpful (in Data/Logs/System_Development.log)
15-08-13 15:45:35 5858 WARNING Flow Router resolve(): Could not resolve a route for building an URI for the given route values.
event => 059ad6ad-6733-11e4-925d-005056010c5f
@action => show
@controller => event
@package => event.management
@subpackage =>
15-08-13 15:45:35 5858 CRITICAL Fluid Uncaught exception #1301610453: Could not resolve a route and its corresponding URI for the given parameters. This may be due to referring to a not existing package / controller / action while building a link or URI. Refer to log and check the backtrace for more details. - See also: 201508131545341eae33.txt
previousException => Uncaught exception #1301610453 in line 354 of /home/013-049/public_html/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/TYPO3_Flow_Mvc_Routing_UriBuilder.php: Could not resolve a route and its corresponding URI for the given parameters. This may be due to referring to a not existing package / controller / action while building a link or URI. Refer to log and check the backtrace for more details.
Sorry for the confusion. I meant the PHP code that implements the widget (the ViewHelper and Controller classes).
In the ViewHelper you need to set protected $ajaxWidget = TRUE; for example
If you use the f:widget.link ViewHelper with ajax="TRUE" Fluid won’t actually use the UriBuilder to create the URL, it will just create a string like “?__widgetId=xyz” or “?__widgetContext=xyz”. So the error above is probably triggered by retrieveData Template and, yes, probably by this VH that can’t be resolved:
Actually I do not configure Route for show event and also for other action. So what I need to now is configure route for event and set subpackage="{null}" ?
the subpackage argument defaults to NULL, so you can just omit it, but it should also work by setting it to an empty string as you did actually.
As to the Route: if the useParentRequest argument is set and the parent request is the main ActionRequest (which it would be by default), you do need a Route for it of course. Are you sure the exact same code worked with 2.2.3 ?
Maybe it’s easier to discuss this in the #flow-general package on slack
FYI a little update on this one: Our on-site task force (aka @aertmann) is currently in Cambodia looking at the issue up close. I think we found the change that broke this and will be able to fix it (btw: I misread the title and thought this was about a patch-level update only)
Confirmed it’s https://jira.neos.io/browse/FLOW-205 and the fix applies cleanly. Re-opened the issue so we can fix it for the next patch level release 2.3.7, but currently we have to wait for the Github move before we can do that.