stenberg / content-staging Goto Github PK

Would prevent title from getting lost if searching, toggling between pages etc.

In the Edit Batch view you cannot select a range of posts when selecting a post on the top then selecting a post further down pressing the SHIFT key.

This is because selection is connected to a click event for a checkbox. Make event listen to changes to checked/unchecked instead (with the added benefit of not having a special method for the select all checkbox).

During pre-flight checks should be performed to ensure that the images the user wants to sync from stage to production actually exists in stage.

For performance reasons the batch importer is running as a background process on the production environment. This currently only works on unix.

We need to determine what operating system the application is running on (php_uname) and take appropriate action (e.g. popen on Windows). Need to know PHP executable, possibly PHP_BINDIR can be of help. If not, user could be given the possibility to configure the path.

Fallback solution is to use AJAX requests.

Only getting the first message (Import of batch has been started) when deploying a batch.

Instead of deleting and inserting post meta we should update.

I have attached a screen shot of my preflight check - I have followed the instructions, added the configs to both environments, but it does not seem to be working. Any ideas what could be the issue?

Better naming of hooks to make it easier for third-party developers.

A message Content batch has been updated! is being displayed after you save a batch you've been working on. This message stays when you navigate between lists of pages using the pagination.

This is because the query param &updated is appended to the pagination links.

Would be nice to get rid of the message once user starts to navigate between pages after an update.

See https://wordpress.org/plugins/about/readme.txt

When selecting posts to include in batch it would be great if pagination was supported. At the moment you can really just see the last 50 posts that was updated.

To make it easy for third-party developers to pass messages from production to content stage a message system will be needed.

When pre-flighting a post that has a parent post that is not on production and not in the batch you want to return a message from production with links to the missing parent. This is not possible because we don't know the content staging domain when on production.

One option is to include the domain with the batch and have a method for getting a URL using the staging domain.

In wp_postmeta there is a meta_key _edit_last that refers to the last user who was making changes to the post. The ID of that user must be re-mapped to match the production user ID.

If a post that is being synced has a parent post, then that parent post should be included in the batch as well. We can then compare if the parent post has been modified since last time it was synced. If that is the case a notice should be given to the user informing that the parent post will be synced as well.

Should always include the parent page in batch. Instead of having a post model where parent post is an ID, the actual post should be included.

If not we will just keep adding things to the post object anyway (like GUID, modification date, etc.).

Only issue access tokens valid for ~1 min.

Support for importing comments and comment meta on production.

As a third-party developer
I need to be able to filter the endpoint
So that I can dynamically change it in a multi-site setup depending on the site I'm currently on.

Currently taxonomies and terms are properties of a batch, they should belong to a post.

Assign a default batch title to batches that has not been given any title.

I want a 'created by' column in the list batches view.

The list of posts you can include in your batch is sorted in a funny way. Does not look right.

https://github.com/travis-ci/travis-ci-php-example

Currently there is a requirement for the developer to add a few settings to their configuration file (wp-config.php).

If these constants are not set, the developer will not be notified other then if display errors is turned on or if developer looks in the log.

To simplify for developers a warning message should be displayed if settings have not been added to the configuration file.

https://wordpress.org/support/topic/undefined-constant-1

Currently only featured images are supported.

Currently all posts of any post type (except for content staging specific post types) is listed in the list posts view when user is creating a batch.

Would be good if you could select post types that should not be included in he post list.

During deploy a loader should be displayed to indicate to the user that progress is being made. Also return more import messages back to user.

Not possible to login in to backend after syncing a batch.

I want a link to the published post so I can check that it looks right after deploy.

When you save a batch (on the Edit Batch page) you are moved to the first page in the pagination. It would probably make more sense to stay on the page you are currently on.

Instead of deleting and inserting user meta we should update.

It does not work to send a post directly to production after it has been created/updated, getting:

PHP Fatal error:  Call to a member function get_id() on a non-object in /wordpress/wp-content/plugins/content-staging/classes/managers/class-batch-mgr.php on line 74

This only happens for slave sites in multi-site setup.

In 'add new' page, I want it to be clear what to do.
More textual descriptions required: ie. "Add Batch title"
"Select Pages to add to Batch"

When creating editing a batch, it would be good if it was possible to select all posts in the list.