Questions about compatability

Sorry about taking so long to get back to you on this.

1) Yes you are correct, at the moment EveryBlog is not guaranteed to be compatible with other modules. However, frequently it does in fact work. Blog Theme integration has been added to EveryBlog in version 1.3. Version 2.0 of EveryBlog is going to see a major rethinking in how things are done and will keep in mind the number of modules that already exist for Durpal's core Blog module. However, if EveryBlog gains enough popularity I would be happy to see other module developers supporting EveryBlog in addition to the core Blog module, however, I would warn developers to hold off till version 2 of EveryBlog is released.

2) Currently there is no mechanism for copying over existing blog posts. However, this should not be that difficult to add. I will think about adding migration support to EveryBlog, perhaps it will be in 1.4, however, if you are really interested in moving to EveryBlog soon, I could write up migration code and release it (at least to you) much earlier.

3) EveryBlog doesn't directly work with PathAuto, however it does have "pretty" paths. From the EveryBlog project page:

To go straight to a blog you can use:
"www.yoursite.com/blog/Your_Blog_Name"

There are also several ways to get a list of blogs on a site:
1) Going to "www.yoursite.com/blogs" shows a list of all the blogs on the site alphabetically.
2) Going to "www.yoursite.com/blogs/user" shows a list of the blogs grouped by the user that created them.
3) Going to "www.yoursite.com/blogs/category/" shows a list of blogs grouped by category.
4) Going to "www.yoursite.com/blogs/user/johndoe" shows a list of all the blogs by the user 'johndoe'
5) Going to "www.yoursite.com/blogs/category/projects" shows a list of all the blogs in the category 'projects'.

So you can see that EveryBlog does use nice-looking easy to use paths for accessing blogs and lists of blogs.

If you have anymore questions, or I didn't answer one of these very well, don't hesitate to ask.

Regards,
NTroutman

I just added migration code to the dev release 6.x-1.x (http://ftp.drupal.org/files/projects/everyblog-6.x-1.x-dev.tar.gz) which should be updated tomorrow (it only gets recompiled twice a day), or you can download it from this post. Let me know how it works if you decide to use it.

Regards,
NTroutman

Did you add migration to the Drupal 5 version too?
I would love to use everyblog too :)

First, this is a great idea. Multiple blogs under a single user are a great idea. However . . .

There are apparently still issues with migration of existing blogs, even in the development code. I chose the migrate option and nothing happened, other than there being no way for me to edit old blogs. I can still get to them if I know their node ID, but they were not migrated. Any thoughts? How can I get my blogs migrated without resorting to restoring my old data. Heck, if I knew what SQL fields are affected, I would be willing to run a MySQL command to run through existing posts and force the issue that way.

I did use the 2.0 code, by the way, to install and migrate. Let me know if there is something else I can do.

Take care out there.

-- Marcel

Oops, looking at the Apache error logs, I see the following.

PHP Fatal error: Callto undefined function everyblog_blog_loar() in sites/all/modules/everyblog/everyblog.pages.inc on line 539

Ideas?