<?xml version="1.0"?>
<!--
Umbraco examine is an extensible indexer and search engine.
This configuration file can be extended to create your own index sets.
Index/Search providers can be defined in the UmbracoSettings.config
More information and documentation can be found on CodePlex: http://umbracoexamine.codeplex.com
-->
<ExamineLuceneIndexSets>
<!-- The internal index set used by Umbraco back-office - DO NOT REMOVE -->
<IndexSet SetName="InternalIndexSet" IndexPath="~/App_Data/TEMP/ExamineIndexes/Internal/">
<IndexAttributeFields>
<add Name="id" />
<add Name="nodeName" />
<add Name="updateDate" />
<add Name="writerName" />
<add Name="path" />
<add Name="nodeTypeAlias" />
<add Name="parentID" />
</IndexAttributeFields>
<IndexUserFields />
<IncludeNodeTypes/>
<ExcludeNodeTypes />
</IndexSet>
<!-- The internal index set used by Umbraco back-office for indexing members - DO NOT REMOVE -->
<IndexSet SetName="InternalMemberIndexSet" IndexPath="~/App_Data/TEMP/ExamineIndexes/InternalMember/">
<IndexAttributeFields>
<add Name="id" />
<add Name="nodeName"/>
<add Name="updateDate" />
<add Name="writerName" />
<add Name="loginName" />
<add Name="email" />
<add Name="nodeTypeAlias" />
</IndexAttributeFields>
<IndexUserFields/>
<IncludeNodeTypes/>
<ExcludeNodeTypes />
</IndexSet>
</ExamineLuceneIndexSets>
Hi guys, wondering if anyone else has seen this issue with umbraco 4.7 and uBlogsy 1.4. This is a production issue at this point and without the source I have very little recourse to correct or bypass this issue.
Ok, so here's the issue at the end of the day. I had removed some of the SEO fields that ship with uBlogsy because I needed to use my own custom fields for the templates that are in use for the site. So, on the 'uBlogsy - Base Page' docType I removed the following properties:
uBlogsySeoKeywords
uBlogsySeoDescription
This resulted in the YSOD errors on both the publish of the post as well as the publish event on the Comments folder that gets created when a new post is published. So, good to know for others I would imagine.
To fix the issue, I simply added the properties back to the base document type and simply placed them in the General Properties tab with a note that they are not in use.
Thanks Anthony for sending the source so I could debug.
Error publishing post
Hi, looks like there's an error in the event handler when publishing a post.
Anyway to get a patch for this? Cheers!
Thanks for the notification.
Did the nodes get inserted from RSS?
Is this publish crash from clicking the "save and publish" button on the content node? Or is it from right clicking the tree?
Hi Anthony, I had forgotten about this bug entirely and just double posted. Sorry about that.
So, this happens when I clikc the Save and Publish button.
Thanks,
Nik
Do you have any custom examine indexes?
Can you paste your examine config here.
No custom Examine indexes:
Thanks,
Nik
Hey Anthony, any chance you would mind sharing the source for 1.4? Would be cool to dig into this and see what may be happening.
Thanks,
Nik
Hi guys, wondering if anyone else has seen this issue with umbraco 4.7 and uBlogsy 1.4. This is a production issue at this point and without the source I have very little recourse to correct or bypass this issue.
Thanks for anyone who has any ideas!
Best,
Nik
Nik what is your email address?
1.4 is beta so there are of course bugs.
Totally understand bro, beta is inherently risky business :) You can get me at [email protected]
Thanks for your help!
Ok, so here's the issue at the end of the day. I had removed some of the SEO fields that ship with uBlogsy because I needed to use my own custom fields for the templates that are in use for the site. So, on the 'uBlogsy - Base Page' docType I removed the following properties:
This resulted in the YSOD errors on both the publish of the post as well as the publish event on the Comments folder that gets created when a new post is published. So, good to know for others I would imagine.
To fix the issue, I simply added the properties back to the base document type and simply placed them in the General Properties tab with a note that they are not in use.
Thanks Anthony for sending the source so I could debug.
Cheers,
Nik
Ah
Yes that will do it.
Lesson of the day... if you need remove or change things, do it incrementally and TEST TEST TEST :)
is working on a reply...