The short answer is you can’t. GlotPress is designed to let anyone collaborate on the translations.
You might be able to use a WordPress plugin to make your site private, which may work with GlotPress, but since GP doesn’t load a lot of the WP logic for it’s pages you may find they don’t work with GP.
If your comfortable writing code, the permission system is changeable and could probably be modified to require a logged in user with a plugin.
Thread Starter
tyutek
(@tyutek)
Thank you for your reply, Greg.
And thank you for all your additional plugins for GlotPress. You really care about GlotPress.
Yes, collaboration, but collaboration does not mean that whole internet has to see what you are doing there. This is not a website to show everybody on the internet, this is a work. There must be a door to enter that community. Only after that, “real” collaborators can see everything if you want them to see.
I tried 6-7 wp plugins but they are successful only with real wp pages, they don’t have an affect on GlotPress pages. They do not even see GlotPress pages.
If I try to play around with the code, this may take some time. 🙂
Don’t you have any plans about this?
Thank you
At this time there is no short term plans to change the behaviour, however there is an ongoing discussion about how to expand the roles in GP to be more robust and obviously this kind of point is being discussed as part of that.
Give this a try: https://github.com/toolstack/gp-require-login
It’s quick and dirty but will force a user to be logged in to WP before they can see any GP pages.
Thread Starter
tyutek
(@tyutek)
You are incredible, Greg. Only in a few minutes after my request you did it. And it really works. No wonder this project is successful. Thanks to people like you.
