On Tuesday, September 25, 2012 4:48:08 AM UTC-4, (unknown) wrote: > I maintain my own website using Seamonkey. I recently purchased a new laptop > and now when I "Save" and "Publish" the changes don't appear. (after refresh) > I think the data is going to a different place that my host is not receiving. > I save to ftp://ftp.myname.com/ and publish to www.myname.com The filename > is "index.html" > > Can someone tell me the exact path ways for saving data. Is it going to the > server or my own laptop? Stupid q but frustrating as it worked before. Where > is my "target" path to add new images and revise files for use on my website. > > cheers for any help. Gaza
Hi, Since this worked before, have you tried to navigate to the page via the browser, that is, have you tried putting "ftp://ftp.myname.com"; in the location bar to see what comes up? when checking the publishing setup, I see a few things; "Publishing address (e.g.:'ftp://ftp.myisp.com/myusername'):" Notice how it gives the path *through 'myisp' as you are likely a directory on the computer that is hosting your page. In other words, you are navigating to ftp.myisp.com to your space which is myusername. The help button, in my case does nothing.... Which may help you. Also, the help on the hoster's website may help as they may have some sort of unique setup. For instance maybe they have security requirements. anyway, maybe that will help, --- OK, main composer window > help (search : publishing)> publishing pages > Solving Common Publishing Problems: """" Solving Common Publishing Problems If one or more of your files fail to publish, the Publishing Status dialog box displays an error message that can help you determine what went wrong and how to fix it. If you are still unable to publish a file, save the file to your hard disk by opening Composer's File menu, and choosing Save. You can then open the file at a later time to try to publish it. To quickly locate the file later, open Composer's File menu, and choose Recent Pages. In this section: Verifying Your Publishing Settings Checking Your Filenames Fixing Publishing Errors Verifying Your Publishing Settings To verify your publishing settings: Close the Publishing Status dialog box, if it is open. Open the Edit menu and choose Publishing Site Settings. In the Publish Settings dialog box, confirm that the site settings are correct for the site you are trying to publish to. If you're not sure, check with your ISP or web hosting service. Verify that you correctly entered the publishing settings: You may have accidentally mis-typed one of the settings. Verify that you entered the correct publishing address: Web hosting services or ISPs may refer to the publishing address as the server name, the hostname, or the server/host. They often specify the publishing location as ftp.myisp.com/username, where username is your user name. For the publishing address to be correct, you must precede the publishing location with either ftp:// or http://. For example, the correct publishing address for the above-mentioned site would be ftp://ftp.myisp.com/username. Checking Your Filenames Examine the names of any files that failed to publish. Make sure that the filenames: Use only numbers or lowercase or uppercase letters. While it's acceptable to create filenames that use uppercase letters, you can avoid potential errors in later locating the published file if you only use lowercase letters in your filenames. When you publish files to a web server, filenames become case-sensitive on the web server. It may be harder for you to remember files names that use only uppercase letters or that use a mix of uppercase and lowercase letters. For example, when you try to locate a published file by typing the filename's web address into the browser's Location Bar, you must enter the filename exactly as you created it, using the same combination of uppercase and lowercase letters. Don't use punctuation characters or spaces. Underscores ( _ ) or hyphens ( - ) are OK. End with .html or .htm (for Composer filenames). Use less than 32 characters. Fixing Publishing Errors If one or more of your files fails to publish, look at the messages Composer displays in the Publishing Status area of the Publishing dialog box. You can use these error messages to help determine what went wrong and what to do to fix the problem. Error Messages: Filename not found. X of Y files failed to publish. The subdirectory directory name doesn't exist on this site or the filename filename is already in use by another subdirectory. The filename filename is already in use by another subdirectory. The server is not available. Check your connection and try again later. You do not have permission to publish to this location. You are currently offline. Click the icon near the lower-right corner of any window to go online. There is not enough disk space available to save the file filename. The filename or subdirectory name is too long. Error Message: Filename not found. or X of Y files failed to publish. Error Description: One or more image files or CSS files failed to publish because Composer could not find them. Some typical reasons might be: The file location you typed is incorrect. The file's location on the web is not accessible. The file's location was changed or the file was deleted or moved to another location. Possible Solutions: Look for broken images in the page you are trying to publish. Broken images will appear with this icon in the page. To correct the image's address, double-click the broken image to display the Image Properties dialog box so you can enter the correct address. Remove the broken image from the page by selecting it (click once on the image), and then pressing Backspace or Delete on your keyboard. If the image is unavailable because the server where the image resides is inaccessible, try publishing the page at a later time. If the missing file is a CSS file, you must first verify the correct location of the CSS file. To fix the file's address in Composer, click the HTML Source tab and edit the file's location in the HTML source code. You should only edit the HTML source if you are familiar with HTML tags. Error Message: The subdirectory directory name doesn't exist on this site or the filename filename is already in use by another subdirectory or The filename filename is already in use by another subdirectory Error Description: You specified the name of a remote subdirectory that does not exist at the publishing site. Composer can only publish to a remote subdirectory that already exists at the publishing location. Or, you specified a filename that is identical to the name of an existing subdirectory at the publishing site. For example, in the Publish Page dialog box, under the Publish tab: for Site subdirectory for this page, you may have typed the name of a subdirectory that does not exist at the publishing location. you checked Include images and other files, and then you typed the name of a subdirectory that does not exist at the publishing location. one of the files you are attempting to publish has the same name as a subdirectory at the publishing site. Possible Solutions: Use a separate FTP program if you want to create, rename, or delete subdirectories at the publishing site. Ask your service provider if they recommend a particular FTP program. You can usually find information on FTP programs in the Help or Support sections of your service provider's website. FTP programs are also available from shareware sites such as ZDNet Downloads. Don't use subdirectory names that end with .html or .htm. Only your Composer filenames should end with .html or .htm. Subdirectory names are case-sensitive, so be sure to enter a subdirectory name exactly as it appears at the publishing location. Error Message: The server is not available. Check your connection and try again later. Error Description: This error can have many causes. For example: Your publishing site settings may not be correct. Your Internet connection may have been lost. Your modem or other equipment that you use to connect to the Internet might not be functioning correctly. The web server that you are trying to publish to might be unavailable due to a technical problem or to an unknown circumstance. Your ISP or web hosting service may be experiencing technical problems. Possible Solutions: Verify that your publishing settings are correct and that you entered them correctly. See Verifying Your Publishing Settings for more information. Make sure your Internet connection is working by attempting to view a web page using the browser. For example, confirm that you can successfully view the page http://www.mozilla.org. If your Internet connection is not working, verify that all hardware, telephone connections, modems, and network connections are functioning properly. Use the browser to try to view a page at the website you are attempting to publish to. If you can successfully view other websites but cannot view a page at the publishing site, your ISP or web hosting service may be experiencing technical problems. Try publishing again later. Your ISP, web hosting service, or the web server may be experiencing temporary technical difficulties. Error Message: You do not have permission to publish to this location. Error Description: You are attempting to publish to a location that you are not authorized to use. You can only publish to sites where you have been granted access by your ISP or web hosting service. Possible Solutions: Verify that you entered the correct user name and password in the Publishing Site Settings dialog box, or in the Publish tab of the Publish dialog box. Contact your ISP to find out where you can publish your pages at their site. Find a web hosting service that you can use to publish your pages. In the browser, search for web hosting. Error Message: You are currently offline. Click the icon near the lower-right corner of any window to go online. Error Description: You are attempting to publish, but your SeaMonkey Internet connection is currently in the offline state. Your Internet connection must be in the online state (connected to the Internet) in order to publish your pages. Verify that your Internet connection is currently offline by looking at the online/offline icon in the lower right corner of any SeaMonkey window. If you are currently offline, the icon appears as . Possible Solutions: Click the online/offline icon to go online. In the online state, the icon should look like this: . Make sure your Internet connection is working by attempting to view a web page using the browser. For example, confirm that you can successfully view the page http://www.mozilla.org. Error Message: There is not enough disk space available to save the file filename. Error Description: The remote web server's hard disk is full, or you may have exceeded the amount of disk space allocated to you by your ISP or web hosting service. Possible Solutions: Use a separate FTP program to delete unnecessary files at your publishing site. Ask your service provider if they recommend a particular FTP program. You can usually find information on FTP programs in the Help or Support sections of your service provider's website. FTP programs are also available from shareware sites such as ZDNet Downloads. Find out from your ISP or web hosting service about increasing your disk space allocation, or switch to a different service that can satisfy your needs. If the web server is located at your company or school, contact the network administrator to find out if you can publish to a different location that has more disk space, or if you can request that additional disk space be allocated to your current publishing location. Error Message: The filename or subdirectory name is too long. Error Description: The number of characters in the filename or the subdirectory name is not supported by the web server computer that you are trying to publish to. Possible Solutions: Limit the length of your filenames and subdirectory names to less than 32 characters. Some operating systems do not support names longer than 32 characters. """""""""""""""" _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
