Hi Graham,

Try to add this code. Maybe you have to update document cache?

var userAdmin = new User(0);

Node.Publish(userAdmin);
library.UpdateDocumentCache(Node.Id);

Thanks

Thanks for the suggestion.

I have tried the code you suggest however I am still experiencing the same issue, does anyone have any idea what extra clicking Save and Publish does over publishing a node via the _contentService.Publish and _contentService.SaveAndPublishWithStatus methods?

Hi Graham,

This method is newest. _contentService.SaveAndPublishWithStatus

Saves and Publishes a single Umbraco.Core.Models.IContent object

This is obsolete: _contentService.SaveAndPublish

Thanks

Hi,

I have been using the SaveAndPublishWithStatus method (see initial problem higher up this thread), I only used the Publish method based on what another user posted. Either way I still experience the same problem as originally mentioned.

Thanks

Hi,

I have been using the SaveAndPublishWithStatus method (see initial problem higher up this thread), I only used the Publish method based on what another user posted. Either way I still experience the same problem as originally mentioned.

Thanks

I've just tested this using a Services.ContentService.Publish and I can see my new node in the var applications 

var applications = Umbraco.ContentAtXPath("//Homepage/Products");

Perhaps the problem is with your XPath (I confess I don't quite understand what your xpath is trying to achieve). Put a breakpoint on this line and drill into the non public members -> _content and can you see the node there? I've tried this with both Publish and SaveAndPublishWithStatus and it seems to be there...

Is it possibly whitespace / illegal chars in your xpath?  

Why use ContentAtXPath? Why not just use the standard API and see if that returns it? I've done this and it always seems to have worked:

Off top of my head it would be something like this to get every application:

var applications = Model.Content.AncestorOrSelf().Descendants("VacancyApplication").Where(n => n.GetPropertyAsValue<int>("candidate") == Members.GetCurrentMemberId();  

(I'm presuming MemberId is an int).

Hi,

The reason I am using ContentAtXpath is two-fold, first is that I am still learning the standard API so wasn' sure how to achieve the above and secondly I have applications that exist within the following type of structure:

A
   - A school 1
        - Live
              - Job
                   - Application 1
                   - Application 2
        - Pending
        - Closed
   - A school 2
B
   - B school
        - Live
        - Pending
        - Closed
   - A school 2

What my code needs to do is grab all of the applications no matter where they exist in the tree and that match the current logged in member id. As far as I can surmise and I have tried you code above, that code does not return all applications regardless of where they exist in the tree, whereas ContentAtXpath does. If you can help me try and work out how to do this without using the ContentAtXpath query that would be great.

Apologies the query you sent works if I remove the

.Where(n => n.GetPropertyAsValue<int>("candidate")==Members.GetCurrentMemberId();  

As you rightly mention, the candidate property type is not an int and is actually stored as a "nuPickers.LuceneDropDownPicker" pre-value. How would I change this to find the right value?

Okay, I have worked out the correct piece of code, see below:

var applications = Model.Content.AncestorOrSelf(1).Descendants("VacancyApplication").Where(x => Convert.ToInt32(x.GetPropertyValue<Picker>("candidate").PickedKeys.FirstOrDefault()) == Members.GetCurrentMemberId());

And I can confirm that this has now resolved the original issue of the node not appearing even though published when using the ContentAtXPath query.

Cool, glad you got it sorted! It's hard to write queries off the top of your head, but I'm glad I pointed you in the right direction. You can do most things via the API :)

is working on a reply...