Thread: Paging Question

Hello, when I click on a page number it encodes the url as http://www.nokomisnutrition.com/c-34...0%20?pagenum=4

this url of course does not work, but if I manually remove all the %20's and leave it at http://www.nokomisnutrition.com/c-34...aspx?pagenum=4 this does work.

Any ideas will be greatly appreciated.
Jose Rojas
http://www.nokomisnutrition.com/

Could you tell us what version are you using?

I came across the same exact issue today. Does any one have input on why the %20 are being added?

Version ML 8.0.1.1

Thanks,
Drew

I had the same issue (I have a post here somewhere about it), I had to modify the code to strip out the whitespace

XSLTExtensionBase.cs ... inside the PagingControl method

Code:

            BaseURL = BaseURL.Replace(" ", "");// hack to remove whitespace
            StringBuilder tmpS = new StringBuilder(4096);

Yes, that's the fix; however, using Regex would be the best solution and you could do apply this fix if you have the source code. If you don't have, please submit a support ticket. One of our technical support engineers should be able to provide you with the appropriate update. Please don't forget to affix your order number for verification purpose on your postage...

Thanks guys, unfortunately i do not have the source code or any incidents. I would think that aspdotnetstorefront would provide fix for a significant but in the code without needed to place an incident.

Is this a problem with all installations or only some? OR what is the root cause of this?

Thanks,

Drew

Just contact support, im sure there will be no charge to fix this for you. They are quite reasonable

I tried, but they told me i would need to purchase an email incident since it is not a known issue and most likely has something to do with the custom code. I just can't see that anything i did would effect any of these variables. I could understand if i had the source code and had access to them but then if i did i could just fix the error!

For now i am not displaying the paging option but if anyone has any information regarding the cause of this I would really appreciate it. We are a brand new company and can't afford any more out of pocket costs.

Thanks,
Drew

"not a known issue" ... did you point them to this thread?

This apparently occurs when you apply source-code formatting. The specific problem places are the BaseURL and the CurrentPage sections, although it might be worthwhile to remove extra white space from any param and variable lines.

Support was unhelpful regarding this, which doesn't make sense, since the point of the XML packages is to allow for customization without touching the codebase, and reformatting code while making said customizations would be a common task. You would think they could at least post a warning/note...

If you do not have the source code you can easily trim the $BaseURL in the xmlpackage.

Use the following code:

Code:

<xsl:param name="_baseUrl">
        <xsl:value-of select="substring($BaseURL,
                  string-length(substring-before($BaseURL, 
                                substring(normalize-space($BaseURL), 1, 1)
                                                 )
                                ) + 1,
                  string-length($BaseURL)
                -
                  string-length(
                        substring-before($BaseURL, 
                                         substring(normalize-space($BaseURL),
                                                   1, 
                                                   1)
                                         )
                                )
                - 
                  string-length(
                        substring-after
                                   ($BaseURL, 
                                    substring(normalize-space($BaseURL),
                                              string-length(
                                                  normalize-space($BaseURL)
                                                            ), 
                                              1)
                                    )
                               )
                 )"/>
      </xsl:param>

and then I use the $_baseUrl parameter with the PagingControl() function as follow:

Code:

<xsl:value-of select="aspdnsf:PagingControl($_baseUrl, $CurrentPage, /root/Products2/Product/pages)" disable-output-escaping="yes" />

This works for me!