CMS Made Simple Forums

no, the site down message shouldn't say anything specific. no sense advertising a potentially insecure system.

in addition to my suggestions above (notice in the upgrade script, mention in the online and archive documentation), maybe a notice in the administration area too, like the 'install directory present' notice. those items should be more than adequate to get the message across about the 'sitedown' file.

also, does the upgrade script check to ensure it has write access to the necessary directories and files? like the install script does, in case the upgrade adds a path or files to the system that should be writable by the server.

you can embed permissions into a tarball, and preserve them on extraction, but that would present it's own problems.

patricia: the upgrade script doesn't create the (sitedown) file, it's present in the distribution archive itself.

On the roadmap for 1.0 is a new installer which will address these problems.
the biggest idea, is to have the user install a cms_install.php (or something like that), and when he browses to that, it would then ask him all of those funky questions, and automatically install eveyrthing from a central location (or mirror). 

though this would have it's own difficulties (i.e: the permissions of all of the files would be owned and writable by the httpd daemon process), it would help with the problem of missing files, and permissions issues on install.

calguy1000 wrote: On the roadmap for 1.0 is a new installer which will address these problems.
the biggest idea, is to have the user install a cms_install.php (or something like that), and when he browses to that, it would then ask him all of those funky questions, and automatically install eveyrthing from a central location (or mirror). 

while that's a nifty idea, do not abandon the traditional 'self-contained' distribution archive that does not need to fetch any files from a remote location.

hey all.  been away for a bit, and still not quite "here" yet.. but anyway,

the behaviour described in the original post still exists in beta2. changing the status of a page doesn't refresh that entry's icon right away, you need to refresh or toggle another status to get the previous one to change.

current server i'm working with is an rhel clone running apache 1.3.34, php 4.4.1, and mysql 4.0.25. and for a change, it's not my box. finally broke down and got a normal account somewhere to offload some of the hassles.

client is firefox 1.5.0.1 or ie 6.0sp2 on winxp.

will try out the latest svn when i get a chance to fire up my own linux box again.

i'm still not getting this now.  I thought I fixed it earlier, but I don't remember if it was before or after beta2.

updated last referenced server & install to svn downloaded within the last hour; with no change. sorry wishy.

Tried 3 different machines, 1 being a windows one.  Don't see it.  I have no idea...

wishy wrote: Tried 3 different machines, 1 being a windows one.  Don't see it.  I have no idea...

will pm you login details of an install that's doing it.


edit: wishy was able to find and fix the problem in the code.