More in this section
Forums / Developing with Sitefinity / what might be going on here?

what might be going on here?

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. steve portock
    steve portock avatar
    8 posts
    Registered:
    23 Apr 2010
    22 May 2010
    Link to this post
    I am customizing the contentviewsingleitem.ascx for a customized blog post view. I did use the meta master as i had some multiple controls using the same id issue that that solves. I downloaded the code for that and had to rebuild it with newer modules, 3.2 vs 3.7 that i am using. Vs2010 did not like the mapping settings at all, but compiled and ran and it appears to work correctly. In doing this, I went back into the blog item editors controls, postnew.ascx and postedit.ascx and took out some meta fields that i had added earlier since with the meta master, i did not need them anymore, and these were extra fields, nothing that was there originally. I also fixed the resx files to and took out the resources items that matched my meta fields. Now i can't delete any blog posts, (sort of)add any, or (soft of)edit any. On any edits or adds, it throws a no segments* file found: files: error in both cases. However the blog post is there after you navigate back to the blog post list. On trying to delete a blog post, I get a similar error, a system.io.filenotfoundexception on the no segments thing, except this one is in a popup window vs the others, in just a server error page condition. So what might be going on here? No code was involved, just removing meta fields and taking out the controls that fed them. Anything I should be looking for?
  2. steve portock
    steve portock avatar
    8 posts
    Registered:
    23 Apr 2010
    22 May 2010
    Link to this post
    This ended up fixing this. Cleaned out the following tables.

    DELETE FROM [PPGSDOTCOM].[dbo].[sf_Search_ClientSettings]
    GO
    DELETE FROM [PPGSDOTCOM].[dbo].[sf_Search_IndexignClient]
    GO
    DELETE FROM [PPGSDOTCOM].[dbo].[sf_Search_IndexignService]
    GO
    DELETE FROM [PPGSDOTCOM].[dbo].[sf_Search_Variables]
    GO

2 posts, 0 answered