Download the PHP package partnermarketing/translation-bundle without Composer

On this page you can find all versions of the php package partnermarketing/translation-bundle. 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 partnermarketing/translation-bundle

Informations about the package translation-bundle

TranslationBundle

Build Status Scrutinizer Code Quality Code Coverage HHVM Status

TranslationBundle is a translation component supporting supporting different translation adapters -- by default, OneSky.

The existing adapters are:

Workflow

When you're developing you should add all translation keys into a file under app/Resources/base-translations.

When you pull translations those will be placed in Symfony 2 standard directory for translations app/Resources/translations.

The directory structure should be similar to the one in base-translations directory, but all files will have an extension to the name.

e.g.

After translation will become:

How to configure

in your parameters.yml

How to use

See documentation in Symfony 2.

How to push translations

How to pull translations

This will pull all latest translations into app/Resources/translations. If base language translations were changed their values will be updated in app/Resources/base-translations.

How to run tests

Since phpunit is a dependency you can run tests using:

How to contribute

All versions of translation-bundle with dependencies

PHP Build Version
Package Version
Requires php Version >=5.4.0
onesky/api-library-php5 Version ~1.0
symfony/filesystem Version ^2.7
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 partnermarketing/translation-bundle contains the following files

Loading the files please wait ....