Re: Wolf 0.7.0 RC1 Issues

Minor, but happen to stumble across this in /wolf/app/models/plugin.php

the class method deleteAllSettings has a debug echo statement that should be removed

Thumbs up

Re: Wolf 0.7.0 RC1 Issues

Fixed the debug statement and the non-working close link for the file manager plugin. Also fixed an issue with dynamically updating of plugin list upon enable/disable.

Wolf CMS founder and lead developer
Please always check the Support forums and Wiki before asking. (My Ohloh account.)
Like Wolf CMS? Consider making a financial contribution.

28

Re: Wolf 0.7.0 RC1 Issues

http://192.168.1.1/admin/page/edit/39
Metadata tab
Height of "Description" field should be reduced to 50px. It's equal to 3 lines of text.

Thumbs up

Re: Wolf 0.7.0 RC1 Issues

I've removed the height specification.

Wolf CMS founder and lead developer
Please always check the Support forums and Wiki before asking. (My Ohloh account.)
Like Wolf CMS? Consider making a financial contribution.

30

Re: Wolf 0.7.0 RC1 Issues

Where can we download the latest bug fix of RC of WolfCMS...

I tried the Google version, but I still have the bugs of the admin not redirecting to the right subfolder and can't update the home page....

31

Re: Wolf 0.7.0 RC1 Issues

ZenZen wrote:

I tried the Google version, but ...

That's a strange one, ZenZen -- there is nothing nowhere more up-to-date that the Google Code repository. Perhaps you've got a different "bug" happening?? hmm

32

Re: Wolf 0.7.0 RC1 Issues

David wrote:

That's a strange one, ZenZen -- there is nothing nowhere more up-to-date that the Google Code repository.

Well, that's what I though.... I'll make an export of the google code repo to try again.... hmm

EDIT : I did an checkout and get the "Illegal value for slug field!" error when trying to modify the title of my Home Page

Last edited by ZenZen (2010-12-04 13:34)

Re: Wolf 0.7.0 RC1 Issues

ZenZen wrote:

EDIT : I did an checkout and get the "Illegal value for slug field!" error when trying to modify the title of my Home Page

Whoops. smile Fixed that.

Wolf CMS founder and lead developer
Please always check the Support forums and Wiki before asking. (My Ohloh account.)
Like Wolf CMS? Consider making a financial contribution.

34

Re: Wolf 0.7.0 RC1 Issues

I'm not crazy, thanks...

35

Re: Wolf 0.7.0 RC1 Issues

My update went smoothly. I like the new administrator folder location.
I was confused where you removed the .htaccess parameters for the admin folder, so it appears to have a differently named admin folder, you just leave it the same, wolf/admin/ and you only need to change the constant in the config.php file.

Thumbs up

Re: Wolf 0.7.0 RC1 Issues

JREAM wrote:

...you only need to change the constant in the config.php file.

Correct. The new admin "folder" is actually just a Dispatcher route. So in future you can rename the admin "folder" by simply changing it in the config.php file.

Wolf CMS founder and lead developer
Please always check the Support forums and Wiki before asking. (My Ohloh account.)
Like Wolf CMS? Consider making a financial contribution.

Re: Wolf 0.7.0 RC1 Issues

I'm getting a php warning when using the Page class method hasContent on a page part that exists.  The warning has to do with the trim function being used to test for a string on an object:

I have debug set to true in the config file and get the following warning:

Warning: trim() expects parameter 1 to be string, object given in C:\dev\wolfcms\wolf\app\models\Page.php on line 359

I'm not sure why the test below was added, but logically it will always fail since trim can't operate on an object

Page.php line 359:

$trim = trim($this->part->$part);

Again, not knowing why this was added, a possible fix would be to replace the trim/empty logic with the following:

if (is_object($this->part->$part))
{
        return true;
}

Thumbs up