I've got what's probably a really basic question, so apologies in advance, but I'm just trying to increase my understanding of CMSms. I inherited my work's site, which had already been all set up, so missed out on that side of things, but the editing I'm up to speed with. I've recently set up a second site with CMS which I installed myself (went very smoothly too!).
Am I correct in thinking that the site itself is all stored in the mySQL database, and the CMSms simply 'calls' this information and allows me to manipulate its layout etc? Or am I way off? Think I need to get my head around mySQL a little more really, it's completely new to me!
Really stupid noob question
Re: Really stupid noob question
Yes/NoHannibal wrote: Am I correct in thinking that the site itself is all stored in the mySQL database, and the CMSms simply 'calls' this information and allows me to manipulate its layout etc? Or am I way off? Think I need to get my head around mySQL a little more really, it's completely new to me!
All content info and layout are in DB, binary files only are out (ex: images, docs/pdf, media, ...) in uploads folder
Infact if you move site (ex from local to production) is necessary move DB and uploads folder
Alby
Re: Really stupid noob question
Ah, gotcha, that makes sense (I think). Am considering upgrading the software on the first site at some point, so was trying to get a better understanding of how it all works before hand.alby wrote:Yes/NoHannibal wrote: Am I correct in thinking that the site itself is all stored in the mySQL database, and the CMSms simply 'calls' this information and allows me to manipulate its layout etc? Or am I way off? Think I need to get my head around mySQL a little more really, it's completely new to me!
All content info and layout are in DB, binary files only are out (ex: images, docs/pdf, media, ...) in uploads folder
Infact if you move site (ex from local to production) is necessary move DB and uploads folder
Alby
Re: Really stupid noob question
If you are supposed to work with a CMSMS site, then reading thru the documentation is highly suggested to avoid problems in the future.
Re: Really stupid noob question
I agree. As a relative newcomer to CMSMS myself, I've found the docs and forum searches very helpful in coming up to speed with CMSMS. You might look here to start: http://wiki.cmsmadesimple.org/index.php/User_Handbookreplytomk3 wrote: If you are supposed to work with a CMSMS site, then reading thru the documentation is highly suggested to avoid problems in the future.
Also, as an aside, if you have the time and resources, you might consider setting up a personal "practice" CMSMS site that you can install/destroy/reinstall without impacting anyone else. I put one on my laptop, for example. That way, you should be able to practice installs, backups, restores, upgrades, etc. until you're comfortable with these procedures... all at a safe distance away from your live production sites.

Hope this helps,
Fred P.
Nearly all men can stand adversity, but if you want to test a man's character, give him power.
- Abraham Lincoln
- Abraham Lincoln
Re: Really stupid noob question
Hello,
See the upgrade procedure in the doc : back up, backup and backup (files+db).
Have fun with CMSms
Pierre M.
It is a good idea to keep up to date with versions as we can't support all.Hannibal wrote: ...Am considering upgrading the software...
See the upgrade procedure in the doc : back up, backup and backup (files+db).
Have fun with CMSms
Pierre M.
Re: Really stupid noob question
Don't think local here, use a webhotel/webserver to install your test site on.fredp wrote: ...you might consider setting up a personal "practice" CMSMS site... I put one on my laptop, for example.
Running a test site on a local computer requires you to install and configure software like Apache with a PHP setup and MySQL

Re: Really stupid noob question
Actually if you use windoze a local install is fairly easy using XAMPP, even I can do it
...

Re: Really stupid noob question
A local install is OK but I find tranfering a hassle plus I find that different hosting companies have subtle differences in their server setup so transfering a site from a local production server to a remote live server has caused me a lot of problems.
I used to develop sites on the live server with my own 'sitedown' done through .htaccess but now with v1.6 I use the built in 'Sitedown Settings' under 'Global Settings'.
I've created a generic 'Coming Soon' html page with inline styles and all the images hosted on my own site and I've put it in the 'Sitedown Settings' box. I added my IP address to the exclude field and voilà I'm free to develop the site in situ while curious visitors get a groovy looking sitedown message that advertises my company to them.
Simon66
I used to develop sites on the live server with my own 'sitedown' done through .htaccess but now with v1.6 I use the built in 'Sitedown Settings' under 'Global Settings'.
I've created a generic 'Coming Soon' html page with inline styles and all the images hosted on my own site and I've put it in the 'Sitedown Settings' box. I added my IP address to the exclude field and voilà I'm free to develop the site in situ while curious visitors get a groovy looking sitedown message that advertises my company to them.
Simon66
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.
This must be Thursday. I never could get the hang of Thursdays.
Douglas Adams - The only sane person in the asylum.
This must be Thursday. I never could get the hang of Thursdays.
Douglas Adams - The only sane person in the asylum.