CMS Made Simple Forums

When I first installed CMS Made Simple 1.6.4, the css was loading correctly in Opera, Firefox and IE7.
I've been following Calguy's guide (http://calguy1000.com/Blogs/8/60/cmsms- ... ow-to.html) to set up an e-commerce solution but as I add modules, it seems to break the css. I have removed them and added them but sometimes it works, sometimes it doesn't. There does not appear to be any pattern.
All I can figure out at this stage is that reverting back to the default modules seems to make things work again but that clearly isn't so handy!

Does anyone have any idea what I could do to resolve this?

Thanks,
Catherine

Further to this, there are no errors reported in the Apache error logs.

Are you sure your site have enough resourses for extra heavy modules like this?

I'm not honestly sure. What are the min specs required?

I have:

PHP Effective Memory Limit (memory_limit): 32 MB
Maximum Execution Time (max_execution_time): 30

I wonder if it could be timing out?
I don't have access to php.ini so is there any way of changing these settings?


Thanks for your help.

miss_d_bus wrote: ... reverting back to the default modules seems to make things work again but that clearly isn't so handy!

I'm writing a "heavy" CMSMS module and I've found that certain contributed modules add a layer of complexity to the code base and complicate the simplicity of that core API.  Then you get modules which depend on such additions.  IMO contributed wrappers offering a gamut of convenience methods are not upgrade-proof and should be avoided.

That said, it would be good to include the best of any generic convenience functionality into the core.  Some of mine include: for grouped dropdowns; for presenting labelled checkboxes in one go with whitespace consistent with .
And any Ajax hooks would be a bonus, especially for implementing Apply button magic.

Can't help with your css problem!

Hmmm it seems like I've hit on a bit of a fundamental problem here for people who want something beyond the default cms functionality! I suppose either coding method is going to hit problems and it sounds like its a compromise. Very tricky.

miss_d_bus wrote: ... hit on a bit of a fundamental problem here for people who want something beyond the default cms functionality...

What you've hit on is a still very new major upgrade, against which it takes ages for contributed modules to get tested and fixed.  There should be no fundamental problem for well written modules that hook into the intended interface API and no deeper.  The caveat in the Admin Extensions -> Module Manager screen under "Use at Your Own Risk" is clear.

It's not only the ease of deployment that makes CMSMS so simple but the underlying engineering too.  That's why I picked it.  I think CMSMS is up there with the best for people who want something beyond the default cms functionality.

I'm still using v1.5 until v1.6 updates slow down to a dribble. Perhaps the e-commerce modules are more stable against that.

While I can't provide any helpful insight to your problem I can confirm that the issues do not lie in version 1.6 or the e-commerce modules. I have setup a full fledged e-commerce suite setup on 1.6.4 and I am not having any issues what so ever. I also have a few other smaller e-commerce suite sites setup with no issues. I'd get together with your host to see if they can bump up the execution time limit.

a) follow the standard procedure:  check your php error log

if that doesn't work

b) login to the admin
    go to admin/style.php and check for errors

Thanks guys. Error log was clean and style.php brings back the css code so obviously the file is there etc.

I did not really think it would be the PHP coding as you all do such as blinding job!!
I imagine its probably the server itself given that the site is hosted fairly cheaply and the hosting company has this annoying habit of safe mode and locking the servers down slightly too tightly.
I'll investigate. Thanks!

All this discussion and not once did anyone ask for system info, tsk tsk...

What sort of info would be useful please?

I *think* I've solved the problem:

I created an .htaccess file and put the following information in it to bump up the default settings:

php_value max_execution_time 90
php_value max_input_time 200
php_value memory_limit 64M


Seems okay now *touch wood!*

So right you are reneh - it was a resource problem.

Hello,

Dr. CSS wrote: All this discussion and not once did anyone ask for system info, tsk tsk...

I was out for 40h, I couldn't join the discusson in time

miss_d_bus wrote: So right you are reneh - it was a resource problem.

I guess the System Info would have told so from the beginning.

Pierre M.