jwong.dayspring

<p>Copy Post removes the tedium of having to copy content, comments, and tags manually from one instance to another.  It also preserves the original post author and date.</p>
<p>Copy Post was originally written when we were preparing to launch a public blog and wanted to pre-populate it with content from our in-office blog that we had been using for the past two years.  If our marketing team thinks that something originally posted to our in-office blog would be helpful or meaningful to others outside of our company, they can easily copy it to the public blog.<br />
Copy Post could also be used in a situation where multiple WordPress instances are used in a development/staging/production setup.</p>
<p>First, a few assumptions and caveats.</p>
<ul>
<li>You must have access to the MySQL database of the destination blog.</li>
<li>The author of the post you are copying must have an account on the destination blog with the same login name, though the IDs don’t have to be the same.</li>
<li>Categories assignments are not copied over, mainly because in our case the categories on the two blogs are different and were going to be edited anyway.</li>
<li>Comments attributed to registered users retain this attribution only if the commenter has an account on the destination blog (just like the author).  If the commenter doesn’t have an account, the comment is still copied, but it’s treated as if it were made by an unregistered visitor.</li>
</ul>
<p>Use the copy post feature to send a post to a destination blog.  You’ll need the post ID, which is available by looking at the edit link for the post.  The plugin will copy the post content, tags, and comments.  The original author and post date will be retained.  All category information will not be copied over.  The resulting post will be set as a “private” post to allow you to set the categories and make edits before it goes live.  Also, you’ll need to be an admin on the source blog to use the plugin.</p>
<p>The settings for the destination blog are configured directly in the WordPress Admin interface, making it possible for us to distribute the plugin to anyone who would need it.</p>


Copy Post

Copy Post allows you to copy posts from one instance of WordPress to another.

nicolasdra

<h3>DEPLOY WEBHOOK GITHUB ACTIONS PLUGIN</h3>
<p>A WordPress plugin to manually trigger a deploy workflow via the Github Actions REST API after updating content.</p>
<h3>FEATURE</h3>
<p>Trigger a deploy workflow via Github Actions after updating content. Users with manage_capabilities are only allowed to perform the action from the the WordPress admin menu.</p>
<h3>SETTINGS</h3>
<p>Fill out the form with the data required on the Settings Page. Find a reference below:</p>
<p>OWNER: The username or organization name that owns the repository.<br />
REPO: The name of the repository.<br />
WORKFLOW_ID: You can either write the full name of your .yml file, ie. “manual-trigger-workflow.yml” or the ID of the workflow that you want to trigger. You can find the ID of a workflow by going to the “Actions” tab of your repository on GitHub, clicking on the name of the workflow, and looking at the URL of the page. The ID is the number that appears after the last forward slash in the URL.<br />
PERSONAL_ACCESS_TOKEN: A personal access token (PAT) with the repo scope. You can create a PAT by going to “Settings” > “Developer settings” > “Personal access tokens” in your GitHub account.<br />
REF: The name of your repository’s main branch. Important: At the moment the plugin is able to create a webhook for a workflow_dispatch trigger without inputs. This feature is planned for later versions.</p>
<h3>TO DO</h3>
<p>Add feature: accept inputs.</p>
<h3>AUTHOR</h3>
<p>Created by Nicolás di Rago.<br />
https://www.nicolasdirago.com/</p>


Copy Post vs Deploy Webhook Github Actions