Do you have it online somewhere so we can take a look?

@Apache - I would highly recommend to switch to UTF-8, this is most likely the cause of your problem.

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

In website development, its best to make sure all parts of your setup are using UTF-8. From DB to HTTP server to the actual html page. If the problem still exists after you've switched to utf-8, we can look further into the problem.

Actually, that line is already in Wolf's .htaccess file. It could be that his server admin simply doesn't allow him to specify it. (in that case, complain to your server admin and have him change to UTF-8)

You still need to set the HTTP headers too by the way!

Yay, I finally joined the wolfcms forum. I'm sorry that I'm joining on a bad note though.

I've just done a fresh install of WolfCMS so I'm sorry to begin with if any of the following is just something I haven't done that I'm supposed to have with a fresh install. I have been playing with WolfCMS for about a month now and am loving it. I was dying for a simple CMS for simple sites and didn't want to use things like joomla for the simple projects.

I'm not sure if I'm doing something wrong, but I'm having trouble with the plugin. When I set the slug to nothing in the mbBlog settings, nothing changes on the home page.. it's still the home page.

If I set it to, well I used "blog", going to domain.com/blog pulls up the list of blog posts. Great until you click one, it produces a 404 error.

A suggestion, I like the intro option, that's incredibly useful for my end goal. But I'd like it if it worked like your other plugins where you place code where you want the blog list to appear, and then have it create pages (without it being pages because that was the goal.. but like pages you don't see in the main "pages" tab..). Sorry for not explaining very well.

Anyway, keep up the good work. I hope you don't mind, but I was using one of your plugins to learn how to build my own plugins.

Does someone have a working version of "mbBlog - Blog system" for Wolf 0.7.3 ?

jackie,

I installed it again and it works now! Just had to adapt the pagination to work properly.

With debug on it shows some "Strict Standards: Non-static method" stuff but it's just on a test install so not a real problem.

Does your HTTP server's error log show anything?

Just installed WolfCMS and mbblog and have noticed the same problem. Makes WolfCMS as a whole pretty much useless for me, as I need a blogging platform and that seems to be the only one (I can't figure out a way to make WolfCMS on it's own act as a usable blog for many users)

Anyway, I investigated a little bit, and I found it seems that when the page is loaded. Here's what I have so far:

From main.php it runs:

    if (Dispatcher::hasRoute($uri)) {
        Observer::notify('dispatch_route_found', $uri);
        Dispatcher::dispatch($uri);
        exit;
    }

with $uri equal to '/' ...which seems correct from my understanding.

From there dispatcher heads into:

        // Is there a literal match? If so we're done
        if (isset(self::$routes[$requested_url])) {
            self::$params = self::splitUrl(self::$routes[$requested_url]);
            return self::executeAction(self::getController(), self::getAction(), self::getParams());
        }

which of course goes to executeAction, which gets to:

        $controller->execute($action, $params);

where $action is 'mbblog' and params is a single element array, element 0 being 'index'

This then runs mbblog/MbblogController.php, which eventually runs it's 'index()' function, getting to this section of code at the end:

        if(defined("CMS_BACKEND"))
        {
               $this->display('mbblog/views/admin/index', $this->mbvars);
        } else
        {               
            $this->executeFrontendLayout();
            exit;
        }

where it takes the second path (else), runs executeFrontendLayout, which gets to this if block:

        if ($layout = $stmt->fetchObject()) {
        // if content-type not set, we set html as default
            if ($layout->content_type == '')
                $layout->content_type = 'text/html';

            // set content-type and charset of the page
            header('Content-Type: '.$layout->content_type.'; charset=UTF-8');

            // Provides compatibility with the Page class.
            // TODO - cleaner way of doing multiple inheritance?
            $this->url = CURRENT_URI;

            // execute the layout code
            eval('?>'.$layout->content);
        }

which it skips because $layout is undefined...then it drops out of the function and exits.

I'm honestly not sure what this plugin offers either; I'm just hoping when I get it installed, it'll be what I need. But basically, I'm trying to set up a blog that will have a lot of different writers, and I want two things: first, users being able to register their own accounts, which doesn't seem to be possible on WolfCMS; and second is an easier way for users to login and make a post. It appears under the default WolfCMS that you can't give someone rights to JUST make posts and not have rights to edit the entire site, and there's no login link, no intuitive post function...basically I feel like I'd probably have to show every person who's going to be using it how to actually make a post...which isn't going to be feasable.

[edit]:
And now that I've got it working...this plugin doesn't help at all...

Last edited by urza9814 (2012-01-12 00:29)

Please try if the Registered Users plugin suits your needs.

Please try the Roles Manager plugin for this kind of right management.

I'm pretty sure you also want to tryout the Account plugin.

Hmm. Thanks for the tips. Hibari's a no-go (needs a higher PHP version than our crap University servers have installed, and I'm trying to avoid paying for hosting)...the accounts plugin doesn't appear to allow users to create their own accounts...but I'll look around some more and see what I can come up with. Not entirely opposed to modifying plugins if it's not too much effort, but we're trying to have something up by next week.