Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Huy Tran 3 posts 23 karma points
    Apr 29, 2011 @ 07:04
    Huy Tran
    0

    Error parsing XSLT file: \xslt\umbBlogListPosts.xslt

    Dear all,

    After I successfully installed Business Template in Stater Kit, I met this problem when parsing Blog List macro.

    "Error parsing XSLT file: \xslt\umbBlogListPosts.xslt"
    In Content area, I got this:
    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.Data.SqlClient.SqlException: Invalid column name 'tagid'.
    Does anyone helps me solve this problem? Thank you so much.
  • Jan Skovgaard 11280 posts 23678 karma points MVP 11x admin c-trib
    Apr 29, 2011 @ 08:12
    Jan Skovgaard
    0

    Hi Huy

    Which version of Umbrac are you using?

    If it's 4.7 then you need to make a lot of alterations to the blog package in order to make it work. The mentioned column is missing in the database but I know that this is not the only error there is with the package - I think that there may be some work in progress to update it so that it works with 4.7.

    /Jan

  • Huy Tran 3 posts 23 karma points
    Apr 29, 2011 @ 08:32
    Huy Tran
    0

    Hi Jan,

    I'm using version 4.7. Can you show me more detail to help me solve this. Thank you.

  • Sharmin Jose 13 posts 33 karma points
    May 03, 2011 @ 22:41
    Sharmin Jose
    0

    Hi Jan/Huy,

    Do you have an update on this? I followed the steps which Connie said in http://our.umbraco.org/forum/getting-started/installing-umbraco/19120-upgrade-to-47-from-452 and deleted those assemblies from bin folder. But does not work.

    Could you share your steps followed or is this still an issue?

    ~Sharmin

     

  • Sharmin Jose 13 posts 33 karma points
    May 03, 2011 @ 22:52
    Sharmin Jose
    0

    I could solve it

    Steps:

    1. Take a backup and delete all the dlls in the bin directory.
    2. Copy the newest dlls from 4.7.
    3. Go to the content and try to view any aspx page.
    4. This would give you an error saying the dll could not be found
    5. Add those dlls only from the backup folder.

    ~Sharmin

Please Sign in or register to post replies

Write your reply to:

Draft