Download the PHP package seravo/wp-palvelu-plugin without Composer

On this page you can find all versions of the php package seravo/wp-palvelu-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 seravo/wp-palvelu-plugin

Informations about the package wp-palvelu-plugin

Seravo.com

Seravo Must-use Plugin

Build Status Latest Stable Version Total Downloads Latest Unstable Version License

Enhances WordPress with Seravo.com specific features and integrations (also known as WP-palvelu.fi in Finland).

Installation

In order to use this with composer you need to add this mu-plugin:

https://github.com/roots/bedrock/blob/master/web/app/mu-plugins/bedrock-autoloader.php

This is because WordPress won't use mu-plugins from their own folders.

Then add this to your composer:

Seravo's customers can simply run wp-seravo-plugin-update to get the latest (tagged) release. For the adventurous, get the git master head with wp-seravo-plugin-update --dev.

Features

Filters

You can insert your own admin notice for users that are in shadow

Currently the velocity of development is so high that documentation lacks badly behind. To find more filters, just search the source code for apply_filters.

Development

Using a real site for development

Some of the features in the Seravo Plugin depend on the API that is available only on a real production site, and thus cannot be tested inside a Vagrant box or the like.

In order to have the git repository on your own computer and in your own editor, while still being able to see the code running on a test site (in the production environment) you can use the command below. It will watch all files for changes and automatically rsync them to the remote server:

Installing development dependencies

To ease Seravo Plugin development, composer should be used to install development dependencies. Running composer install installs PHPCS, PHPCBF, WordPress PHPCS standards and Rector.

Updating translations

Remember to update translations of all public facing string by running inside Vagrant:

NOTE! If this fails on PHP Fatal error: Uncaught Error: Maximum function nesting level of '256' reached temporarily remove the overly complex files with rm js/cruft*.

Translations can be done for instance by using Poedit. On editor open languages/seravo-fi.po and select Update from pot file which will update the po file. After translating compile the po file to seravo-fi.mo mo file.

Running Rector and PHPCS

If you have Rector and PHPCS installed locally with composer install, simply run composer test. Alternatively run PHPCS inside local Vagrant or Docker image, or on the same remote site used for testing:

Rector and PHPCS errors can be automatically fixed with composer fix. All Rector errors should be resolved before merging to master even if it's not part of CI tests.

Changelog

See git history and release commit messages.

All versions of wp-palvelu-plugin with dependencies

PHP Build Version
Package Version
Requires php Version >=7.0
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 seravo/wp-palvelu-plugin contains the following files

Loading the files please wait ....