Download the PHP package wdb/wdb-language-fallback without Composer

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

TYPO3 extension wdb_language_fallback

The extension is solving some issues with language fallback in TYPO3.
Scenario to develop the extension was the following case:

TYPO3 never works correctly and displays German as fallback for Italian which is wrong.
This extensions verifies the data and is assigning the right language as Fallback.

Concerning powermail this extension shows the forms correctly but the forms can't be sent because the form-fields include wrong variables. The professional distribution is fixing this issue and might be able to solve issues in other special extensions too.

Languages can be configured, an example configuration with the mentioned scenario can be found in the file ext_typoscript_setup.txt (see below).

Installation:

Download the extension from TER or github. Composer installation is possible too.
If you download the extension by extension-manager from TER it will be easily installed.
If you download it from TER as zip-archive, save the archive in the folder typo3conf/ext/ of your installation and unpack it in a new folder wdb_language_fallback.
If you want to install by composer execute composer require wdb/wdb-language-fallback.

Requirements:

A running TYPO3 installation with correct configuration including Site Configuration which includes the language setup.

Configuration:

Activating the extension by language

Configuration is done in the file ext_typoscript_setup.txt of the extension. In a single-domain Installation it can be probably overwritten in the TypoScript-Setup in the TYPO3-backend. For a multi-domain-setup Tests are required first, contact me if you need corresponding functionality.
This is the configuration which can be adjusted to individual needs:

Lines with values 0 like fr = 0 could be removed and are only added to include all used languages in the file.
Languages which are configured in config.wdb_language_fallback_pro.activeForLanguages with the value 1 will activate this extension for correcting the fallback. Usage of this extension is usually not required for simple fallback to the default language.

If you configure config.wdb_language_fallback_pro.activeForLanguages.languageAspect with the value hreflang then config.wdb_language_fallback_pro.activeForLanguages has to be configured a bit different (assume italian again as language which is activating this fallback extension):

The option hreflang has the advantage enabling the extension more granular. Assume you've a site with the values it-FR, it-CH and it-IT, then it's possible to enable the extension for only one of them even the typo3Language or twoLetterIsoCode for all of them has the value it.

Intrinsic fields (only in pro-distribution)

Intrinsic fields are fields where the value in the translated record is taken from the original language, so the value in the translated record is ignored.

This is required in the extension powermail to provide the same variables in forms independent of the language. Other extensions might need this option too, so in general this option could solve some extension related problems.

The configuration for this option related to the extension powermail:

all keys on level below intrinsicFields are tablenames for the extension, then the intrinsic fieldnames are values whereas the keys are just counting numbers starting with 0 for each table.
Concerning this use-case the field uid for every table is in every language the same, in some tables still other field-values are the same too, it's obvious that in this case with these fields relations between the different tables are saved.
This option intrinsicFields related to powermail provides usage of the same variables in forms for every language and grants that the submitted form can be evaluated.

Support

Any questions and issues can be posted as issues on
https://github.com/DavidBruchmann/wdb_language_fallback/issues

Wiki:
https://github.com/DavidBruchmann/wdb_language_fallback/wiki

Source:
https://github.com/DavidBruchmann/wdb_language_fallback

Documentation (this file):
https://github.com/DavidBruchmann/wdb_language_fallback/tree/master/README.md

Homepage:
https://webdevelopment.barlians.com

Disclaimer:

This extension was developed with much care about several issues but

Professional distribution:

The professional distribution is shipped as wdb_language_fallback_pro, it covers support of powermail and other extensions.
Please contact me for price and amount of required licenses.
Please provide a list of extensions that have to be supported, so that untested extensions can be tested.

Extensions that have been tested together with this language fallback extension:

Sponsoring:

You can support development and maintenance of this extension by PayPal. For info about our bank-account please file a personal request.

PayPal: https://paypal.me/SophieBarlian

Contact:

e-mail: [email protected]
skype: david.bruchmann-web

If you contact me by skype, please use a profile picture where no nudity or other offensive content is shown, else your contact-request will be declined. Also an offensive user-name might be a reason for me to decline a contact-request.

Related to the following issues:

TODO:

Changelog:

[2019.08.15][v1.3.0] fix sys_file_metadata needs null instead of false #9 [2019.08.14][v1.2.0] fix return value for missing results (false), add annotations and comments, remove version from composer.json, fix missing usage of initTsfe() [2019.08.06][v1.1.1] reformat and add TODOs and chapter intrinsicFields in README.md
[2019.08.06][v1.1.0] fix coding-faults
[2019.08.05][v1.0.2] Add sponsoring link in README.md
[2019.08.05][v1.0.1] fix constraint in composer.json, change in README.md
[2019.08.05][v1.0.0] Initial release

All versions of wdb-language-fallback with dependencies

PHP Build Version
Package Version
Requires typo3/cms-core Version ^9.5
typo3/cms-frontend Version ^9.5
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 wdb/wdb-language-fallback contains the following files

Loading the files please wait ....