CMS Made Simple Forums

Hey gang,

I attempted to update cms made simple from the highest 1.9 version to 1.10. I initially downloaded the 1.10 version on my mac at work, then FTP'd it on my Windows 7 machine at home (because my ftp at work sucks). Installation looked fine in IE, but broke all to crap in Firefox. Each page displays gibberish at the top, but otherwise seems decently OK. The admin is broken and is missing tabs in Firefox (but not IE).

The Gibberish looks something like:

com.apple.quarantine0000;4ea9af42;Firefox;|org.mozilla.firefoxThis resource fork intentionally left blank ÿÿMac OS X 2°âATTR;šÉÿâ˜*˜*

I read another thread that had a similar problem, but when I re-download the files and upload them on my PC this does not go away.

http://www.tourpikecounty.com

any ideas?

PHP 5.2.6

Check to see if you have any files starting with ._ on your server.. They will be hidden (in Linux), so if there is a 'show hidden files' option, turn it on.

There are a lot of files that are like that that show up when I click show hidden files, what am I supposed to do?

delete them.

There is a crap load of these, I'll delete them all and let you know how it goes. I appreciate your help.

These are files that Macs create.

This seems to have solved the issue. I appreciate you for helping. I have other problems that have popped up after I upgraded, but I'll search the forum before posting about them.

This happens if you've downloaded the distribution to a Mac machine, unzipped it there using Finder, then uploaded to your server.

If you still need to follow the above steps, then do the following instead.

1. Download distribution to a known location on the Mac (example in folder on Desktop)
2. Launch terminal
3. cd to the folder where you have the zip file
4. use gunzip and tar to extract the files
5. Use command-line FTP or FileZilla to upload the extracted files and folders to your server
- Don't use Finder to visit this extracted folder at any time (at least not until you have finished the upload) - this helps to prevent the ._ files from being created. Also saves you the hassle of finding and delete these (although you can use the "find" command-line tool to do it in one go something like this: (test first before you run this command).

S