Getting Silverstripe Pages published!? about silverstripe-restfulapi

[colymba]

True, I haven't used the CMS for a while. When developing an app this get's managed by Ember.

But I can see that DataObject with Versioned enabled could be an issue.

First thing that comes to mind would be to extend RESTfulAPI_DefaultQueryHandler and override handleQuery() with a few hooks. Maybe something like this:

public function handleQuery(SS_HTTPRequest $request)
{
    $result = parent::handleQuery($request);

    //Check if result....
    //If yes get the classname from the result (DataObject or DataList)
    //Check if the class has the extension Versioned enabled
    //if yes call doPublish() on each DataObject

    return $result;
}

The basic idea is here, and there should not be much more to change. You could also pass a query parameter with your request like ?versioned=publish or ?versioned=unpublish so you know if you need to publish or unpublish...

ps: just curious, have you been using Ember with SS too?

[DarioSoller]

thanks for your quick answer! I have tried couple of things, but couldn't solve the issue yet. I keep you updated... It just never sets the attributes wasPublished = 1 and PublisherID = 2 in the SiteTree_versions table of the SS database.

My goal is to make an ember client app for parts of the database of an already existing silverstripe CMS. Therefore I am currently working on a test SS project, to not mess up the whole thing. I liked the approach of both, ember and silverstripe, so I came up with the idea of trying to couple them somehow. Little research brought me to your git...

Anyway, cool project! So I will love to share my experiences along the way and keep you updated

[colymba]

I'll see what I can come up with about the Versioned object issue and let you know if I find a solution.

In the meanwhile, yes please do keep me posted how you get on with Ember and this API, eager to get feedback and use cases comments....

[richwestcoast]

Any progress with this? :)

[colymba]

Am not around much lately so it doesn't get much attention unfortunately... Happy for any one to pick this up :)

Like posted above, all this should need is extend the QueryHandler handleQuery to check if the requested class is Versioned and use a URL query parameter to toggle the publish/unpublish...

Although I don't think this would make it in the master but maybe in a recipe like note in the doc...

[DarioSoller]

Same with me, unfortunately haven't found the time to try it out yet!

[colymba]

Tracking those here #27