CMS Setup Help Required

[Samval]

Hello All,

I am first time user of CMS Made Simple.

My environment setup is as follows:
O/s: Windows 2003 SBS
PHP: Installed version 5.2.5
MYSQL : Installed version 5.0

I have performed following steps so far from reading installation documentation.
1. Downloaded version 1.2 of CMS
2. Created a Database in MYSQL called CMS
3. Ensured PHP is configured to work with IIS
4. Copied unziped content of CMS installtion in default website directory
5. Ensured IIS user has full control over all files

Now the problem is:
When I try to browse the website using IIS MMC console using the following link http://localhost/CMS/install/
I get following error message:
Website declined to show this page
Most likely causes:
This website requires you to log in.

Any help would be much appreciated.

Many Thanks in advance
Sam

[alby]

4. Copied unziped content of CMS installtion in default website directory
...........
When I try to browse the website using IIS MMC console using the following link http://localhost/CMS/install/

If you unzip in default (root) folder of IIS, your link is http://localhost/

Alby

[Samval]

Hi Alby,

Apologies for confusion.

Directory structure on the server is as follows:

C:\Inetpub\wwwroot\CMS

and hence I was using the link http://localhost/CMS and have also tried http://localhost/CMS/install/ but with no success keep getting the same error

  The website declined to show this webpage
HTTP 403 
  Most likely causes:
This website requires you to log in.

  What you can try:
    Go back to the previous page.

    More information

This error (HTTP 403 Forbidden) means that this program was able to connect to the website, but it does not have permission to view the webpage.

Awaiting your response

Regards,

[alby]

  The website declined to show this webpage
HTTP 403 
  Most likely causes:
This website requires you to log in.

I don't know IIS.

You must verify that server:
- respond for index.php (IMHO: default for IIS is home.htm, default.htm and maybe index.htm but not index.php)
- there is a .htaccess in root directory (I don't know if in IIS is same of Apache)

Alby

[Samval]

Thanks Alby for your reply.

However I have tried browsing to Index.php but with nosuccess.

Who would be the best person to provide help with setting it up with IIS? and how can I get in touch with them?

Regards,

[kermit]

can you drop a regular HTML file into a) the webroot, b) webroot\CMS, c) webroot\someotherfolder and browse to those?

if so, can you also do the same with this (named phpinfo.php):

Code: Select all

<?php

phpinfo();

?> 

if you cannot do all the above (2 files, 3 locations), then the problem definitely lies with the server configuration, and not cmsms... i would then start with permissions, as that's the error message you originally received.

[Samval]

Thanks for the reply.

I can browse for the file in all 3 locations.

I have also given all users on the server Full Control of all files and folders in CMS directory.

What else could I check for?

Regards,

[alby]

I have also given all users on the server Full Control of all files and folders in CMS directory.

What else could I check for?

View this if help you

Alby

[Samval]

Many Thanks Alby,

After giving CMS folder all possible permission in windows and creating a config.php file from the sample posted, when I browse the Index.php page I get the following message "Site down for maintenance."

I guess we have taken a step forward. Can you please throw some light on what the above message mean?

Regards,

[alby]

Many Thanks Alby,

After giving CMS folder all possible permission in windows and creating a config.php file from the sample posted, when I browse the Index.php page I get the following message "Site down for maintenance."

I guess we have taken a step forward. Can you please throw some light on what the above message mean?

It's little warning only for clean cache (NECESSARY for upgrade but less important for install because deleted automatically)
Go to admin area,  Global settings and Clear cache 

Alby

[ericob]

Is this documented anywhere?

That is, can you get to /admin if that SITEDOWN file exists?  (How would you know to try?)

Personally, I just dug around and finally found the SITEDOWN file and simply deleted it.  My site took a while to appear but it did eventually.

We're back to the problem of very, very, very terse documentation in areas where GREAT DETAIL is required.  I did not see any documentation that after an upgrade my site would be in a SITEDOWN state and that I should (should I?  Should I need to?)  find the "Clear Cache" button and press it.

If this is necessary/recommended, why doesn't it happen automatically, as part of the update?  If not that, why not document it somewhere?

If it is documented, why not make that information as easy to find as the diff file is??

[kermit]

Is this documented anywhere?

That is, can you get to /admin if that SITEDOWN file exists?  (How would you know to try?)

Personally, I just dug around and finally found the SITEDOWN file and simply deleted it.  My site took a while to appear but it did eventually.

We're back to the problem of very, very, very terse documentation in areas where GREAT DETAIL is required.  I did not see any documentation that after an upgrade my site would be in a SITEDOWN state and that I should (should I?  Should I need to?)  find the "Clear Cache" button and press it.

SITEDOWN is a semaphore file present in the distribution archives. it is normally deleted upon successful completion of the install or upgrade script.. this prevents a site from trying to run on new new code without receiving a possible required database schema upgrade.  if you manually copy the cmsms files, construct or restore your own config.php and database, and do not use an install or upgrade script, then you must also remove the SITEDOWN file yourself.  -- at least that's my own take on it..

the SITEDOWN file is also used if you "turn off" the site in global settings.


as far as clearing the CMSMS cache goes on an upgrade.. you should do that BEFORE you even start the upgrade.

[Dr.CSS]

If you are using Windows you should be using XAMPP...