GNOME Bugzilla – Bug 156855
WordPress set-up
Last modified: 2009-08-15 18:40:50 UTC
Currently CVS sets up a WordPress blog in the preferences by appending '/wordpress/xmlrpc.php' to the Base Blog URL. A better solution might be to only append '/xmlrpc.php'. This way depending on how they installed WP, they would still be able to use Gnome-Blog. ex. if 'http://foo.org/' contained xmlrpc.php they would be unable to set-up Gnome-Blog.
Created attachment 33223 [details] [review] blogger_prefs.py patch to modify WordPress preference Here's a patch for the change I suggested.
I've tenatively added this patch, thanks for sending it. Isn't wordpress/xmlrpc.php the default though? I'd like people who know as little as possible to set things up as easily as possible. You can always do a custom blog type if you've done tweaks to your wordpress install?
That would probably be fine.
I'm just curious if wordpress/xmlrpc.php is the default... I actually have no idea, so you'll have to guide me here! I just looked it up on the web and guessed since I don't have wordpress myself.
The default is wordpress/xmlrpc.php, but a lot of people tend to modify the install to the 'top level' of their webroot, so their url wouldn't be like 'http://example.com/wordpress/index.php'. I believe in WP 1.2, they've modified it so you can have 'index.php' in the webroot, instead of the installation directory. Most likely the only people not using the wordpress directory set-up will be people that install Wordpress before 1.2 (like me). So, based on this I think your right not to apply the patch.
*** Bug 163784 has been marked as a duplicate of this bug. ***
Cool, thanks Brian
*** Bug 163965 has been marked as a duplicate of this bug. ***
If this setting is made only to make things simpler, i can't agree, but it's just my opinion, if you install your wordpress in any other directory than the default wordpress (i suppose most people will change that, because it is not a "cool" url) you have to choose non-obvious settings, like "Self-run Custom MetaBlog" which don't make any sense ... Wouldn't simply be easier if you ask the user to point to their xmlrpc.php file (also think about people who have a wropress blog hosted by someone else like blogspot.com) I think keeping the default install directory as default ending isn't a good thing :)
*** Bug 316182 has been marked as a duplicate of this bug. ***
The default installation is that the blog url is http://example.com/wordpress/ , with the API at http://example.com/wordpress/xmlrpc.php . Putting index.php in a different directory from the xmlrpc.php file requires manually copying files and adding a couple of lines of PHP to index.php. So the default blog URL with WordPress is http://example.com/wordpress/ - it seems to me that this is what the user would reasonably put in the 'Base Blog URL' field. Currently, the user has to supply a different 'Base Blog URL' from the URL used to access the blog, which strikes me as counter-intuitive.
While I appreciate that this bug is closed, it might be useful to examine the HTML returned from the URL that the user actually specified; most WordPress blogs will have a pingback link that points to the xmlrpc.php file: <link rel="pingback" href="http://example.org/somefolder/xmlrpc.php" /> which could conceivably be parsed and used if <enteredurl>/wordpress/xmlrpc.php doesn't seem to exist.