Problem with setting a page to be unpublished by API

[titanium]

Dear ProcessWire fans,

I'm trying to set a page to be unpublished by API. Reason is: the page contains a field with a timestamp. As soon as the timestamp is reached, the page should become automatically unpublished.

As far as I know, the following simple code in the page's template should do:

if($timestamp <= time()) {
	wire('page')->addStatus(Page::statusUnpublished);
	wire('page')->save;
	throw new Wire404Exception();
}

The 404 is thrown, but the status doesn't get updated. If I edit the page in the admin afterwards, it is still published...

[adrian]

Make sure you have debug mode on so you can see any errors that are thrown. It might be as simple as needing this before the save line:

wire('page')->of(false);

http://wiki.processwire.com/index.php/Text_Formatters

http://cheatsheet.processwire.com/?filter=of(true

[titanium]

Thanks, Adrian. My test case is like this (I put it in a template):

var_dump(wire('page')->status);

wire('page')->addStatus(Page::statusUnpublished);
wire('page')->of(false);
wire('page')->save;
wire('page')->of(true);

var_dump(wire('page')->status);
exit;

When the page is called in the browser the output is:

int(1)

int(2049)

As far as I know, the page should have the status 2049 now, as int(2049) indicates. It should have been saved. But if I reload the page, I do get the same result! I expected int(2049), int(2049). What could be wrong with this?

[Wanze]

You must set the output formatting to false before changing the status.

Also you need to write save(), because it's a method and not a property:

wire('page')->of(false);
wire('page')->addStatus(Page::statusUnpublished);
wire('page')->save();
wire('page')->of(true);

[titanium]

D'oh! Embarrassing for me

[blackeye1987]

hi got a similar problem

i have a hook on aftersave which does in the end

if(!$page->is(Page::statusUnpublished)){
 $page->of(false);
 $page->status = Page::statusUnpublished;
 $page->save();
}

if i put out 

id: status(before change) status (after change)

i get this:

1310:int(0) int(2048) 

in basically an endless loop.

so it doesn't save the state, but why ?

[Soma]

Save hook save hook save hook ...

Add a flag to the page on first save and check for it to terminate.

[blackeye1987]

well this would be a workaround but it wouldn't help since the page doesn't get saved...
the status stays published.
so even if i exit the function on second call the page stays without beeing edited.



ahhhhh nevermind.. i found the error.. and it wasn't in the code

i set the template settings to do not allow to unpublish pages,
since i forgot what i was doing yesterday and testing today's frontent.. sooo.. jeah.. my bad.. nvm guys

[Soma]

You shouldn't exit (actually never) but use a flag

...
if($page->skip) return;
$page->skip = true;
$page->save();
...

[blackeye1987]

i didn't ment to use "<?php exit; ?>" to extit the function.

i already use return to get out it was depending on the published state of the page.

since i could not set it anymore it was called again.

it looks like this in my func

if(!$page->is(Page::statusUnpublished)){
 $page->of(false);
 $page->status = Page::statusUnpublished;
 $page->save();
}
return;

i just got into trouble because of the user ability to think straight

[Soma]

Ah ok.

On a sidenote: It's recommended better to use add and remove status not just status = status cause it's a bitmask and it can have more than one status.

$page->addStatus(Page::statusUnpublished);

https://processwire.com/talk/topic/1293-how-to-set-unpublished-for-a-page-in-the-api/?p=11538

[blackeye1987]

i know saw that, in diffrent posts.

but due to restrictions of users they are not able to set these.

the unpublished state is used to indicate that they dont need to fill the topic.

its complicated to explain.

but thanks for the reminder