Download the PHP package charliedev/fallback-site without Composer
On this page you can find all versions of the php package charliedev/fallback-site. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download charliedev/fallback-site
More information about charliedev/fallback-site
Files in charliedev/fallback-site
Package fallback-site
Short Description Allows sites of a multi-site install to use entries of other sites if a matching slug is found.
License proprietary
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 fallback-site
Fallback Site for Craft 3
This plugin allows each site to fall back to another site when a requested element cannot be found. This allows multi-site installations (typically for multiple languages) to gracefully fall back to existing content if available.
When a request is made for an element that would normally not be found, Fallback Site will check the configured site for an element with the same slug. For example, if you have an English site and a Spanish site as part of your craft install, and English is the fallback for Spanish, then handling for a request to the Spanish site would go as follows:
- First, if an element was found on the Spanish site, everything continues as normal, and Fallback Site does not intervene.
- If an element was not found on the Spanish site, Fallback Site checks if there is an English element with the same the slug.
- If an English element is found, then that element's ID is used to see if there is a Spanish version available, which can happen if an incorrect, untranslated slug is used.
- If a Spanish version exists, then a 301 redirect will be sent to the user, directing them to the correct URL.
- If a Spanish version does not exist, then Fallback Site makes Craft use the English element in place of the Spanish one (With some conditions listed below).
- If an English element is not found, then the request continues as a 404 as normal.
See the flowcharts below which demonstrate what happens when requesting a page, about-us, under a secondary, Spanish site (located at /es) within a multi-site Craft installation.
Normal Craft element handling
Element handling with Fallback Site
Requirements
- Craft CMS 3.0.0-RC1 or above
-
Open a terminal and navigate to your project folder:
-
Require the package to download it via Composer:
- Install the plugin on the
Settings -> Pluginspage in the Craft control panel.
--- or ---
- Install the plugin via the command line:
Configuration
Within the Craft control panel, go to the Settings -> Plugins page, and then look for the Settings button listed by the Fallback Site plugin.
Here, you can select which site acts as a fallback for each other site. Fallbacks can also be chained across multiple sites, each site falling back to the next.
Usage
While the plugin works without any additional configuration, you may want to know if an entry being displayed has been substituted by Fallback Site. This may be done to display notices about the availability of site-specific content, or notify users of the replacement. Detecting this can be done by comparing the current site stored by Craft with the entry's associated site.
Built for Craft CMS by Charlie Development
