0.9rc1 Released!

[Ted]

TinyMCE is such a pain sometimes (as are all javascript WYSIWYGs). I'll see if I can figure out what the problem is over the weekend. Thanks.

[Ted]

rc4 is up. I didn't fix any WYSIWYG related problems, though. I have a hard time getting them to duplicate...

[100rk]

Hi Wishy,
can You please move file 'helparea.js' from 'admin' directory to other ('lib')? In case I don't want link to admin page at public pages and want to use plugin ExpandCollapse, information about 'where is my admin directory' is in HTML code - as source file of JavaScript library.
Question is not 'are we paranoid?', but 'are we paranoid enough?'

[Ted]

It's a valid request. I'll do it this afternoon.

[100rk]

Thanks
I also vote for automatic assignment 'root_path' every time CMSMS is called - but not from $_SERVER['DOCUMENT_ROOT'] but by the dirname(__FILE__) construction - DOCUMENT_ROOT is not offered correctly on most systems, like OpenBSD with VIRTUAL_DOCUMENT_ROOT (not change with apache virtual_directory or virtual_host things) - for example see ::REMOVED:: - path /var/www/htdocs is NOT real path to webroot directory. And one more thing: do You think about automatic chmod() directories during install procedure?

[Ted]

Is the chmod() thing even possible? Most people don't have their files owned by the webserver when they're uploaded, so the server couldn't chmod them anyway... I guess it could go there and it not, then fail silently...

As for automatic doc_root, it's a great idea! I don't want to do it for 0.9, though. It's too much of a major change to do this close to a release, and I want to be able to explore the ramifications.

I also REALLY want to explore other ways of doing URLs. Like http://domain.tld/index.php/page1 or similar, but I'm holding off on that also, because of problems with how IIS does it. It's going to take some serious testing, and it's too close...

I think 0.9 will be out Monday night, assuming no problems. I just need help tracking down these TinyMCE bugs and working through them.

[100rk]

OK, I understand Your priorities. I have to study new API now and then I will think about 2 features from roadmap - automated module download/install and multilanguage support. It can be implemented as modules - I don't think all CMSMS users will use it, so - this possibility will be nice, but no necessary in basic distribution. One question: which way for module download from 'module repository' You would like? FTP or HTTP?

[100rk]

Hi Wishy, at the end of file /admin/menu.php (where is modules menu created) you can move condition 'if ($cmsmodules[$key]['object']->HasAdmin())' between first 'if' conditions - this second 'if' is not neccessary.

[Ted]

uptoeleven started working on stuff for the automated downloads/installs. Problem is that there are several issues that come along with it...

1. I want it to be somewhat secure. Meaning that downloads should be signed, or at least have some kind of check against a central site with an md5 sum or something. I'd love to have signed archives, but that might be a little too much.

2. I want it to be implemented in pure PHP, because I don't want to have to have users install anything else.

He's been a little under the weather, so I'm not sure how progress goes on it.

[100rk]

Hi Wishy,

can You please do one little change in HTMLArea before 0.9 is released?
Please change lines 23 and 33 in file '/modules/HTMLArea/htmlarea/plugins/ImageManager/config.inc.php'

from

Code: Select all

$IMConfig['base_dir'] = $config["uploads_path"].'/images';
$IMConfig['base_url'] = $config["uploads_url"].'/images/';

to

Code: Select all

$IMConfig['base_dir'] = $config["image_uploads_path"];
$IMConfig['base_url'] = $config["image_uploads_url"];

Thank You for Your time.

[Ted]

done.

[100rk]

Thanks

And another thing: creating textarea (module API - page.functions) with fixed number of cols&rows is uncomfortable limitation - try how it works for example in new (but very nice) module Calendar - width of textarea in HTMLArea is smaller then width of free space in admin page or then HTMLArea toolbox.

[Ted]

Ok, I'll put that on my 0.9.1 list. Someone else mentioned it as well, but I'm trying not to break anything if I can help it at this point.

[100rk]

Hi Wishy, I am glad to 0.9 is not here yet... I found similar bug as in 0.8.2 - bad resolving dependencies in moment creating 'Install' link in plugin management (0.9rc4)

So I changed lines 395-414 in plugins.php
from

Code: Select all

$brokendeps = 0;

if (count($modinstance->GetDependencies()) > 0) #Check for any deps
{
    #Now check to see if we can satisfy any deps
    foreach ($modinstance->GetDependencies() as $onedepkey=>$onedepvalue)
    {
        if (isset($gCms->modules[$onedepkey]) && 
            $gCms->modules[$onedepkey]['installed'] == true &&
            $gCms->modules[$onedepkey]['active'] == true &&
            version_compare($modinstance->GetVersion(), $onedepvalue) > -1)
        {
            $brokendeps++;
        }
        elseif (!isset($gCms->modules[$onedepkey]))
        {
            $brokendeps++;
        }
    }
}

to

Code: Select all

$brokendeps = 0;

$dependencies = $modinstance->GetDependencies();

if (count($dependencies) > 0) #Check for any deps
{
    #Now check to see if we can satisfy any deps
    foreach ($dependencies as $onedepkey=>$onedepvalue)
    {
        if (!isset($gCms->modules[$onedepkey]) ||
            $gCms->modules[$onedepkey]['installed'] != true ||
            $gCms->modules[$onedepkey]['active'] != true ||
            version_compare($gCms->modules[$onedepkey]['object']->GetVersion(), $onedepvalue) < 0)
        {
            $brokendeps++;
        }
    }
}

Update it in SVN, please.

New API is excellent - and it promises a lot of new functions (not 'linked' to its future actions in this time) Great work!

Hi, 100rk.

[Ted]

I'm taking your word on that fix. It's in SVN.