[Plugin: Logged in] XML RPC blocked
-
This plugin prevents the use of the xmlrpc protocol, and I assume the atom as well. This will upset Jetpack and.the mobile app.
-
Thanks for the heads up, I had not thought of that. The plugin will block/redirect all traffic to the site expect traffic to the login page and admin section. In many cases where I have used the plugin I actually want to block the entire page, but it might be a good idea to add a setting for allowing XMLRPC and Atom.
Yeah – It would be nice to have check-boxes allowing users to enable and disable blocking of XML-RPC, and Atom. Also, it would be nice if we could allow the RSS feeds through as well. One thing I have used the plugin for is hiding pre-production sites from the public, but of course you can’t post from the mobile app if the plugin is enabled.
Also, some people I have spoken to wanted to use it so that their WP install would act a bit like an API, with no front end, but a back end CMS and RSS to get content out. Of course, they can’t do that at the moment.
Thanks for your time.I just released version 1.0.1 with added support for enabling RSS and Atom feeds, I hope that solves your problem. Unfortunately XML-RPC will require some more research so I didn’t have time to add that today, but I’ll hopefully be able to get it done soon.
Pre-production sites as in deed my main area of use as well. I guess todays update would enable you to run a basic RSS/Atom based API using Logged in, but I think for more advanced setups you would probably want to do the redirecting/blocking yourself. But again, the (fairly undocumented) filters in Logged in might prove useful when it comes to deciding how to handle unapproved page loads.
Thanks, Simon. I will try and push the update through soon ish, and that is a big help. I completely understand your issue with XML-RPC – I wouldn’t enjoy doing that either. I did get around the issues by putting the blocking right in the theme, which of course allowed RSS and XML-RPC though, but this should be done with a plugin.
Thanks again for your swift responses and help. Angus.Hi again. Just had a look at XML-RPC, and since all communication is directed at an XML-RPC endpoint located at wordpress/xmlrpc.php is was pretty straight forward. I haven’t pushed it to the WordPress plugins directory yet, thought I’d do some more testing first.
I really appreciate it if you could do a test using the latest version of the plugin, which you can get at my github repo (direct download link), since I’m not that experienced with using XML-RPC or the WordPress iPhone app. Directory should probably be renamed
logged-in
before running, or at least not be allowed to coexists with another version of the plugin.I will try and get that going ASAP, but my conditions aren’t ideal – I have direct access to my server only twice a week, and the rest of the time I have to try and get around the proxies at College that block :22 and :21, which are both kinda important. Thanks anyway for helping. If I find an issue, or something else like that, where will be the most convenient place for me to tell you??
I understand. I you find an issue, please send me an email at simon [at] dessibelle.se. Thanks!
- The topic ‘[Plugin: Logged in] XML RPC blocked’ is closed to new replies.