TweezerMan

Browsers can do some auto-guessing of the index file name if the initial URL doesn't return a page, but that's not what we're really talking about here. The server config file has a directive called DirectoryIndex that determines what file names and in what order the web server will look for index files when there isn't a file name in the URL (the URL ends in "/"). I believe this is what the servers are configured to look for (taken from a forum post by TCH-Bruce): >DirectoryIndex index.html index.wml index.cgi index.shtml index.jsp index.js index.jp index.php4 index.php3 index.php index.phtml index.htm default.htm If you want to alter the order of pages searched, or add/delete file names from the list, you can add a DirectoryIndex directive to your /public_html directory's .htaccess file, and it will override the server's setting. Assuming the above list is correct, if there's both an index.htm and index.html page in a directory, the server would serve the index.html file, as that file name is listed before index.htm in the DirectoryIndex directive.

You need to re-upload <MT dir>/tmpl/cms/pinging.tmpl to the server. When you originally uploaded the MT files, that particular one was not successfully uploaded - it is currently a zero byte file. I'd say this would account for the behavior you're seeing.

The sending of trackback pings and weblog notification pings is a two-way communication process. In order for MT to recognize a ping as successful, MT must get a response back from the server being pinged within a certain period of time. The larger weblog pinging services such as weblogs.com get hammered constantly with ping notifications, and they often don't respond back to the pinging server in time, even though the ping itself was successfully received. What I suspect is happening is that MT is waiting long enough for the responses to its pings that your browser is timing out, and since it hasn't received any new data to display, you get left with a blank page.

Welcome to the forums, Dianna!

Welcome back, Mark!

That error message doesn't look like the full message - what file did the error occur in? I looked at the code, and I was mistaken about the '<!--tag-->' text in the category description of a tag's category. That text needs to stay in the category description - it is how the Tags plugin identifies whether a category is being used as a tag or not. It doesn't look like it matters whether the '<!--tag-->' text is before or after the actual category description - it just needs to be in there somewhere. (When an existing category is used as a tag, the Tags plugin appends the '<!--tag-->' text after the existing category description.) Replacing the '<!--tag-->' in the tag's category descriptions may resolve the issues you're having now, but it's hard to be sure when you don't know what the real error is. Yes, you are supposed to be able to use more than one tag on an entry if you wish.

Yes. The description that you're seeing is just a placeholder that the Tags plugin puts in a new category when it creates one. You could have tried this yourself and saw what happened - it would either work or it wouldn't, and if it didn't, you could have put the original description back

Yes, if you want display a description for a tag, you would need to enter that description in the tag's corresponding category description. The MTTagDescription tag is actually just an alias for the MTCategoryDescription tag.

On a page within a subdomain, you can't use a relative URL to refer to a page outside of the subdomain. If you wanted to link to a file in your main domain, you'd need to use a full URL. That's because PHP code is script code that is run locally on the server:

Welcome to the forums, Cesar!

Welcome to the forums, mollyo!

Welcome to the forums, manojvp! These are not the same thing - they are two different ways to point at the same location. The first is a local server path, and the second is a URL. A local server path can only be used by a script running locally on the server - you can't use it in the HTML of a web page. What you're trying to come up with is what's known as a 'relative URL' - basically a partial URL, or a URL 'path'. To link to your stylesheet in your web page, instead of linking with a full URL like this: ><link rel="stylesheet" type="text/css" href='http://www.organswap.org/presentation.css'> ...you could link to it with a relative URL like this, omitting the domain portion of the URL: ><link rel="stylesheet" type="text/css" href='/presentation.css'> When the web page is loaded in the browser, the browser will complete the relative URL with the domain name from the web page's URL to get the full URL of the stylesheet. The advantage to using relative URLs wherever you can is that if you ever decided to change the domain name for your web site, relative links to other pages and files on your web site will still work and not be broken - you won't have to edit every link to replace the old domain name with the new one. You can also link to images with a relative URL. This full URL: >http://www.organswap.org/images/aspen100x800.jpg ...can be replaced with this relative URL: >/images/aspen100x800.jpg A relative URL that starts with "/" is relative to the root of the domain (like the examples I've shown above). You can also use relative URLs that do not start with "/" - these URLs are relative to the URL of the web page that it appears on. I usually recommend not using relative URLs that aren't relative to the root of the domain - links using this type of relative URL are easily broken. Hope this helps...

The purpose of the playlist is to play the files one after the other. Even the full-blown Windows Media Player doesn't stop playing individual items when it is playing from a playlist. If you want the playback to stop at the end of each video, you're going to have to add some custom javascript programming to control the player. As an example, here's some code that 1) adds a drop-down box to select .mpg's directly from (a fake playlist), 2) a 'Previous' and a 'Next' button to move backwards and forwards through this playlist, and 3) javascript code for these controls to interact with the player. Add the following just before the <object> tag for the media player: ><script type="text/javascript"> function media_select() { var opt = document.getElementById('playlist'); if (opt.selectedIndex > 0) { VIDEO.enabled = true; VIDEO.URL = opt.value; VIDEO.controls.play(); } else { VIDEO.enabled = false; VIDEO.URL = ''; } } function prev() { var opt = document.getElementById('playlist'); if (opt.selectedIndex > 1) { opt.selectedIndex = opt.selectedIndex - 1; } else { opt.selectedIndex = opt.length - 1; } media_select(); VIDEO.controls.play(); } function next() { var opt = document.getElementById('playlist'); if (opt.selectedIndex < opt.length - 1) { opt.selectedIndex = opt.selectedIndex + 1; } else { opt.selectedIndex = 1; } media_select(); VIDEO.controls.play(); } </script> <div style="position: absolute; left: 280px; top: 448px; width: 386px;"> <select id="playlist" onchange="media_select()"> <option value="">::::: Choose Your Video Here :::::</option> <option value="http://url/to/video1.mpg">Title of mpg #1</option> <option value="http://url/to/video2.mpg">Title of mpg #2</option> <option value="http://url/to/video3.mpg">Title of mpg #3</option> </select> <input type="button" id="prev" value="|<<" title="Previous" onClick = "prev()" /> <input type="button" id="next" value=">>|" title="Next" onClick = "next()" /> </div> Add additional <option> tags as necessary for each video you want available to the player. For each set of <option> tags, put the URL to each video in the 'value' attribute, and the video's title between the <option> and </option> tags. In the html for the player, set the URL to an empty string: ><PARAM NAME="URL" VALUE=""> The new controls should appear just below the media player, but you can place them anywhere you want around the player or elsewhere on the page by adjusting their position in the <div> tag. The Previous and Next buttons on the player won't be functional, since now there's no playlist loaded again, but the new HTML buttons will imitate their functionality. When an .mpg is selected from the drop down, the javascript code will load that one .mpg file and automatically play it. At the end of the video, the player will stop. When the "Previous" or "Next" buttons are clicked, the javascript code will load the previous or next video in the drop-down llist, update the drop-down list with the new selection, then automatically play it. At the end of the video, the player will stop. Clicking "Previous" or "Next" at the end of the list will wrap around to the other end of the list and select that video to play. Give it a shot, see what you think...

The main problem with installing LAME is that it requires compilation from source code (the './configure' and 'make' commands). All of the other commands can be done from CPanel's File Manager. You'd have to submit a ticket to the Help Desk and ask them if they would install it, but I don't think they would.

What you'd need to do is create a playlist file and replace the link to the .mpg file in the <param name="url"> tag with the link to the playlist. The "previous" and "next" buttons in the media player will then function to play the previous and next items in the playlist. The player you have coded is an embedded Windows Media Player, so you could use Windows Media Player (WMP) to create your playlist. WMP saves playlists in .wpl format by default, but you can load the playlist in WMP and do a "Save Playlist As..." to save the playlist in .wpl, .m3u, or .asx formats. (I have no idea which format is better or best.) Once you have the playlist created as a file, you'll probably need to open it in a text editor and edit the file locations of the individual media files. The WMP playlists I looked at used relative paths that probably wouldn't work if the playlist file was moved or uploaded to a web server. Hope this helps...

I took a look at the Gallery code, and where that error occurs, Gallery is specifically testing /albums/.users/userdb.dat, where "/albums" is the album directory you've configured in Gallery. I guess this would be /photos/.users/userdb.dat in your case...? Anyway, Gallery says it does not have write permission on that file (meaning it's probably not 0777).

According to Gallery's Troubleshooting FAQ, something's changed the permissions on your /albums folder from 0777 so that Gallery's scripts no longer have write permission there. The recommended solution is to use an FTP program to recursively set the permissions on the /albums directory and every file/directory in it to 0777 (including the .users directory, which may be hidden). If you are unable to do this with your FTP program, you can submit a ticket to the Help Desk and ask them to do this for you.

Although I have FP2000, I've never used it to publish a web page. I tried using it to publish via FTP a little while ago, as that option seemed the easiest for me without having to mess around too much with my web site. Although you said some files were uploaded when you published your site, they do not appear when you browse to http://www.lisafrase.com/, which tells me that the files are not being uploaded to the correct directory on the server. When you actually publish your site in FrontPage (to perform an FTP transfer), you need to specify the following as the location: >ftp://ftp.lisafrase.com/public_html/ "ftp.lisafrase.com" should be the proper address of your FTP server, and the "/public_html" tells FrontPage to start publishing your web pages in that directory. The /public_html directory on the server is the directory that the web server will look for your web pages in when you browse to http://www.lisafrase.com/, so it is important that your files end up in this directory. Re: FTP timeout - FTP transfers do sometimes hang up and not finish - it happens from time to time with FTP servers. You just need to try your transfer again. While I was testing, I had to republish 3 times before all of the files would transfer. Hope this helps...

Topic moved for organization. You have two different index pages on your site. The new page you're uploading is index.htm, but browsing to http://www.Gale2006.com displays the page index.html. If you delete the index.html page from the public_html directory on the server, browsing to your URL should display the new page instead (index.htm). Or, you could change the filename in FrontPage to index.html so it will overwrite the existing page on the server (and delete index.htm as an unnecessary duplicate). One way or the other, you ought to get rid of whichever file extension you don't want to use for the main index page. Hope this helps...

Topic moved for organization.

The commands in the "script" are MySQL database queries that add your "bad words" directly to the phpBB database. As others have mentioned, you can run these MySQL queries in phpMyAdmin, which is already installed and available on your TCH account. (CPanel -> MySQL Databases - the link to phpMyAdmin is at the bottom of the page.) Once within phpMyAdmin, select your database from the "Database:" drop-down box on the left side of the page if you have more than one database. Then click the "SQL" tab, at the top of the right side of the page. Copy the MySQL queries from the "script" and paste them into the large box labelled "Run SQL query/queries on database <database_name>", then click the "Go" button just below that box. This will run the query, and assuming there's no problems or errors, all of the words will be added to the database. Hope this helps...

Topics merged.

Welcome to the forums, Yankman30!

Welcome to the forums, Rory!

Welcome to the forums, erik!