Download the PHP package wieni/wmpathauto without Composer
On this page you can find all versions of the php package wieni/wmpathauto. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download wieni/wmpathauto
More information about wieni/wmpathauto
Files in wieni/wmpathauto
Package wmpathauto
Short Description Dynamic path aliases, pathauto patterns & automatic updating of aliases
License MIT
FAQ
Example:
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 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.
Informations about the package wmpathauto
wmpathauto
Dynamic path aliases, pathauto patterns & automatic updating of aliases
Why?
- Create dynamic path aliases and pathauto patterns, for the cases where tokens are too limited
- Automatically update an entity alias when other entities that were used to build this alias are updated
Installation
This package requires PHP 7.1 and Drupal 8 or higher. It can be installed using Composer:
How does it work?
Dynamic path aliases
Sometimes when defining pathauto patterns, you'll notice the token
system is just too limited. This module supports building patterns and
aliases in code using plugins with annotations, respectively
@AliasBuilder and @PatternBuilder.
Dependencies
When updating an entity with a path alias, all entities, configs and other path aliases that were used to build that alias are stored in the database. In the future, when one of those path aliases, entities or configs are updated, the path alias that depends on them will be automatically regenerated.
There are multiple ways to define dependencies:
Automatic dependencies with tokens
When your pathauto pattern uses supported tokens, dependencies will be
automatically added based on those tokens. For example, if your pattern
contains the [site:name] token, the aliases using this pattern will be
regenerated when the site name is changed.
Support for more token types can be added by creating plugins with the
@PatternTokenDependencyProvider annotation, defining the token type in the
type parameter and implementing the
PatternTokenDependencyProviderInterface interface.
Manual dependencies using plugins
Dependencies can also be added manually by creating plugins with the
@EntityAliasDependencyProvider annotation, implementing the
EntityAliasDependencyProviderInterface interface. Plugins with AliasBuilder or
PatternBuilder annotations implementing the same interface are also
considered.
Changelog
All notable changes to this project will be documented in the CHANGELOG file.
Security
If you discover any security-related issues, please email [email protected] instead of using the issue tracker.
License
Distributed under the MIT License. See the LICENSE file for more information.
