TweezerMan

<{POST_SNAPBACK}> This is probably because the code is compiled in a binary form (I infer this from the requirements for either Zend Optimizer or IonCube). Code that is compiled into binary should run faster on the server, but it is unreadable by people. Another advantage to distributing complied code is that no one can copy or steal the code, but I don't know how much that was a factor for the creator of Shopping Cart Builder in choosing to distribute compiled code.

I found the following instructions for installation in Shopping Cart Builder's Knowledge Base: The way I read that, *all* files should be uploaded in BINARY mode. I'd suggest first deleting any existing Shopping Cart Builder files you have on the server (so there's no question whether the newly uploaded files overwrote the existing ones), then upload them again with your FTP program configured to use BINARY mode for all files, regardless of their file extensions.

I guess your method came from this MSKB article? In the article, assuming you're running Windows XP SP2, the only method offered to repair IE6 and Outlook Express is to reinstall SP2. The method you describe only applies to Windows XP and Windows XP SP1.

I did a little searching on Google, and it appears that your error is usually caused by files that were uploaded to the server in the wrong mode (ASCII instead of BINARY, or vice versa). If there were any installation instructions provided, I'd suggest looking to see if there was anything written about what FTP mode should be used with the files in your Shopping Cart Builder download. I'd also recommend not relying on any auto-detection of FTP mode when uploading the Shopping Cart Builder files. Instead, manually select the FTP mode so you know they are being uploaded in the correct mode to the server. Hope this helps...

Welcome to the forums, datingsas!

Welcome to the forums, Lisety!

Welcome to the forums, sdanks!

Welcome to the forums, wttl!

I have no problem performing a ping or trace route to savagegames.org. Assuming it's not a temporary problem, it looks to me like something is blocking you from sending out ping or trace route packets, like a firewall on your PC, LAN, or perhaps your ISP.

The MT interface pages (mt.cgi) look correct now. I think you just need to do a full rebuild on your weblog again, so the change in CGIPath will be reflected on your weblog's pages (such as the Search box).

You need to have "CGIPath" in front of the URL in the mt.cfg file, so MT knows what it is, like I indicated in my previous post: >CGIPath http://www.darkgraysheep.com/mt/

You're almost there. I think you still may have a problem with the CGIPath setting in your mt.cfg file too. It should read like this, based on what you posted in your first post: >CGIPath http://www.darkgraysheep.com/mt/

I checked the to make sure there was no #, but I am not sure about reuploading. And here is where my lack of experience will shine, but when I go to the cpanel-file manager and click upload, it of course directs me to my own hard drive, but the altered mt.cfg file is on the file manager, not my harddrive. If I were to upload it, wouldn't it rewrite the one I configured using the tutorial? <{POST_SNAPBACK}> Since you're editing mt.cfg directly on the server, forget what I said about re-uploading the mt.cfg file - this is not causing your problems and you don't need to re-upload it. What do you have for the CGIPath and StaticWebPath settings in your mt.cfg file, and does the StaticWebPath setting have a "#" at the beginning of the line? You should not have to do this, but to get it working quickly, I'd suggest removing any "#" at the beginning of the StaticWebPath line if there is one, then change it to the following: >StaticWebPath /mt/ Save the mt.cfg file, and you should be in business! When I click rebuild nothing at all happens. No screen comes up, it's like it's a dead button. And when I did the test posts I did change them from draft to publish. So that isn't the problem. <{POST_SNAPBACK}> I believe the "dead button" problem is a symptom of MT not reading mt.cfg correctly (specifically, the StaticWebPath setting). The rebuild button (and a number of other buttons) in the MT interface use some javascript code to make them work. This javascript code is in the mt.js file, and MT currently isn't looking for it in the right place, making the button appear "dead". When MT is reading the StaticWebPath setting in mt.cfg correctly, the rebuild button should start working too.

I'm not aware of any issues with the Weblog Config settings that darkgraysheep is using, provided that both the /blog and /archives directories exist in the public_html directory. MT does not require the Local Archive Path to be a subdirectory of the Local Site Path.

I take it that means Thunderbird is now working okay? I'd chalk it up to a bad Monday - one reason why I hate Mondays!! Please don't feel stupid - your e-mail program quit working, you asked your TCH family for help, and ultimately you found out what the real problem was. Nothing wrong with that! Both uniquelyalike.com and www.uniquelyalike.com both resolve for me now.

Welcome to the forums, darkgraysheep! It looks to me like you need to create the "archives" directory in your public_html directory for MT to write your weblog archive pages in. MT won't create it for you - it will display an error instead if it does not exist. The problem with the 404 errors referencing "URL /cgi-bin/mt.cgi" sounds like MT is not reading your mt.cfg file properly. Make sure that the CGIPath setting in mt.cfg does not have a "#" at the beginning of the line, and re-upload the mt.cfg file to your server, making sure that it is uploaded in ASCII mode (*not* BINARY mode). You should be seeing some sort of errors when rebuilding, but since you're not, have you changed the 4 entries you wrote from "Draft" to "Publish"? MT doesn't publish entries that are set to "Draft". Your Weblog Config settings look correct, so I don't believe they're causing you any of your problems. Hope this helps...

That would do it!

uniquelyalike.com currently doesn't resolve for me - I'm getting this in my browser at the moment: And if I try to look up uniquelyalike.com with WinXP's nslookup command, I get this response:

I'll second the opinion that it appears to be a domain problem. I could not verify that the DNS record for uniquelyalike.com actually has an MX record (mail server record). I also did a couple of e-mail tests from dnsstuff.com:

What kind of errors are you seeing?

Welcome to the forums, drifter! Please do not post the same question to multiple threads, as this is a violation of the Forum Guidelines:

The file format is more than "XML-like" - it is true XML. While the <loc> and <lastmod> tags could be described with Atom or RSS, there's other tags in the sitemap spec that cannot be.

I don't see how either of them could be used to describe a site map.

#1 will always happen, provided that the 'action' parameter in your <form> tag points to a valid script on your site. What happens when the form data is submitted depends on the design of the script. #2 requires a script that can accept your site's form data, compose an e-mail with it, then send it to you. #3 - I don't know what you mean by "configuring application forms". #4 - There's lots of tutorials and information on the internet about how to build HTML forms in general - I'd suggest searching Google. To find a script that will e-mail you submitted form data, try searching hotscripts.com (there's quite a few available).

Welcome to the forums, Topaz! I've never used osCommerce, but your error message sounds like a permissions problem. Check the permissions on the index.php file listed in the error message - if the permissions are 0644, I'd suggest changing them to 0666. That should give your script permission to write to the file.