Download the PHP package codeq/advancedpublish without Composer

On this page you can find all versions of the php package codeq/advancedpublish. 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 codeq/advancedpublish

Informations about the package advancedpublish

CodeQ.AdvancedPublish

This package enforces a four-eyes-principle for publishing changes. For that reasons, every user gets an additional workspace, on which changes staged for publication are parked. The user then can request a review from an authorized user, who can then publish the changes to the live workspace. The reviewer can also reject the changes, whereupon the editor can revise the changes and request a new review.

Roles

CodeQ.AdvancedPublish:AbstractReviewer

This role can be used to give users the ability to review changes. Using this role aims at not being fully able to publish changes, but to be restricted later using custom filters in the CodeQ.AdvancedPublish.reviewers.filterImplementations setting.

CodeQ.AdvancedPublish:CanReview

This role can be used to give users the ability to review changes with the aim to be able to publish changes across the site without any restriction.

CodeQ.AdvancedPublish:CanReviewOwnRequests

This role can be used to give users the ability to review their own requests.

CodeQ.AdvancedPublish:CanViewProtocol

This role can be used to give users the ability to view the publication protocol.

CodeQ.AdvancedPublish:SuperEditor

This role is allowed to see the original workspace dropdown in the Neos UI and to switch workspaces. Other users only see a simplified publish button without the option to switch workspaces.

Reviewer Filters

The package provides a flexible system to control which reviewers are allowed to publish specific content. This is implemented through reviewer filters that check if a user has the necessary permissions to publish a node.

How Reviewer Filters Work

  1. Each filter implements the ReviewerFilterInterface and returns a boolean value.
  2. If at least one filter returns true, the reviewer is allowed to publish the content.
  3. If all filters return false, the reviewer is not allowed to publish the content.

Implementing Custom Reviewer Filters

To create a custom reviewer filter:

  1. Create a class that implements CodeQ\AdvancedPublish\Domain\Service\ReviewerFilterInterface
  2. Implement the checkFilterConditionsForUserAndNode method that returns true if the user is allowed to publish the node, or false otherwise
  3. Register your filter in the Settings.yaml configuration:

Example Filter Implementation

Suggested project changes

Deny live publishing and manipulation of workspaces

All versions of advancedpublish with dependencies

PHP Build Version
Package Version
Requires neos/neos Version ^7 || ^8
sandstorm/templatemailer Version ^2
neosidekick/revisions Version *
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 codeq/advancedpublish contains the following files

Loading the files please wait ...