CMS Made Simple Forums

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 ...

Russ wrote: 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?

• 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.

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

zgrob wrote: 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

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

tamlyn wrote: 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.

< 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...."