Hi,

I'd love to use this module but without the blog module. We did set up our own blog content type and don't need a blog per user, all those links, lists and other overhead the blog module gives us. Its a nice module but just not needed for our site. My understanding of this module is more like a remote editor for any content type not just one called "blog".

Why does this module depend on the core blog module?
Can it run independently?

CommentFileSizeAuthor
#3 620920_remove_dependency-D6-v1.patch684 byteskars-t

Comments

jrglasgow’s picture

I suppose that the module doesn't NEED the blog module. Off the top of my head I cannot think of any reason that the module would break if the dependency was removed.

I ported the code from the Blog API module and it had that dependency listed... so I haven't tested it without the blog module.

you can test it your self and let me know how it goes.

All you have to do to remove the blog dependency is go to your wlw_blogapi.info file and remove the line

dependencies[]=blog 
kars-t’s picture

Status: Active » Postponed (maintainer needs more info)

I wouldn't have started to think about this if the core module had this dependency ;)

If I browse the blogapi CVS I can't where this would come from. So I believe its not necessary for the module.

I will remove the dependency on my site, try to get livewriter running and come back here if it succeeds. Than will make a small patch and you can test and decide what to do. :)

kars-t’s picture

Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new684 bytes

Okay I did test this excessively and I have no problems blogging. This works really great. Tags, images, text, just everything! Thanks for the module! :D
Mini patch applied. Please think about this.

jrglasgow’s picture

Status: Needs review » Fixed

I have committed this patch

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.