1.0 Beta6 Released!

[jce76350]

Hi,

In page "news"
This page is not Valid XHTML 1.0 Transitional! from  http://validator.w3.org/check

I think the problem is  "&cntnt01article" " &cntnt01origid"  "&cntnt01returnid"
--> must be &cntnt01article ...

I fix the problem (Is the best solution ? )

In lib\classes\class.module.inc.php (line 2571): $id = 'cntnt01';
   remplace by                                                        $id = 'amp;cntnt01';

And an other "not Valid XHTML 1.0" in Content » News/Detail Template
must be

[zgrob]

Hi,

Just installed version1.0 beta4 to have a look at the new features and stuff.

After playing around a bit I found a problem with section headers not working properly in menu's. They just appear as black text at the wrong position and it goes completely wrong when you add a child page to the section header.

For the rest it looks great, keep up the good work!

Regards,
Rob

[Ted]

Beta5 is up.  Hopefully this is the last one and we'll be releasing 1.0 sometime next week.  Please, any last minute testing you can do is always appreciated.

Thanks!

[3dcandy]

Still can't install beta5, try's to connect to a https:// address on my homeserver running windows server 2003.
That will be IIS 6, PHP 5.1.4.0

Any ideas guys, wanna move over to 1.0 but this is stopping me

[3dcandy]

If I navigate to the install dir, and run the install.php file it works...maybe a typo or summat when it redirects from the base directory??

[Dr.CSS]

To install...

www.  your site. com/install/install.php  (stretched url so it won't turn into a link)

for upgrade...

/install/upgrade.php

[Russ]

OK Beta 5. Upgrade to my test 0.13 appeared to go OK. Whoopeee...

1. I still cannot install the included 'Search'. It fails somewhere during the installation - very annoying as this is one thing I want to testt. One table is created, but no admin and the module does not show as installed. If you need more help in debugging I'm available most of today. Should this not be installed by default?
2.The File manager Module (not the default one) installs OK but when you click on it the tabs appear but nothing below them. I've psoted on the forum topic for this module.
3. Module Manager is very slow? Losts of module don't seem ready to install - no XML? Also some modules appear multople times with older versions?
4. Is there going to be an expansion of 'anchor' to replace cms_self link and the previous and next bits?
5. FCKEditor still does not seem to accept toolbar layout pasted into it's admin module?
6. FCKEditor still seems fickle with CSS classes in display when pasted into it's admin module or in the drop down in the editor? Yes I know you can do it but it's not very easy.
7. The comments module still seems to be built with a table based form in template? Widths for form are way too wide, but this could be down to my CSS? Actually these are set in form creation which is one of those smarty creations I don't really understand. What is wrong with using normal XHTML form syntax? There must be a good reason?

Other Comments:
+ Still no multi-user editing support. Two people can edit the same page without warnings. Surely this must be in version 1.0? I can't see how it cannot be. Quite sad.
+. Also sad to see Elijah's cool news url's patch not implimented. Same would apply to it's use in Album etc.
+ Should we not use the The File manager Module (not the default one), as the default one? When it was working it seemed better?
+ Why not dump the ImageManger tag thingy and use Album as the default gallery?
+. Is there a spell checker for any of the editors - this would be very good.

Now please don't take these comments the wrong way, they are meant to be constructive. I've been in this business a long time and as far as I can see, this should not be the last beta? Still too many things to be done? My only regret is I do not have access to SVN on a regular basis or I would help out more.

I'll let you know if I have more.

Russ

[3dcandy]

I get the install idea, but older versions would just install by themselves when you went to the base directory the 1st time.
Chat module doesn't work, I have multiple problems with module manager (works one in about 10 times for me)
This version appears slower than older versions too.

I need to spend more time on it, but seems to be getting a little bloated as we move towards a 1.0 release

[calguy1000]

OK Beta 5. Upgrade to my test 0.13 appeared to go OK. Whoopeee...

1. I still cannot install the included 'Search'. It fails somewhere during the installation - very annoying as this is one thing I want to testt. One table is created, but no admin and the module does not show as installed. If you need more help in debugging I'm available most of today. Should this not be installed by default?

We're looking into this one, is there any information in your error logs ?

2.The File manager Module (not the default one) installs OK but when you click on it the tabs appear but nothing below them. I've psoted on the forum topic for this module.

This isn't a core issue, so not really related to the Beta.  We may include this file manager into the core at a later date, but not for 1.0.

3. Module Manager is very slow? Losts of module don't seem ready to install - no XML? Also some modules appear multople times with older versions?

Okay, now for the meat:

• Modulemanager and it's server side ModuleRepository are having difficulty with large XML files (Captcha, Comments, and FCKEditor).  Things seem to time-out or run out of memory or something on the current server.  It works fine when I have a local repository, and my PHP memory limit set to 16Mb.  I don't have access to the httpd error logs on the cms server to see what's happening for sure.
• There is an issue with naming of the XML files which I'll get to hopefully in the next day or two, which handles one of the captcha issues.
• And yes, the multiple versionf of a module are there intentionally.  Hopefully this week we'll get to a script that will limit the number of versions available, and post 1.0 I'll look at changing the appearance somewhat so that it makes a bit more sense, but the multipe versions thing will probably stay so that if necessary people can revert to older versions of a module.

I hope this clears some stuff up for you

4. Is there going to be an expansion of 'anchor' to replace cms_self link and the previous and next bits?

Alot of work has been done with cms_selflink, and from what I'm told the 'anchor' plugin is almost redundant now.  either way, we'll probably leave this issue unless it becomes urgent

5. FCKEditor still does not seem to accept toolbar layout pasted into it's admin module?
6. FCKEditor still seems fickle with CSS classes in display when pasted into it's admin module or in the drop down in the editor? Yes I know you can do it but it's not very easy.

These are low priority issues, so we probably won't fix em in the beta...... we're only trying to resolve absolutely critical issues at this time.

7. The comments module still seems to be built with a table based form in template? Widths for form are way too wide, but this could be down to my CSS? Actually these are set in form creation which is one of those smarty creations I don't really understand. What is wrong with using normal XHTML form syntax? There must be a good reason?

The comments module is not in the core, so it's not related to the beta.  I'd get in touch with the comments module owner.

Other Comments:
+ Still no multi-user editing support. Two people can edit the same page without warnings. Surely this must be in version 1.0? I can't see how it cannot be. Quite sad.

Nope.... Sorry this is not as small as an issue as you would think, and it's been put off till post 1.0

+. Also sad to see Elijah's cool news url's patch not implimented. Same would apply to it's use in Album etc.
+ Should we not use the The File manager Module (not the default one), as the default one? When it was working it seemed better?
+ Why not dump the ImageManger tag thingy and use Album as the default gallery?
+. Is there a spell checker for any of the editors - this would be very good.

We essentially cut off features (I think one or two rather important ones got in) after the first beta came out, and have just been addressing performance issues and serious bugs.  The last of the "cool" features went in (I think) just prior to Beta1.  Our aim is to make 1.0 a very stable release, and to have it last a while, so we are keeping the feature creep in the beta series under a tight leash.  We'll probably let him free again after the release is out.

Now please don't take these comments the wrong way, they are meant to be constructive. I've been in this business a long time and as far as I can see, this should not be the last beta? Still too many things to be done? My only regret is I do not have access to SVN on a regular basis or I would help out more.

I'll let you know if I have more.

Russ

We're not offended, keep up the good work.... and please, give us as much information as possible about your Search install issue....

[tamlyn]

Woooohoooo! Go 1.0! Tried fresh install and upgrade from 0.13 and both went v. smoothly. Just a couple of comments:

The CMSMailer module defaults to 'smtp' which usually requires some configuration. I think it would be better to default to sendmail on *nix hosts as that nearly always works out of the box.

I also don't like the inclusion of a favicon file. It's not useful to anyone and it's a pain to those uf us used to upgrading by simply overwriting everything since that will overwrite our own favicons. I know a lot of other cmses do it but that's no excuse.

But otherwise super-well-done It's looking fantastic!

[larskong]

Hi CMSMS forum,

Thank you for a great site management system. I love to work with it.

I have a problem in v.1.0-beta5 that I saw (to a lesser degree) in beta4 also.

In the standard installation, just playing around in the menus, I keep getting
the error message "Apache HTTP Server found an error and was closed"
(translated from danish into english).

It happens both in IE6.0, Firefox1.5.0.5, and Opera9.1.

What could be the cause of this?
Best regards / Lars

CMSMS v. 1.0 Beta5
Opera v.9.1
IE v. 6.0
Firefox v.1.5.0.5
Windows XP platform SP2
XAMPP for Windows Version 1.4.16 (PHP Version 5.0.5, Apache 2.0.54)

[gelöscht durch Administrator]

[tamlyn]

Hi lars, I'd say it was very unlikely that cmsms is causing apache to crash as you reported. More likely it is due to a misconfiguration of Apache or xampp or some library. Have you tried running other php/mysql software on your setup? Also check your apache error logs for more info on why it crashed and maybe ask in the xampp forums too.

[larskong]

Hi tamlyn,

I should have thought of that. I will ask the XAMPP forum about it and look in the logfiles.
It startet when I installed CMSMS v.1.0-beta4 on the same XAMPP installation that I have
been running earlier versions on...strange..

Thanks / Lars 

[larskong]

Hi,

Just installed version1.0 beta4 to have a look at the new features and stuff.

After playing around a bit I found a problem with section headers not working properly in menu's. They just appear as black text at the wrong position and it goes completely wrong when you add a child page to the section header.

For the rest it looks great, keep up the good work!

Regards,
Rob

Great! I think CMSMS is the most promising site management system I have tried out yet, and I look forward
very much to the v.1.0 release.

I have noticed the same problem with sectionsheaders, and also there is some kind of mismatch in the standard
installation with regards to horizontal CSSmenu. In the template "CSSMenu top + 2 columns" under navigation
it says:

Code: Select all

<!-- Start Navigation -->
      <div id="menu_vert">
         <h2 class="accessibility">Navigation</h2>
         {menu template='cssmenu.tpl'}
      <hr class="accessibility" />
      </div>
      <!-- End Navigation -->

Should it perhaps be and then the stylesheet "Navigation: Simple - Horizontal"
maybe should be assigned this template also (or instead)?

Summing up:
1) There seem to be a problem with handling of sectionheader (maybe from both the template cssmenu.tpl and styling).
2) There seem to be a mismatch concerning templates and stylesheets with regards to horizontal menu.

Kind regards / Lars

[Elijah Lofgren]

I also don't like the inclusion of a favicon file. It's not useful to anyone and it's a pain to those uf us used to upgrading by simply overwriting everything since that will overwrite our own favicons. I know a lot of other cmses do it but that's no excuse.

I'm to blame for adding that in. You're right it should probably be removed. I'll try asking in the irc channel and see if calguy100 or Ted is around and gives the OK for it to be removed.

Edit:
I asked calguy and this is what he said:

Code: Select all

< calguy1001> heh, I don't mind.... maybe rename it to something though, instead of deleting it.  favicon_cms.ico or something.
 * calguy1001 remembers when the topics were "please add a favicon...."

So I've renamed it: http://viewsvn.cmsmadesimple.org/viewsv ... 4&view=rev