Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
timse201 edited this page Jan 23, 2017 · 7 revisions

Language: en, de

No hosting on WordPress.org?

It is often asked why the plugin is "distributed" exclusively via GitHub and not via WordPress.org. The question is legitimate. The reason is the convenience (for me as a developer): With GitHub releases, issues, pull requests and shortcuts can be created quickly and easily. Communication with users is also done via GitHub

On WordPress.org (almost) everything is possible but not without detours. GitHub is just more appealing. When a certain maturity is reached the plugin will be emigrated to WordPress.org.

Would not access protection be a better choice?

Absolute! The .htaccess protection is directly on the server level. The problem lies in the reasonableness of the method: With WordPress instances with numerous (changing) users, the login details administration and user communication are very demanding or not economical.

In summary: The commissioning of an access protection via .htaccess in question - very gladly. Otherwise the use of a 2-factor verification (does not have to be via e-mail) is highly recommended.


Jumping marks