# Allow login to a read-only site

**URL:** <https://meta.discourse.org/t/allow-login-to-a-read-only-site/54270>\
**Category:** Feature\
**Tags:** read-only\
**Created:** [14 Diciembre, 2016 22:30 UTC](https://meta.discourse.org/t/allow-login-to-a-read-only-site/54270 "2016-12-14T22:30:30Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [15 Diciembre, 2016 19:22 UTC](https://meta.discourse.org/t/allow-login-to-a-read-only-site/54270/5 "2016-12-15T19:22:19Z")

</div>

> [@steef](#):
>
> Or maybe a special URI specifically to disable read only mode?

Yeah. If I’d thought ahead to have an API key I probably could have fixed it that way. One of my plans is a remote control panel to do things like that. I think that there are a handful of tasks that it would be handy to be able to do via API calls via a remote web interface. Things like:

- Creating sets of categories with certain colors and permissions for a particular purpose
- control settings for sets of users
- help to walk a user through Wordpress integration

It seems a little bizarre to build a web interface to remotely control a web app, but plugins get stale, and hosted people can’t install them anyway.

---

_[View the full topic](https://meta.discourse.org/t/allow-login-to-a-read-only-site/54270)._
