Help with getting the CMS CORE package up and running. This does not include 3rd party modules, PHP scripts, anything downloaded via module manager or from any external source.
I'm getting this error when I log in and use the admin panel after upgrading from 1.3.1 to 1.4.1.
I've tried to set the theme to Default and it goes back to the old admin theme before NCleanGrey and tried to set it back, etc.. and still get the above error no matter what it is set at.
Warning: Cannot modify header information - headers already sent by (output started at /mypathhere/lib/html_entity_decode_php4.php:622) in /mypathhere/admin/lang.php on line 51
Warning: Cannot modify header information - headers already sent by (output started at /mypathhere/lib/html_entity_decode_php4.php:622) in /mypathhere/lib/classes/class.admintheme.inc.php on line 161
Warning: Cannot modify header information - headers already sent by (output started at /mypathhere/lib/html_entity_decode_php4.php:622) in /mypathhere/lib/classes/class.admintheme.inc.php on line 164
Warning: Cannot modify header information - headers already sent by (output started at /mypathhere/lib/html_entity_decode_php4.php:622) in /mypathhere/lib/classes/class.admintheme.inc.php on line 167
Warning: Cannot modify header information - headers already sent by (output started at /mypathhere/lib/html_entity_decode_php4.php:622) in /mypathhere/lib/classes/class.admintheme.inc.php on line 168
Warning: Cannot modify header information - headers already sent by (output started at /mypathhere/lib/html_entity_decode_php4.php:622) in /mypathhere/lib/classes/class.admintheme.inc.php on line 171
Warning: Cannot modify header information - headers already sent by (output started at /mypathhere/lib/html_entity_decode_php4.php:622) in /mypathhere/lib/classes/class.admintheme.inc.php on line 176
Last edited by kurtf on Tue Aug 12, 2008 5:48 pm, edited 1 time in total.
I did my first few installs via FTP but it's s...l...o...w...
If you have control panel access then CPanel, DirectAdmin, and others have a file manager that allows you to extract the install file.
Its far quicker and less error prone to FTP the install.tar.gz file to your site and then use your control panel file manager to extract the contents. You could upload the install using the file manager as well if you wanted to. Don't forget to delete the install file when you're done.
Nick
Last edited by Anonymous on Tue Aug 12, 2008 8:57 pm, edited 1 time in total.
kurtf wrote:
I did and the checksums do match.
00100b876f7274bceb7921a6ca5a148d
Is what I get on my d/l.
I mean't that you should verify the files once they've been FTP'd to your webserver, using the 'System Verification' link on the 'Site Admin' menu. That involves uses a checksum file (e.g. cmsmadesimple-1.4.1-base-checksum.dat) with approx 1600 checksums. That will tell you if you've got any missing or corrupt files after the upload. I think what you did was verify the install file that you downloaded from the Forge.
I know you're sorted, but I thought this distinction might be useful to others.
Nick
Last edited by Anonymous on Tue Aug 12, 2008 8:58 pm, edited 1 time in total.
Pierre M. wrote:
Thankx Nick. Please consider copy-paste to the wiki
I've updated the "Quick Install via FTP" instructions.
I've added a suggestion to upload the install.tar.gz file and use the control panel's file manager to extract it's contents on the server. I've also added a new last step to suggest verifying the upload/install using the appropriate checksum.
