+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / receiving "Page not found" after configuring and adding the category widget with custom taxonomy to my page with a dynamic module

receiving "Page not found" after configuring and adding the category widget with custom taxonomy to my page with a dynamic module

3 posts, 0 answered
  1. Jody
    Jody avatar
    9 posts
    Registered:
    05 Dec 2012
    24 Dec 2012
    Link to this post
    I have a dynamic module called listings. I place this widget on a page called Listing. I have a custom Classification called "listingcategories" set up under classifications and within my dynamic module I have a field that is of type Classification named "listingcategories".  I added the Category Widget and configure it with the following: I set the baseURL to ~/listings (which is the Listings page), the DynamicContentType to Telerik.Sitefinity.DynamicTypes.Model.Listings.Listing, the FieldName to listingcategories, and the TaxonomyId to the id of the custom taxonomy.

    When I finish configuring the widget, I see the custom taxonomy displayed properly on my page based on the records of the dynamic content.

    When I mouseover the links in category widget, i see the url looks ok and shows the right item count for the custom classification: Below is an example the url:
    http://localhost/listings/-in-listingcategories/listingcategories/category1/sub1

    However, when I click any of the taxonomy urls, I get the Page Not Found error below. What am I possibly missing in my custom taxonomy or dynamic module?



    Server Error in '/' Application.
    Page not found
    Description: An unhandled exception occurred during
    the execution of the current web request. Please review the stack trace
    for more information about the error and where it originated in the
    code.
    Exception Details: System.Web.HttpException: Page not found
    Source Error:
    An unhandled exception was generated during the execution of the current
    web request. Information regarding the origin and location of the
    exception can be identified using the exception stack trace below.





  2. Bostjan
    Bostjan avatar
    10 posts
    Registered:
    18 Sep 2009
    14 Jan 2013
    Link to this post

    We noticed the same thing

    Any news on how to resolve this issue?

  3. Jen Peleva
    Jen Peleva avatar
    568 posts
    Registered:
    10 Nov 2016
    17 Jan 2013
    Link to this post
    Hi Bostjan,

    Did you try what my colleagug Nikolay offered as a workaround in his reply? 

    Regards,
    Jen Peleva
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
3 posts, 0 answered