Download the PHP package jidoka1902/redirecting-fallbacks-symfony without Composer

On this page you can find all versions of the php package jidoka1902/redirecting-fallbacks-symfony. 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?

Informations about the package redirecting-fallbacks-symfony

redirecting-fallbacks-symfony

Symfony Integration for the "redirecting-fallbacks" project.

Examples

It's all about the configuration.

Basic Configuration

First of all, load the integration and library classes as services. So you can wire them as you need.

After that you can decide what type of routes you want to specify in your configuration files. Either plain paths like "/" and "/blog" or symfony named routes like "app_index".

For Symfony Routing - use the provided FrameworkUrlGeneratorAdapter:

If you prefer plain paths to redirect to use this config:

Gloal Redirect on 404

Now that you know how to configure your prefered path-type - let's have a basic example about one redirect path for all occuring 404 Status Reasons (NotFoundHttpException or plain ResponseCode 404).

è voila! every request resulting in a 404 state will be redirected to "/"

More Precise Redirects depending on Paths

After that basic configuration, lets have a look at how to create more individual 404-redirects. E.g. if someone enters an not found blog url because of a wrong slug which was not found in your storage, should that be redirected to the start-page or do you have a fancy blog post search site? Same here:

But beware! the order of your mappings plays a role.

All versions of redirecting-fallbacks-symfony with dependencies

PHP Build Version
Package Version
Requires php Version ^7.0
jidoka1902/redirecting-fallbacks Version ^1.0.1
symfony/routing Version ^3.4|^4.0
symfony/event-dispatcher Version ^3.4|^4.0
symfony/http-foundation Version ^3.4|^4.0
symfony/http-kernel Version ^3.4|^4.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 jidoka1902/redirecting-fallbacks-symfony contains the following files

Loading the files please wait ....