Path not created when posting story with BlogAPI
| Project: | Pathauto |
| Version: | 4.7.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Summary
Using two different blog posting clients—MarsEdit and Flock on Mac OS X—new stories posted via BlogAPI to my Drupal 4.7.4 site with the Pathauto module enabled do not get Pathauto-generated URLs.
Steps to reproduce
Set up a Drupal site. Install/enable Pathauto and BlogAPI.
Connect to the Drupal site using a blog posting client, like Flock. Flock is a good choice because it autoconfigured very well for me (just tried today, Wednesday, January 3, 2007) and it is cross platform for Mac/Windows/Linux.
Post a new story node using the posting client.
Verify that the new story uses its node path, not a Pathauto-generated one, by default.
Expected results
The new story node should be posted and receive a Pathauto-generated URL, just as it does when a story is created through Drupal’s Web interface.
Actual results
A new story posted through a client like Flock does not receive a Pathauto-generated URL.
Notes
This node also describes the same problem, but does not appear to be in the issue tracker.
I can add the URLs manually through the Drupal Web interface, but I’d rather not have to; that’s the reason I want to use a posting client in the first place. :) Thanks!
#1
Note that this has been reported previously and was fixed: http://drupal.org/node/91306
#2
Thanks for the reply. I’ll double check which version I have installed. I did a search to try to find other reports of the same kind, but didn’t see any reported issues, just other posts; apologies if I pointed out something that had already been fixed.
#3
That's no problem about the duplicate - I've gotten to know the issue queue a little too well in the past few months since I started maintaining pathauto :)
And yes, if this problem has cropped up again or if it still exists once you update pathauto to the latest version then please reopen this issue.