New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Force login to make the site private - Gozer | Forzar acceso para hacer privado el sitio - Gozer | Details |
Original current |
|||
| ↑ | Force visitors to log in before accessing your site with extensive exception controls. | Fuerza a los visitantes a iniciar sesión antes de poder acceder a tu sitio web con múltiples controles de excepción. | Details |
Original current
Force visitors to log in before accessing your site with extensive exception controls.
CommentShort description. You have to log in to edit this translation. |
|||
| Since 2.1.0 Gozer reads the visitor IP from the direct connection by default, because trusting proxy headers on sites not behind a proxy allowed anyone to impersonate an allowed IP by forging a header. Behind Cloudflare or a reverse proxy, the direct connection is the proxy itself, so go to Settings > Gozer > "Visitor IP detection" and select the header your infrastructure sets (CF-Connecting-IP for Cloudflare, X-Real-IP or X-Forwarded-For for other proxies). Your IP whitelist will work as before. | Desde la versión 2.1.0, Gozer lee la IP del visitante a partir de la conexión directa por defecto, ya que confiar en las cabeceras del proxy en sitios que no se encuentran detrás de un proxy permitía a cualquiera suplantar una IP autorizada falsificando una cabecera. Detrás de Cloudflare o de un proxy inverso, la conexión directa es el propio proxy, así que ve a «Ajustes > Gozer > Detección de la IP del visitante» y selecciona la cabecera que establezca tu infraestructura (CF-Connecting-IP para Cloudflare, X-Real-IP o X-Forwarded-For para otros proxies). Tu lista blanca de IPs seguirá funcionando como hasta ahora. | Details | |
Original current
Since 2.1.0 Gozer reads the visitor IP from the direct connection by default, because trusting proxy headers on sites not behind a proxy allowed anyone to impersonate an allowed IP by forging a header. Behind Cloudflare or a reverse proxy, the direct connection is the proxy itself, so go to Settings > Gozer > "Visitor IP detection" and select the header your infrastructure sets (CF-Connecting-IP for Cloudflare, X-Real-IP or X-Forwarded-For for other proxies). Your IP whitelist will work as before.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If "Search engine bots" is enabled (the default), yes: bots are recognized by their user agent, which any visitor can set freely, so a curl request claiming to be Googlebot gets through. If your site must stay private to everyone except real search engines, enable "Verify bots by reverse DNS": Gozer then confirms the claim with a forward-confirmed reverse DNS lookup against the engine's official domains (Google, Bing, Yahoo, Yandex, Baidu, and Apple) and blocks impostors, as well as bots that cannot be verified this way (such as social network preview fetchers). If the site should be completely hermetic, disable the "Search engine bots" exception altogether. | Si la opción «Bots de motores de búsqueda» está activada (es el valor por defecto), sí: los bots se reconocen por su agente de usuario, que cualquier visitante puede imitar, por lo que una solicitud «curl» que afirme ser Googlebot pasa sin problemas. Si tu sitio debe permanecer privado para todo el mundo excepto para los motores de búsqueda reales, activa «Verificar bots mediante DNS inverso»: Gozer confirma entonces la identidad mediante una consulta de DNS inverso con confirmación directa contra los dominios oficiales de los motores (Google, Bing, Yahoo, Yandex, Baidu y Apple) y bloquea a los impostores y a los bots que no se pueden verificar de esta forma (como los programas de obtención de vistas previas de redes sociales). Si el sitio debe ser completamente hermético, desactiva por completo la excepción «Bots de motores de búsqueda». | Details | |
Original current
If "Search engine bots" is enabled (the default), yes: bots are recognized by their user agent, which any visitor can set freely, so a curl request claiming to be Googlebot gets through. If your site must stay private to everyone except real search engines, enable "Verify bots by reverse DNS": Gozer then confirms the claim with a forward-confirmed reverse DNS lookup against the engine's official domains (Google, Bing, Yahoo, Yandex, Baidu, and Apple) and blocks impostors, as well as bots that cannot be verified this way (such as social network preview fetchers). If the site should be completely hermetic, disable the "Search engine bots" exception altogether.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| I am behind Cloudflare or a reverse proxy and my allowed IPs stopped working | Estoy detrás de Cloudflare o de un proxy inverso y mis direcciones IP permitidas han dejado de funcionar | Details | |
Original current
I am behind Cloudflare or a reverse proxy and my allowed IPs stopped working
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Can someone fake being Googlebot to see my private site? | ¿Puede alguien hacerse pasar por Googlebot para ver mi sitio privado? | Details | |
Original current
Can someone fake being Googlebot to see my private site?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| <strong>Advanced IP whitelist</strong> - Supports individual IPs, CIDR notation, and wildcards, with configurable IP detection for sites behind Cloudflare or a reverse proxy | <strong>Lista blanca de IPs avanzada</strong> - Admite IPs individuales, notación CIDR y comodines, con detección de IP configurable para sitios detrás de Cloudflare o un proxy inverso | Details | |
Original current
<strong>Advanced IP whitelist</strong> - Supports individual IPs, CIDR notation, and wildcards, with configurable IP detection for sites behind Cloudflare or a reverse proxy
CommentFound in description list item. You have to log in to edit this translation. |
|||
| <strong>Verified bots</strong> - Optionally confirm crawlers by reverse DNS so nobody can fake being Googlebot | <strong>Bots verificados</strong> - Opcionalmente, se pueden confirmar los rastreadores mediante DNS inverso para que nadie pueda hacerse pasar por Googlebot | Details | |
Original current
<strong>Verified bots</strong> - Optionally confirm crawlers by reverse DNS so nobody can fake being Googlebot
CommentFound in description list item. You have to log in to edit this translation. |
|||
| Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just <a href="mailto:gozer@ayudawp.com">contact me</a> and tell me what you need. | ¿Necesitas ayuda individualizada, resolución de problemas prioritaria o una funcionalidad, integración o adaptaciones personalizadas creadas específicamente para tu sitio? Ofrezco soporte privado y desarrollos personalizados. Solo tienes que <a href="mailto:gozer@ayudawp.com">contactarme</a> y decirme qué necesitas. | Details | |
Original current
Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just <a href="mailto:gozer@ayudawp.com">contact me</a> and tell me what you need.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Need private support or custom development? | ¿Necesitas soporte privado o un desarrollo personalizado? | Details | |
Original current
Need private support or custom development?
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| A page cache (a caching plugin, your host, or a CDN) can serve pre-generated HTML without running WordPress, so Gozer never sees those requests. Gozer purges the major caching plugins automatically when you activate the plugin, toggle private mode, or save settings, but if your host or CDN caches HTML you may need to purge it once after enabling Gozer. | Una caché de página (un plugin de caché, tu proveedor de alojamiento o una CDN) puede servir HTML pregenerado sin necesidad de ejecutar WordPress, por lo que Gozer nunca detecta esas solicitudes. Gozer vacía automáticamente las principales cachés de los plugins cuando se activa el plugin, se activa el modo privado o se guardan los ajustes; sin embargo, si tu proveedor de alojamiento o tu CDN almacenan HTML en caché, es posible que tengas que vaciarla después de activar Gozer. | Details | |
Original current
A page cache (a caching plugin, your host, or a CDN) can serve pre-generated HTML without running WordPress, so Gozer never sees those requests. Gozer purges the major caching plugins automatically when you activate the plugin, toggle private mode, or save settings, but if your host or CDN caches HTML you may need to purge it once after enabling Gozer.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you set a "Minimum access level" higher than the user's role, logged-in users below that level are treated like logged-out visitors and shown a 403 page. This front-end restriction is independent from the WordPress dashboard: a Subscriber can still reach their profile screen but will not see the front-end. Set the access level back to "Any logged-in user" to allow every logged-in user through. | Si estableces un «Nivel de acceso mínimo» superior al perfil del usuario, los usuarios conectados que se encuentren por debajo de ese nivel serán tratados como visitantes desconectados, y se les mostrará una página 403. Esta restricción en la parte pública es independiente del escritorio de WordPress. Un suscriptor podrá seguir accediendo a su pantalla de perfil, pero no verá la parte pública. Vuelve a establecer el nivel de acceso en «Cualquier usuario conectado» para permitir el acceso a todos los usuarios que hayan iniciado sesión. | Details | |
Original current
If you set a "Minimum access level" higher than the user's role, logged-in users below that level are treated like logged-out visitors and shown a 403 page. This front-end restriction is independent from the WordPress dashboard: a Subscriber can still reach their profile screen but will not see the front-end. Set the access level back to "Any logged-in user" to allow every logged-in user through.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| I enabled private mode but old pages still load without logging in | He activado el modo privado pero las páginas antiguas siguen cargando sin estar conectado | Details | |
Original current
I enabled private mode but old pages still load without logging in
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Why can a logged-in user still not see my site? | ¿Puede que un usuario conectado siga sin ver mi sitio? | Details | |
Original current
Why can a logged-in user still not see my site?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Gozer the Gozerian is the supernatural entity from Ghostbusters (1984) who asked "Are you a god?" before denying access to mere mortals. Just like our plugin does with your site visitors. | Gozer el Gozeriano es la entidad sobrenatural de «Los cazafantasmas» (1984) que preguntaba «¿Eres un dios?» antes de negar el acceso a los simples mortales. Igual que hace nuestro plugin con los visitantes de tu sitio web. | Details | |
Original current
Gozer the Gozerian is the supernatural entity from Ghostbusters (1984) who asked "Are you a god?" before denying access to mere mortals. Just like our plugin does with your site visitors.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Plugin name.