SP Shows Latest Component reported as "deleted"

ENV: Windows 2003 R2. TS 7.3.2

Problem:

When using "get latest components" a number of components are showing the version as "deleted". This results in the component being removed if you continue with the update. If you remove the component and added the lastest version again to the page, the componet is fine (its clearly not deleted). Point to the same DCR used by the old component version and all is well. However, this is anonying, time consuming and a few of the components do not externalize content in a DCR - so, it you remove it from the page, recovering the content is awkward, at best.

Question:

Does anyone know what property/xml setting/database entry ? is convincing the SP the the latest version of the component has been "deleted" and what can be done to correct that state?

Background

I assume that the something in the .component definition is responsible, but the Base Component version number appears is 0 most of the time; the Version property of the .component file reflects the submission but does not always agree with the "version" number shown by the "get latest command" (using the manual method is show what the latest version is) for components that are "not" reported as deleted.

We have run the reset_xml on pages that are migrated to force them to pickup the latest component, but that is not helping with the 'deleted' state. We have looked in the .page file for any information that might confuse the get latest command but nothing we have tried has helped yet.

We develop components in DEV and then deploy them to TEST and then to PROD. I have not doubt that somewhere in the migration process we have introduced this condition. However, we have been doing this migation in the past and only recently has this problem been seen.

Any insights would be appreciated.

Paul Neiswander

Find more posts tagged with

Comments

Rick Poulin

The text of the <BaseComponent> element must match what's in your STAGING exactly, and is case sensitive.

So if your .page has a component that says

<BaseComponent Version="3"><![CDATA[Content/Plain Text.component]]></BaseComponent>

The component update process will look for

/iwadmin/main/livesite/component/STAGING/Content/Plain Text.component

If you have one space instead of two, or the capitalization is not the same, or the folder structure is not the same, then SitePub will not find this component in STAGING and will determine it to have been deleted. It could also very well be the case that your permissions on those folders are wrong, such that your regular users don't have read access into it, in which case the file would again not be found and be assumed deleted.

PNeiswander

Thanks Rick.

We will give this a shot. I was focused on .component and not .page.

Paul Neiswander

PNeiswander

Note on the solution:

In applying this solution the "Get Latest Components" action from the Site Publisher menu - when choosing the "Manual Compare" option, still showed that the latest version of some of the components in the page were deleted --- even after apply the correction that Rick provided.

However, when editing the Page and checking each of the components using the "Check for Updates" option from the component menu in Site Publisher, the "Deleted" problem was gone and the "latest" version of the component was correctly shown and matched the Version number of the latest component (based on Properties of the component).

After applying updating the components via the "Edit Page" action and saving the page, the Site Publisher -> Get Latest Components action indidcated all components were up to date. THe "deleted" state was no longer incorrectly being reported. Not sure what caused this apparent diffrerence between the two methods of check for latest components.