After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 167499 - Looks for XMLRPC file in subdirectory ('wordpress')
Looks for XMLRPC file in subdirectory ('wordpress')
Status: RESOLVED FIXED
Product: gnome-blog
Classification: Other
Component: Blog Applet
0.8
Other Linux
: Normal normal
: ---
Assigned To: GNOME blog maintainers
GNOME blog maintainers
: 169875 523178 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-02-15 17:55 UTC by Chase Urich
Modified: 2010-03-11 18:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch to set custom wordpress path without over-writing current settings (954 bytes, patch)
2006-10-22 11:41 UTC, Huw Lynes
none Details | Review
hange Self-Run Wordpress directory to be given base URL. (975 bytes, patch)
2010-03-05 20:52 UTC, Tommi Asiala
committed Details | Review

Description Chase Urich 2005-02-15 17:55:25 UTC
Distribution/Version: Gentoo;Kernel:2.6.10

I have an install of wordpress in a subdirectory of my domain ('blog'). After
installing gnome-blog, I selected 'Wordpress' as my blog type and entered the
base URL to the blog ('http://www.kc5mpk.com/blog/'). After entering a username
and password I selected "Lookup Blogs". It searches for the xmlrpc.php file in a
'wordpress' subdirectory of my base URL. There is no wordpress subdirectory, so
I have to select Self-Run Other and specify the full path the the XMLRPC file
and ignore any of the default options for Wordpress.
Comment 1 Brian Pepple 2005-02-19 15:50:08 UTC
The 'WordPress' type in Gnome-Blog is set-up to use the WordPress default
installation.  Please refer to bug 156855.
Comment 2 Greg Etling 2005-04-01 05:29:46 UTC
I would agree that the default behavior is fine, except for the fact that it is
hard coded into the blogger_prefs.py file. Therefore anyone installing to a
directory name on their server other than 'wordpress' must hand code the python
file to change it - not a desirable option! Whereas by applying the patch in bug
156855, the user can point to their blog in preferences wherever it is.

Therefore, as an alternate to applying this patch - can we make certain at least
if the user makes the change in gconf-editor, that gnome-blog doesn't overwrite it?
Comment 3 Olav Vitters 2005-05-19 15:59:05 UTC
*** Bug 169875 has been marked as a duplicate of this bug. ***
Comment 4 Huw Lynes 2006-06-10 12:48:28 UTC
OK I've been playing with this today.

Unfortunately the gnome-blog preferences page will overwrite the url_ending field with whatever is contained in blogger_prefs.py . As long as you don't run preferences from within gnome-blog then everything works fine.

It seems unlikely that current users are going to re-run preferences so the patch shouldn't break anything currently working. Even if you do break your currently working setup you can permanenly fix it by changing xmlrpc_url . At the moment people not running site.domain/wordpress/xmlrpc.php installation have no way of permanently fixing their prefs in gnome-blog.

just my 2c
Comment 5 Shannon Eric Peevey 2006-07-16 02:15:32 UTC
Here is a patch that will fix this problem:

--- blogger_prefs.py    2006-07-15 14:39:57.000000000 -0500
+++ blogger_prefs.py.new        2006-07-15 14:41:26.000000000 -0500
@@ -126,7 +126,7 @@
             url_description = _("Base Blog URL:")
         elif blog_type == "custom-wordpress":
             url = None
-            url_ending = "wordpress/xmlrpc.php"
+            url_ending = "/xmlrpc.php"
             protocol = "MetaWeblog"
             url_description = _("Base Blog URL:")
         elif blog_type == "blogger.com":



Comment 6 chris lindley 2006-09-24 20:25:40 UTC
My comment on this is that my Wordpress installation is in the root directory of the website. Therefore currently impossible to use Gnome-Blog. I would like to strongly suggest this is changed!! Well if my opinion is important that is :-)
Comment 7 Huw Lynes 2006-10-22 11:41:30 UTC
Created attachment 75196 [details] [review]
patch to set custom wordpress path without over-writing current settings

this patch takes any existing url_ending and adds it to the url. This makes it obvious what is going on in the dialog box and allows people to add custom wordpress paths without breaking current configurations.
Comment 8 Tommi Asiala 2010-03-05 20:52:33 UTC
Created attachment 155359 [details] [review]
hange Self-Run Wordpress directory to be given base URL.

Change default search path for xmlrpc.php directory for self-run wordpress to
be given base URL instead of base URL + "/wordpress/".

Same as Shannon's patch for current head.

Automatically adding "wordpress" to URL due to default packaging directory is insane.
Comment 9 Tommi Asiala 2010-03-05 21:45:55 UTC
*** Bug 523178 has been marked as a duplicate of this bug. ***