Good work, Mike! I won't have time to try it out for a while so a quick question: what kind of URL structure does mbBlog produce for new pages?

Well unless you use the "blog intro" section, which allows you to have an intro paragraph which then produces a read more link for the user to click through to read the rest of the post in the blog body, then all the posts just list in on one page. (With pagination if there are too many).
If any of that makes sense....

But using my site as an example which has the blog on the homepage, it currently will just display www.mikebarlow.co.uk/?bid=9

for pagination it will be www.mikebarlow.co.uk/?bpage=2

I do aim to use mod rewrite to get nice formatted urls but like i said i wanted to get the base functionality down first while learning wolf, so the urls will come. When it does it will no doubt be a formatted version of the blog title. (Unless people request otherwise)

Thanks for the heads up, I've been using 0.5.5.
I may look into that actually, will probably develop it has 2.x series of mbBlog, while developing 1.x for 0.5.5, especially with 0.6 not being out yet.

I expect it's just a temporary thing, snsmurf, but the link provided is being reported as broken. Can you confirm? Thanks!

Major update to this plugin!
I've done a complete rewrite for this plugin. Now uses dispatcher routes to help get clean urls / paging.

I'll release an "upgrader" in the next day or two, the database table has changed, so bear it in mind and check back in a couple of days if you are already running the original mbBlog.

IMPORTANT EDIT: To use mbBlog you'll have to run the two fixes I've posted on the following two google code issues:
http://code.google.com/p/wolfcms/issues/detail?id=165 and
http://code.google.com/p/wolfcms/issues/detail?id=169

www.mikebarlow.co.uk/wolf-cms.html#mbblog

Last edited by snsmurf (2010-05-12 23:56)

As default, the blog path is set to homepage, meaning the dispatcher routes will take over and redirect your homepage to load the blog posts.
This can be changed in the blog settings by changing the blog path. If you wanted your blog to appear at www.mydomain/my-blog you would type my-blog into the blog path box.

If your blog path is blank and the posts aren't showing on the homepage, are you getting any errors of any kind?
Also if they aren't working, could you provide details about which version of wolf you are using, along with server environment / any modifications you may have made to wolf.

Do you have debug turned on? And if not could you turn it on.

Need to set debug to true in the config.php of the Wolf Root. Hopefully should give some indication if anything is going wrong.

Hmmmm... Not sure what is going on here.
I shall have a look today during my dinner break and get back to you.

Thanks for giving me the heads up on this though, always difficult to catch everything when it's just yourself that tests it!

snsmurf: thanks alot, it works.

However a new issue arrived

First of all: it's taking the wolf theme as a layout.
I checked with the mbcontact topic and found the solution

line 60            $this->setLayout('wolf');

Changed wolf into my theme (using) and problem solved.
just a note here: can this be changed in automatic theme? So it discovers the current theme and adapts?

Then the bigger issue, and saying that php is still at the very beginnings for me to learn, but will search later, maybe i can find the issue, is that the blog post isn't showing.

I made a post, but the URL is different then the blog.

for instance: www.domain.com/blog/ (current root to blog)
blogpost: www.domain.com/view/blogpost-name/
result: 404

Looks like the blog system is automaticly turning on the view/topic on. Maybe because it's not in my route i thought. But as i'm new to this system: when i leave the blog path empty i still see my home page without the blog.

I can spot alot of this in the mbblogcontroller.php:

line 56: $this->assignToLayout('sidebar', new View('../../plugins/mbblog/views/admin/sidebar'));
line 74: if($this->result == 'view')
Line 154      public function view($urltitle)

and index.php:

 Line 52
Dispatcher::addRoute(array( 
    '/'.$blogpath => '/plugin/mbblog/index/', 
    '/'.$blogpath.':num' => '/plugin/mbblog/index/$1',    
    '/'.$blogpath.'view/:any' => '/plugin/mbblog/view/$1'
)); 

What lets me believe the views is coming back everywhere (like in the URL)

I'm still searching, cause changing the view to blog did not help on the frontpage.

Hello,

I'm trying to make mbBlog work on wolf 0.6.0a... but ran into major problems.. so i tried to do the patches but it didn't fix anything.

I was never able to see the public blog. The admin interface works but not the public facing part.

1) say i set the slug to /myblog/ in the mbBlog settings and try to navigate to www.domain.com/myblog I get a 404 error.

2) say i create a Page called "myblog" which I leave blank then it will just display that page.

Also one thing i'm not sure I understand about this plugin is that it replaces completely a "page"? So I can't create a "Blog Page" and just insert the mbBlog content in it? This is not clear in the instructions.

3) if this plugin replace completely a Page then It breaks main menu navigation which just iterates over Published main Pages to create the menu....

I'm sure there is something I'm misunderstanding but the bottom line is that to me, mbBlog doesn't work.

Last edited by Cybrid (2010-06-29 17:08)

I just recently tried setting up the mbBlog plugin and ran into many of the difficulties that others have. I am not sure if a final fix has been found and posted elsewhere, but I managed to get it working fine, so I thought I would share how...

1. I installed and activated the plugin.

2. I set my blog path in the settings to: blog/

3. Needing to get a link to said blog to appear in my navigation menu, I created a child page titled: Blog with a slug of: blog and a breadcrumb entry of: Blog
... I then set the page to Published.

4. I installed the Redirector plugin...

5. I added a redirect so that: /blog redirects to: /blog/

6. In viewlog.php I changed this code: href="/view/
...to this: href="blog/view/
...and then in the same line changed: >/">
...to this: >">

7. In bloglist.php I changed this code: href="/view/
...to this: href="blog/view/
...and then in the same line changed: >/">
...to this: >">
....and then changed this code: href='/view/".stripslashes
...to this: href='blog/view/".stripslashes

....and it works. So far. Hope this helps out. I'm getting ready to do a redesign on my site as I pursue something a little different, so I can't say how long that blog post or even the blog will remain online if anyone should care to check it out. I'll try to leave it up a few days and add another post or two to see how it works with multiple posts, but I was up all night and am tired, in need of sleep.

http://www.connectionary.com/

Sean

** UPDATE: 08/29/2010 - 3:21 CST **
Ran into a minor problem with the navigation menu outputting the Blog menu item in the navigation menu as I wanted....but with an empty set of UL tags (no list items...which is what it should be doing, because I want them hidden), and this led to non-validation for XHTML strict.

Solution? I changed the Blog page status to hidden and hard-coded the entry into the navigation menu.

Everything seems fine, and I don't appear to get any robots.txt, 404 or other internal errors in any logs...so the redirection all seems to be going smoothly.

** UPDATE: 08/29/2010 - 5:24 CST **
I tried a few changes to see what I could get going. I deleted the Blog page altogether and eliminated all the redirects....

Things will work like this if I set my blog settings path to: blog/

The problem is that I then have that one page with '/' tacked on the end of the URL which is contrary to what I want. This seems to be the root of the problem--the trailing / required in the Blog Settings - Blog Path field.

I wish I were more knowledgeable of PHP and programming in general so I could track the issue better, but that appears to be the major obstacle to having a uniform navigation/URL structure with this blog plugin. The other issue that I have is in trying to enable commenting on blog posts using the Comments plugin. I have tried various solutions, from placing the required code in the template for my site pages (which then requires ensuring comments are disabled for all non-blog pages...and it doesn't work in any case) to placing the code in viewblog.php...again, with no luck.

The question to me is: why is it necessary to append the Blog Path setting with a / at all? There must be a better way to tackle this.....just wish I knew what it was. I suppose for uniformity's sake, I could tweak .htaccess to append a / to every URL that doesn't end one so everything would look uniform. But that still wouldn't solve the issue with getting the needed Comment plugin code into pages (I suppose there could be something I'm obviously missing....just not aware of?).

Last edited by Sean (2010-08-29 23:47)

Setting the charset to UTF-8 should do it:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

That worked for me anyway.

You could also put this to your .htaccess:

AddType text/css;charset=UTF-8 .css
AddType text/html;charset=UTF-8 .html
AddType application/xhtml+xml;charset=UTF-8 .xhtml

Last edited by Fortron (2010-09-23 08:25)