Download the PHP package upstatement/ups-editorial-wp-plugin without Composer

On this page you can find all versions of the php package upstatement/ups-editorial-wp-plugin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of upstatement/ups-editorial-wp-plugin

Informations about the package ups-editorial-wp-plugin

Upstatement Editorial

A WordPress plugin for enhancing the editorial experience, including some common customizations for the Gutenberg editor.

Table of Contents

What This Plugin Does

The purpose of this plugin is to tailor the Gutenberg editor experience to be better suited to editors using their WordPress theme and to add functionality common to many websites. Features added as a part of this plugin fall into three categories: block modifications, editor plugins, and core enhancements. This plugin also exposes some global functions that can be used in theme templates.

Blocks

Extended Blocks

The following blocks are extended typically at the registration hook (blocks.registerBlockType) to limit the number of available options for an editor. Some blocks also hook into the edit lifecycle (via the editor.BlockEdit hook) to add additional classes and structure to the editor markup so as to be able to control certain aspects of the block's settings with css.

Note that you can continue to extend core block functionality in your theme by using WordPress's blocks.registerBlockType and editor.BlockEdit filters.

Editor Plugins

Our main Gutenberg "plugin" adds two panels to the main sidebar of posts: the Article Topper & Authors panels.

Article Topper Panel

The article topper panel controls article post metadata concerned with the article topper. This includes:

Authors Panel

The Authors panel allows editors to assign multiple authors to the author byline. This process starts with the Authors section under Posts, where you can create author profiles.

These authors also serve as taxonomies for your articles, so archive pages full of an author's own content are auto-generated on your behalf.

Core Enhancements

Template functions

This plugin exposes a few functions that can be used to retrieve relevant values handled by the plugin. See the Theme API section for information about the available functions.

Theme configuration

By default, all features of this plugin are enabled once the plugin is activated. However, you are able to configure the plugin's functionality (including disabling certain features) via a configuration file that can be added to your theme.

To set up a configuration file, add a ups-editorial.php file to your theme's root that returns an array containing the relevant configuration options:

Configuration

author_panel

Allowed types: boolean

Default value: true

Enable or disable the plugin's Author taxonomy, as well as the Gutenberg editor panel containing the mechanism to add and manage authors for an individual post.

article_topper_panel

Allowed types: boolean

Default value: true

Enable or disable the registration of fields for article toppers and the Gutenberg panel that controls those fields.

attachment_credit

Allowed types: boolean

Default value: true

Enable or disable the registration of a credit field for attachments.

extended_blocks

Allowed types: array

Default value:

A list of blocks that are extended by the plugin. To disable the extension of a certain block, exclude it from this array.

enable_block_styles

Allowed types: array

Default value: array()

WordPress core includes style options for some core blocks. This plugin removes those style options by default, but this parameter can be used to re-enable the core style options for specific blocks. The following blocks have core styles that can be re-enabled via this parameter: button, image, quote, separator, table.

Theme API

There are a few globally-available functions that can be used by your theme to retrieve data defined by this plugin's functionality. These functions are defined in the Template.php file at the root of the plugin directory, and exist under the Upstatement\Editorial namespace.

It is recommended that your theme implement these functions wrapped by a function_exists check to prevent undefined errors in the case that the plugin is disabled. For example:

get_post_authors

Retrieve a list of authors for a post.

Parameters

post

    Post to retrieve authors for. Leave blank to use the current global post.

field

    The field to return for each author. This can be any property from a WP_Term object. Leave blank to return the entire WP_Term object.

Return

Returns an array consisting of author data. If field is blank, this will be an array of WP_Term objects. If a field is specific, this will be an array of values for that field.

get_post_overline

Retrieve the overline category for a post.

Parameters

post

    Post to retrieve the overline for. Leave blank to use the current global post.

Return

Returns the WP_Term object of the category term identified as the overline, or null if none is set.

Troubleshooting

"I've updated the content in the Editorial sidebar, but it's not appearing in the preview."

This is a known issue with Wordpress Gutenberg where post meta doesn't save until the Update button is pressed. We're currently tracking the main issue at WordPress/gutenberg#14900, but until then you can try one of the following steps:

Block validation and recovery

When changing the saved markup of existing or new components, you are likely to come across an issue with block validation.

This error occurs when the markup of a block on last save doesn't match the markup of the block when it loads within the editor.

If this error was intentional, the easiest way to bypass the issue is:

  1. In the top right corner of the block, press the three dots.

  2. Select the Attempt block recovery option. This will re-render the block markup according to the latest version of the save function.

  3. Update the post to save the latest block markup.

If the error was unintentional, your console will be the best place to identify what went wrong. That may look something like this:

In the case above, there was a new cite element added to the markup after the block was already saved to the post. At this point you can either (1) choose the Attempt block recovery option to update the markup, (2) remove and recreate the block, or (3) revert the save function to remove the cite element.

Local Development

To make changes to this plugin, you can download this repository and add it to the plugins/ directory of any running WordPress instance. You'll also need to perform some setup steps to ensure that you have all the built dependencies:

To start working locally, you'll need the following things on your machine:

Once the above are installed, you can get set up with the following steps:

  1. Ensure you're running the expected version of Node:

  2. Install Node dependencies:

  3. Install composer dependencies and generate autoloaders:

  4. Watch the plugin files for changes:

You can build the static front-end assets at any time with the following script:

Resources

During the development of this plugin, we found the following resources to be useful:

All versions of ups-editorial-wp-plugin with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package upstatement/ups-editorial-wp-plugin contains the following files

Loading the files please wait ....