nikosdion
commented
3 years ago There are no language files here. You asked me to merge main into development which is wrong.
Please fork the repository into your GitHub account. Clone the repository locally. Switch to the development branch locally. Create a new local branch, e.g. lang-ru_RU. Add your language files. Commit them. Push to your cloned repository on GitHub. Make a PR from your repository's lang-ru_RU branch to the development branch on this repository.
I am closing this PR since it's not salvageable.
rigin
Pull Request for Issue # .
Summary of Changes
Russification of the extension
com_engage lib_fof40 plg_actionlog_engage plg_content_engage plg_datacompliance_engage plg_engage_akismet plg_engage_email plg_engage_gravatar plg_privacy_engage plg_system_engagecache plg_user_engage
Testing Instructions
Result before applying PR
Be specific. You may link to one or more screenshots or a video as long as it's not the only clue you leave. Use words to describe what happens.
Result after applying PR
Be specific. You may link to one or more screenshots or a video as long as it's not the only clue you leave. Use words to describe what happens.
Backwards compatibility
Does this PR break backwards compatibility? Is it a minor break (template overrides need to be updated) or a hard b/c break (code interfacing with the public API, e.g. plugins, need to be rewritten)?
If it does break b/c document how it breaks it and what other developers making plugins or template overrides for LoginGuard should do.
Documentation Changes Required
Provide the changes which need to be done per Wiki file. Indicate which Wiki file(s) would need to be created and their proposed names.
Translation impact
Does it add or remove language strings? Which ones?
Technical information
If there are technical considerations which may not be apparent in the code please explain here. For example, why you did something which is not obvious, and you couldn't fully describe with code comments because it spans several files / methods.