Sure I had to comment out the code I told you about last time, once I did that the currentroutedurl is what it should be from the PRC. In other words if my URL is this
127.0.0.1/space/andyscott/module/page/1
And I try to get the PRC and use the currentroutedurl in a module everything prior to the page is missing. What this means is that if I need that to rebuild the url at any stage then this information is missing for en example of what I am doing, it is not pretty and I think there is a better way but here it is.
<cfif (offset-15) gte 0>
<cfif listFind(prc.currentroutedurl, ‘Page’, ‘/’)>
<cfset routedUrl = listSetAt(prc.currentroutedurl, listLen(prc.currentroutedurl,’/’), rc.page-1, ‘/’ ) />
<cfset routedUrl = prc.currentroutedurl & ‘Page/’ & rc.page-1 />
Newer Entries
As you can see that if I was to use this outside of a module this would work a charm, inside a module it doesn’t work. But it does work if I comment the code that was first reported in the SES interceptor. The code that is comment out is
// Check if the match is a module Routing entry point or not?
if( len( foundRoute.moduleRouting ) ){
// Try to Populate the params from the module pattern if any
for(x=1; x lte arrayLen(foundRoute.patternParams); x=x+1){
params[foundRoute.patternParams[x]] = mid(requestString, match.pos[x+1], match.len[x+1]);
}
// Try to discover the route via the module routing calls
structAppend(params, findRoute(reReplaceNoCase(requestString,foundRoute.regexpattern,""),arguments.event,foundRoute.moduleRouting), true);
// Return if parameters found.
//if( NOT structIsEmpty(params) ){
// return params;
//}
Notice that if paramters is found is commented out, but I do know that this also causes other issues with value pairs as I reported earlier too.
Regards,
Andrew Scott
http://www.andyscott.id.au/