Ubuntu
drivel package

Drivel needs a better Wordpress setup

Bug #129321 reported by James
2
Affects Status Importance Assigned to Milestone
Drivel
Invalid
Wishlist
drivel (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I installed Drivel to use with my Wordpress blog. Although it stated in the package description that Wordpress is supported, when I first opened Drivel there was no option on the drop-down list directly for Wordpress. Reading the FAQ didn't help me very much, I ended up having to guess what the path to my xmlrpc.php file was, as well as select Moveable Type. It should be changed to where Wordpress is an option in the dropdown list, and all that needs to be provided is the username and password. Wordpress is a popular enough blogging site that it needs to be better implemented in what is an otherwise great blogging program.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, seems that you already send it upstream just linking by now: http://bugzilla.gnome.org/show_bug.cgi?id=461948

Changed in drivel:
importance: Undecided → Low
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in drivel:
status: Unknown → New
Revision history for this message
James (chiisu81) wrote :

I did, I'm slowly learning to use Launchpad in all its potential. :) I know this isn't a serious bug or such, maybe should be switched to a requested feature for the next release?

Bug Watch Updater (bug-watch-updater)
Changed in drivel:
status: New → Incomplete
Revision history for this message
Neil Williams (codehelp) wrote :

It is not possible to automate the URL for a wordpress blog because it depends on the individual configuration of that individual server. In many cases, it will be http://myserver/xmlrpc.php but this cannot be assumed and drivel cannot go searching the website for a possible file called xmlrpc.php, it would take too long. It could be any number of levels deep or in a completely different subdomain like http://blog.myserver/ or something.
I'm upstream for drivel and I cannot accept the intention of the bug report as-is. All that is possible is that the FAQ can be improved, as documented in the bugzilla version of this bug report.
I intend to implement the changes described in the bugzilla report into the next release, at which point I will consider both the bugzilla bug and this bug to be closed as I have had no feedback to the bugzilla bug report for 4 months.
Incidentally, this is not just a wordpress issue, it affects ANY blog engine which is user-installable. The only blog engines that are entirely predictable are sites like livejournal and blogger (possibly advogato, need to check that). Therefore it affects my own blog too, which uses serendipity.
If there was a reliable way to fix this, I would but user installable blog engines cannot be predictable, by definition.

Changed in drivel:
status: Incomplete → Invalid
Changed in drivel (Ubuntu):
status: Triaged → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in drivel:
importance: Unknown → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.