Blank.html ? - help
Blank.html ? - help
hi all,
I (well, my boss did) purchased the license a couple of hours ago. I already changed the menu. It works beautifully locally. However I uploaded all the necessary files to the server (via CuteFTP). The new menu would not work live. Do I need to upload blank.html as well?
what am I doing wrong?
please review http://www.paper.com/menu.htm
thanks in advance,
Kevin
I (well, my boss did) purchased the license a couple of hours ago. I already changed the menu. It works beautifully locally. However I uploaded all the necessary files to the server (via CuteFTP). The new menu would not work live. Do I need to upload blank.html as well?
what am I doing wrong?
please review http://www.paper.com/menu.htm
thanks in advance,
Kevin
I think John might have it, upload problem.
Seems like a problem with mmenudom.js - Try uploading it again and make sure it's sent as a text file.
Also, did you change the license details in milonic_src.js - These cannot be changed or the menu will break, your download will make these changes for you.
Hope this helps
Andy
Seems like a problem with mmenudom.js - Try uploading it again and make sure it's sent as a text file.
Also, did you change the license details in milonic_src.js - These cannot be changed or the menu will break, your download will make these changes for you.
Hope this helps
Andy
Kevin -
I just took your page and loaded it on one of my servers at http://www.west.asu.edu/sa/testsite/. The only thing I changed was to add http://www.paper.com/ to the JS calls so I was pulling everything from your server. As expected, it failed.
Next I changed the JS calls to get the 3 code files (same version as yours) from my server, but still call the _data file from your server. It works just fine at http://www.west.asu.edu/sa/testsite/index2.htm.
One of two things is wrong...
1. Your ftp program doesn't really understand ASCII (text) or all the code files were not uploaded in text mode, or...
2. You got a bad download from our server (not that our server is bad, but it happens, as I'm sure you know). Download the files again.
In either case, upload all the files again making sure the ASCII mode is checked, or try another ftp program.
I just took your page and loaded it on one of my servers at http://www.west.asu.edu/sa/testsite/. The only thing I changed was to add http://www.paper.com/ to the JS calls so I was pulling everything from your server. As expected, it failed.
Next I changed the JS calls to get the 3 code files (same version as yours) from my server, but still call the _data file from your server. It works just fine at http://www.west.asu.edu/sa/testsite/index2.htm.
One of two things is wrong...
1. Your ftp program doesn't really understand ASCII (text) or all the code files were not uploaded in text mode, or...
2. You got a bad download from our server (not that our server is bad, but it happens, as I'm sure you know). Download the files again.
In either case, upload all the files again making sure the ASCII mode is checked, or try another ftp program.
John
Hi Kevin,
John's right. Youre mmenudom.js and mmenuns4.js files are messed up. Both are wrapping lines way out, which effectively breaks the js code. (milonic_src.js is unaffected because its code does not extend as far to the right). Since the download comes in a compressed archive file, the culprit must be your upload. It's causing the wrapping. Don't know anything about CuteFTP. You could always try IE... just enter ftp://paper.com as the URL. If it works, you should be prompted for your ftp login. Then just drag and drop.
Alternatively, you might try CoreFTP Lite (it's free) at http://www.coreftp.com
Cheers,
Kevin
John's right. Youre mmenudom.js and mmenuns4.js files are messed up. Both are wrapping lines way out, which effectively breaks the js code. (milonic_src.js is unaffected because its code does not extend as far to the right). Since the download comes in a compressed archive file, the culprit must be your upload. It's causing the wrapping. Don't know anything about CuteFTP. You could always try IE... just enter ftp://paper.com as the URL. If it works, you should be prompted for your ftp login. Then just drag and drop.
Alternatively, you might try CoreFTP Lite (it's free) at http://www.coreftp.com
Cheers,
Kevin
Just opening the files in BBEdit should not have caused a problem. However, if you resaved them (without the proper settings) - that would definitely cause a problem. You probably already know this, but there's no reason to do anything with the code files except upload them.
I am a Mac user as well, and have no problem uploading these files. I use CaptainFTP, and Fetch is also very good.
I am a Mac user as well, and have no problem uploading these files. I use CaptainFTP, and Fetch is also very good.
John
Kevin,
I have used Cute FTP for years now and have uploaded my Milonic menu files and code files without any problems. As mentioned, your particular problem may not be with your Cute FTP program but with corrupted files, path problems or something else. But, as far as Cute FTP goes, try this:
Launch the Cute FTP program so your files open on your IPSs sever, or where ever they are. Then look at the very top tool bar and select "Transfer" (You may have to highlight any file on the server side window pane first). Then after you have selected "Transfer" from the top tool bar, a drop down box will appear. Select "Transfer Type", and another drop down menu select box will slide out. Finally, select "Auto". You don't have to do Save or anything, just close your Cute FTP program. Just to be sure, I would log right back in, just to be sure the changes you made took affect.
Anyway, I have had my Cute FTP program set this way for years and upload .gif, jpeg, .js, .exe, .doc. you name it, and they upload perfectly every time and work everytime when I download and use them.
Hope this helps,
Sounds like you have your menu working now, but thought I might be of some help with your Cute FTP program.
I have used Cute FTP for years now and have uploaded my Milonic menu files and code files without any problems. As mentioned, your particular problem may not be with your Cute FTP program but with corrupted files, path problems or something else. But, as far as Cute FTP goes, try this:
Launch the Cute FTP program so your files open on your IPSs sever, or where ever they are. Then look at the very top tool bar and select "Transfer" (You may have to highlight any file on the server side window pane first). Then after you have selected "Transfer" from the top tool bar, a drop down box will appear. Select "Transfer Type", and another drop down menu select box will slide out. Finally, select "Auto". You don't have to do Save or anything, just close your Cute FTP program. Just to be sure, I would log right back in, just to be sure the changes you made took affect.
Anyway, I have had my Cute FTP program set this way for years and upload .gif, jpeg, .js, .exe, .doc. you name it, and they upload perfectly every time and work everytime when I download and use them.
Hope this helps,
Sounds like you have your menu working now, but thought I might be of some help with your Cute FTP program.
Rudy
I'm biting my tounge here and trying not to have another rant about Apple Macs but boy do they give us problems
Recently had a similar problem from another customer, seems she couldn't even download the menu at all, had to give her a refund in the end.
Any idea what the problem is, is it just an incompatibility with file formats?
-- Andy

Recently had a similar problem from another customer, seems she couldn't even download the menu at all, had to give her a refund in the end.
Any idea what the problem is, is it just an incompatibility with file formats?
-- Andy
Sorry, Rudy, but I have to take issue with that. While "most" of the time the auto setting, in any ftp program, will work properly, it's just not always the case. I speak from the experience of more than just one person. With JS files it's always safest to select 'text' or 'ASCII' mode for the uploads.rudy wrote:Select "Transfer Type", and another drop down menu select box will slide out. Finally, select "Auto".
For that matter, it's the same for uploading HTML files, especially if there is code embedded, as they are just straight text as well.
John
Then I'm just going to say she simply didn't know what she was doing. Who knows what she was using to decompress the files, and what the ftp program/procedure was. I've never had a problem with anything I've gotten from you, and I would guess most of the Mac folks here are the same.Andy wrote:Recently had a similar problem from another customer, seems she couldn't even download the menu at all, had to give her a refund in the end.
Good grief - text is text, regardless. With the proper program (just like any other system), Mac fully understands .zip, and even .tar.gz, not to mention a slew of other formats that Win knows. I pass stuff back and forth between my Mac and (gulp) PeeC every day with no problems at all.Andy wrote:Any idea what the problem is, is it just an incompatibility with file formats?
The problem is the user. They buy a Mac for its capabilities and ease of use - both areas in which it definitely shines. However, many are really non-computer folks, and as soon as things get out of the super-easy sandbox they are completely lost. A little reading and the right program(s) would fix the problem, but their mentality is, "It's a Mac - it should do everything for me". Sorry - not in todays world.
John
You would think so wouldn't you. The problem we had the other day on that post I ranted on. Well, all I did was remove the white space from the tabled based menu and viola, it now workie.Good grief - text is text,
I suppose I could have found the offending character/s with a the hex editor but I really couldn't be bothered and couldn't wait to turn the Mac off. On stand-by it keeps powering up the hard drive for no reason, then shutting it down again but not before soing what seems like a full defrag.
Man, I hate those machines

So in essence, the Mac seems to be throwing in odd chars here and there but why and how?
-- Andy
I'll ass-ume you're running the latest OS (10.3.5).
Go to System Preferences/Energy Saver. Set the two 'sliders' to Never (sleep). Also make sure the checkbox in the lower left corner for putting hard disks to sleep is NOT checked.
As for throwing extra characters in, I still say it's not the Mac - it's the user...
Go to System Preferences/Energy Saver. Set the two 'sliders' to Never (sleep). Also make sure the checkbox in the lower left corner for putting hard disks to sleep is NOT checked.
As for throwing extra characters in, I still say it's not the Mac - it's the user...

John