CMS Made Simple Forums

Hi,

I notice that CSS Menu is not in the distribution any more.  I am having some problems getting CSS Menu to work properly with Beta 2 (especially on MS Internet Explorer) though there are some more things I can try, like making another test site, comparing files and moving things across slowly and carefully...

Is CSS Menu still supported, or should we migrate to Menu Manager?

Can Menu Manager produce the same visual effect (i.e. vertical menu with dropdowns) as CSS Menu?

Thanks!!

Ah, now I understand!

I'll make a test site from scratch with cmsmadesimple.org/cms-daily.tar.gz, to get familiar with that new template.  Then I'll be ready for the new release.

Thanks for all the help Patricia

It´s really easy, just view the help in the modul section. You can even copy the tpl to the database with the admin interface and edit it there to fit your needs.

@martin42: Since a lot of people are going to have quesetions on this, can you share your results of what you did here specifically from a user's view?  We need a couple of pioneers to blaze through and share their experiences. 

Thanks!

@wishy:
Just as an idea for 0.12 how about letting smarty change the three old smarty-tags to an info like "Tag no longer supported. Please see module section help of menu manager for further informations."?

@wishy: Yep, good idea...

For max. benefit ahead of the 0.12 release, I guess I should grab the very latest out of the SVN trunk, so I'm building the SVN client right now

While we're here, I noticed you've put a cool tweak into stylesheet.php for ETag support, for Apache servers.  Can we stuff the same code into index.php, so that it works for content pages too?  This will only work if the HTML debug comment is disabled (otherwise the MD5 hash will change because the number of queries or time taken will differ slightly).

(UPDATED) I did think we could make this work for non-Apache servers, but it turns out that the HTTP header we need (If-None-Match) is not copied into the environment by the CGI standard.  So we don't have enough info to do this in the general case.  Sorry for the confusion.

Cheers!

- Martin.

I suppose we could, though the content pages are probably going to change a lot more often than the stylesheet will.  I guess any reduction of bandwidth is better than none...

martin42 wrote: Can we stuff the same code into index.php, so that it works for content pages too?  This will only work if the HTML debug comment is disabled (otherwise the MD5 hash will change because the number of queries or time taken will differ slightly).

I did think we could make this work for non-Apache servers, but it turns out that the HTTP header we need (If-None-Match) is not copied into the environment by the CGI standard.  So we don't have enough info to do this in the general case. 

Actually, I have made more tests, and at least for the Mathopd webserver, in fact all the HTTP headers *are* present in the environment.  You can see this by creating 'test.php' and running it from your CMSMS root directory:
If you run this TWICE (so that the browser has already seen the ETAG when it sends the second request), you should see the following output in the environment section of the phpinfo output: So (at least with this web server) it should be possible to do content caching, even when you're not using PHP as an Apache module.  It would be good to have this in place for 0.12 if possible.