If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Pushing changes Pushing changes to GitHub as pull request Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Processing repository with scripts Pre commit processing

Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Automatically receiving changes from Bitbucket Automatically receiving changes from GitLab Pushing changes Merge or rebase Interacting with others Lazy commits Pre commit processing of translations Example - generating administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors. See also https://docs.djangoproject.com/en/1.6/ref/settings/#admins ALLOWED_HOSTS

Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Automatically receiving changes from Bitbucket Automatically receiving changes from GitLab Pushing changes Merge or rebase Interacting with others Lazy commits Pre commit processing of translations Example - generating administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors. See also https://docs.djangoproject.com/en/1.6/ref/settings/#admins ALLOWED_HOSTS

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Pushing changes Pushing changes to GitHub as pull request Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Pre commit processing of translations Example - generating

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Pushing changes Pushing changes to GitHub as pull request Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Processing repository with scripts Post update repository

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Pushing changes Pushing changes to GitHub as pull request Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Processing repository with scripts Post update repository

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed language codes Changing language defintions Continuous translation Updating repositories Avoiding merge conflicts Automatically receiving changes from GitHub Automatically receiving changes from Bitbucket

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Automatically receiving changes from GitLab Pushing changes Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Processing repository with scripts Post update repository

foreign key would be category_type_id. Join tables, used in hasAndBelongsToMany (HABTM) relationships between models, must be named after the model tables they will join, e.g. users HABTM groups would be joined apes_zoos is better than zoos_apes. All tables with which CakePHP models interact (with the exception of join tables) require a singular primary key to uniquely identify each row. If you wish to model a table attribute. CakePHP does not support composite primary keys. If you want to directly manipulate your join table data, use direct query calls or add a primary key to act on it as a normal model. For example:

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed language codes Changing language defintions Continuous translation Updating repositories Avoiding merge conflicts Automatically receiving changes from GitHub Automatically receiving changes from Bitbucket