404 page not working?

[Chris F]

My 404 page doesn't come up properly and results in an error. Any inactive URL results in a ERROR at line 2493 of file /home/j76qmlw2353o/public_html/lib/misc.functions.php:

ERROR MESSAGE:

Attempt to set headers, but headers were already sent at: /home/j76qmlw2353o/public_html/lib/classes/contenttypes/Content.inc.php::1328
TRACK TRACE:

#0 /home/j76qmlw2353o/public_html/index.php(183): setup_session(false)
#1 {main}

If I hit refresh on the browser, the 404 page will appear, just not for the initial load. Any idea what is wrong?


triangleswimschool.com

CMS Made Simple Install Information
CMSMS Version 2.2.14

Installed Modules
AdminSearch 1.0.5
CGBetterForms 1.10.4
CGExtensions 1.65.2
CGSimpleSmarty 2.2.1
CMSContentManager 1.1.9
Captcha 1.0
CmsJobManager 0.1.3
DesignManager 1.1.8
FileManager 1.6.11
FilePicker 1.0.4.1
Gallery 2.4.2
MenuManager 1.50.3
MicroTiny 2.2.4
ModuleManager 2.1.7
Navigator 1.0.9
News 2.51.10
Search 1.51.8

[DIGI3]

What PHP version, and if you try changing it (e.g. 7.2 to 7.3) does it go away?

Other things to check would be temporarily removing htaccess, deleting the error page and starting over, and using a blank page template for it.

These are all just guesses, I wasn't able to recreate the issue.

[Chris F]

Thanks DIGI3. If you go to, say "https://www.triangleswimschool.com/blabla" it gives you the 404 page properly? It gives the CMS error page for me.

[DIGI3]

Sorry, I meant I wasn't able to recreate it on a clean install. I do see the problem on your server.

[Chris F]

This was a migration from another server.

[velden]

Did you migrate using FTP by any chance?

It sounds like a file that has content (can also be a space, line-break) after the closing php> tag.
It can be an adventure to find the one (IF it's indeed the cause). Though you may start to check the config.php file as that's one you have been editing for sure.

[Chris F]

Yes FTP. So corrupt file?

I've tried moving the files over again, in the affected files listed in the error. Nothing seems to be working.

[velden]

Corrupt files is one possible cause indeed.
For FTP transfers it's important to set the transfer mode to binary.

IF the problem is caused by one or more corrupt files - which isn't sure - then those files can be corrupted during download from the old environment and/or during upload to the new environment.

If you still have access to the old environment, it could help to generate a checksum file there and use it to verify the new environment.
CMSMS has built-in functionality for that. (Site admin > System Verification)

Please note that I'm just guessing based on what you post. There can be other reasons so don't go blind on just this option.

[Chris F]

I do still have it on the prior server. I downloaded a checksum file and uploaded to the site on the new server. Says 3190 Files failed. I'll try downloading it again and reuploading all the files to the new server.

[velden]

Well you could try to download a few of the failed files again from the old server in binary transfer mode and upload those the new server (in binary mode again of course).
Then check if the number of failed files decreases.

If that works, you know what to do.

[velden]

Make sure you have a proper backup first (files and database)

If it's a 2.x install, you may consider to do a Freshen (repair) installation:

Freshening the installation involves replacing all core files and recreating the configuration. You will be asked basic configuration information, however the database will not be touched.

Just upload the original cmsms-2.x.xx-install.php file to the webroot and 'call' it from the browser. The Freshen (repair) installation option should appear on step 2.
You will need the database password in step 4.
Note this will overwrite core CMSMS files but 3rd party modules will not be touched.

Afterwards, do the verification again.

[Chris F]

The freshen did it! Thank you so much!