Page Staging

[Knubbi]

We use the amazingly awesome Processwire as a website CMS. Again, thanks to Ryan and the Community to make it happen!

What we miss is a a staging mechanism:

The "production version" of a page is visible for the public.

A different "work in progress" version of the same page is only visible for specific users (or user groups).

Specific users can turn "work in progress" pages into "production version".

Does this exist already? Is there a workaround to achieve it or would this be something 4.0?

[MoritzLost]

This is the exact purpose of the ProDrafts module!

[psy]

You could use site/config .php settings, eg:

<?php

if ($user->hasRole('dev') { // or whatever role you assign 
// development templates directory
$config->urls->templates = $config->urls->site . 'templates-dev/';
$config->paths->templates = $config->paths->site . 'templates-dev/';

$config->urls->fieldTemplates = $config->urls->templates . 'fields/';
$config->paths->fieldTemplates = $config->paths->templates . 'fields/';

} 

// other users, including the public, will see the default $config->templates & $config->paths (same for fields) 

 

[psy]

@MoritzLost True, however (unless I missed something), ProDrafts doesn't work for Repeater Matrix whereas my suggestion will work for template development.

As I understand it, ProDrafts is more for checking/comparing content before committing changes. 

I guess it's what @Knubbi is trying to do

[MoritzLost]

@psy No idea, I haven't used ProDrafts yet. Though unless I have misunderstood the question, this question is about having public and draft versions of a page's content, not different versions of it's PHP template. So I don't think your suggestion applies to this use-case?

[Knubbi]

Indeed, it is about the content.

As we make extensive use of RepeaterMatrix, ProDraft may not be a fit. Too bad.

[psy]

If it's only content, there's also https://modules.processwire.com/modules/version-control/

 

[Knubbi]

We do have "version control" but it doesn't hide the latest (work in progress) version. It's kind the other way round.

P.S.: Just found, that we do have a ProDrafts license. Any insight, when this might be included in ProDrafts (Quote of description "In addition, fields using a type of Repeater or PageTable are not currently supported for drafts (though support is planned).")?

 

 

[psy]

@Knubbi that's a question for Ryan in the ProDrafts forum ? 

[dragan]

This may seem like a hackish workflow proposal, but you could just as well clone the production page, unpublish that copy, and work on that. If the clone is ready to be published, publish that one and hide / unpublish the other. Just bear in mind to adjust the page names and -names to avoid ugly looking URLs like /section/my-page-name-copy and 404s.

[szabesz]

5 hours ago, dragan said:

but you could just as well clone the production page, unpublish that copy, and work on that.

That reminds me of this one: https://github.com/robphilp/ProcessPageDraft (https://modules.processwire.com/modules/process-page-draft/)

Never tried it though...

[Mikie]

As far as I remember ProDrafts got an update at some point to work with RepeaterMatrix. Could be wrong but I feel it was in a blog post.

Edit: here's the post, with caveats about auto-save https://processwire.com/blog/posts/processwire-3.0.75-and-a-new-version-of-prodrafts/

[AndZyk]

ProDrafts is working good with repeaters. In rare occasions there are some quirks, but you could customize your ProDrafts settings in that case.

Another solution would be to have a staging website and a production website, which I would recommend in any case. The client could prepare new pages on the staging website and you could export and import them to the production website with the import/export feature. For small changes that would be overkill, but for large changes to the website this is also a good way.

Regards, Andreas

[louisstephens]

I actually was working on something similar to import/exporting using the Rest API module here at work. I have a cron job set up targeting a specific page (on the live site) with some jquery checking the api endpoint (local dev server with an external locked ip). I then post that to the targeted page and run some php to update fields on the live site with the content.. It's overkill, but I like it as it allows new content/changes to be uploaded if in case I wasnt able to get to it.

[Knubbi]

*bump*

A web site staging system is still sorely missed. All suggested solutions are no work around.

ProDraft applies to individual pages. There is no central button "RollOut" to make the new version of multiple pages go live in one go.

Besides ProDraft is sometimes quirky with repeaters.

Is there really not even a thought of implementing a staging mechanism?

 

P.S.: Just noticed that the top title is not ideal. It should be "website staging" instead of just "page staging". Sorry for that.

[bernhard]

This is something that I'd also wish to have. But it's not easy to do properly.

10 minutes ago, Knubbi said:

ProDraft applies to individual pages. There is no central button "RollOut" to make the new version of multiple pages go live in one go.

If that's the only thing missing have you thought of asking Ryan for adding that feature to ProDrafts?

[dragan]

I have never used ProDrafts, but the docs mention a drafts manager:

https://processwire.com/store/pro-drafts/#drafts-manager

Quote

From here you can review pending drafts, compare and view them, publish or abandon them, individually or in groups.

Quote

From there you can perform batch publish/abandon operations

Sounds like it's exactly what you're asking for.

And even if that feature wouldn't exist: It would be quite easy to use ListerPro and write a custom Batch Action I guess...

Edited July 3, 2023 by dragan
added image

[bernhard]

1 minute ago, dragan said:

And even if that feature wouldn't exist: It would be quite easy to use ListerPro and write a custom Batch Action I guess...

I don't think so. At least not with the kind of site that I build. As soon as you have some references in your pages or media like images etc. it gets tricky I guess... But maybe it's easier than I think. I'd be happy if that's the case ? 

[dragan]

2 minutes ago, bernhard said:

I don't think so. At least not with the kind of site that I build. As soon as you have some references in your pages or media like images etc. it gets tricky I guess... But maybe it's easier than I think. I'd be happy if that's the case ? 

Well, I meant if you have ProDrafts installed, but it would be missing the batch publishing feature. I know that building a staging workflow from scratch is far from easy - otherwise we'd have a dozen modules out there already and this forum thread wouldn't even exist ?

[bartelsmedia]

On 7/3/2023 at 2:49 PM, dragan said:

I have never used ProDrafts, but the docs mention a drafts manager:

Wow, wasn't aware of this. Sorry for this.

But bernards comment is also valid.

[Boost]

Fortunately, @ryan isn't in sales? Despite three years passing, this thread remains silent, with no input from him regarding the suitability of ProDrafts for page staging ?