Jump to content

TweezerMan

Members
  • Posts

    1,763
  • Joined

  • Last visited

Everything posted by TweezerMan

  1. Access to GET, wget, and lynx has been removed from the servers as a security measure. You would need to modify your script so it can be run without using these tools.
  2. Check the web server error log and see what reason it gives for the 500 errors.
  3. Welcome to the forums, Andrew!
  4. >$message = '$first_name.$last_name.$email.$headline.$story_text'; Variables are not evaluated when they are enclosed in single quotes as you them - the variable names are seen as just plain text. To have the variable names evaulated, you need to enclose the above string in double quotes (").
  5. Welcome to the forums, kook44!
  6. Welcome to the forums, Pele!
  7. Welcome to the forums, Reality_Burst!
  8. I no longer see the <script> tag either. Maybe you or the Help Desk did something that fixed phpBB back to the way it was?
  9. It not possible for you to make any changes to httpd.conf. I don't believe the Help Desk would make this change for you as this would make the server have a non-standard configuration. Also, any changes to the httpd.conf file could affect every customer on your server. Since TCH does not offer shell access, you would not be able to run these commands. The Help Desk could run these commands for you, but I'm not sure it would be much help since you probably won't be able to modify httpd.conf as you want. This option would have to be changed by the Help Desk. I don't know if the Help Desk would be willing to make this change or not.
  10. Looking at "View Source" of your phpBB main page, this line is the very first line of code, even before the !DOCTYPE or <html> tag: ><script language=JavaScript src=/rmpcugt.js></script> The link to the script does not appear to be valid now. But the position of this script, ahead of all other HTML code, in an invalid place for a <script> tag, and the odd, psuedo-random name of the script leads me to suspect that this is not your code, but code that a malicious attacker may have inserted into your site.
  11. The directory is publicly viewable, which isn't quite the same as 'become public'. Hotlinking will not prevent someone from viewing the directory by itself. If you don't want the directory to be viewable, you need to go into the Index Manager in your CPanel and set that directory to "No Indexes". It's not that phpBB does or doesn't use java - the user is saying that something on one or more of your forum pages is attempting to download a trojan. A link to a specific page where this occurring would be extremely helpful, as it could be verified whether or not there is mailcious code in the page. Your user was infected by a trojan, known as 'Trojan Moo': Opening the folder should not have triggered this trojan - I think you'd have to actually view an infected .jpg file. It's possible that the user had already been infected and the timing of 'm00.exe' appearing on the desktop at the same time the /images folder was opened was merely coincidence. You may not see anything on your PC - the problems (if they exist) would be with files on the server.
  12. One with lots of bandwidth. Each viewer does have its own file format (encoding). Most users should be able to play a Windows Media Player or QuickTime video file. I don't know that I would provide files formatted for other players (such as RealPlayer). Each video segment should be a single file. You would be able to move them as you would any other file, although moving 250 files that can each be up to 3 to 5 megabytes in size (a guess here) may take some time to move. I would definitely be looking for these two things: 1) a host that allows large amounts of total bandwidth per month, and 2) a host that can accomodate many users hitting the video files at one time. You (or your expert) would need to estimate what's needed here based on the size of the video files you'll be hosting, and taking a guess about the probable usage patterns of your students (how many students can be expected to view videos at any one time, and how many times each student can be expected to view any particular video). Yes - the syllablus would just link to the video file as it would to a regular web page. The videos would not have any access controls unless you put some controls in place. Controlling access looks to me like it would be something that is difficult to set up, control, and manage (probably the most difficult part of your project). A web server provides crude methods to control access, but I don't know that they would be practical to use for your project. You may want to investigate using a script (possibly a custom written one) to manage and control access to your video files. Anyone wanting to view one of your videos would have to go through this script to be authorized, otherwise they are not allowed to view the video file. Not having any experience in this area, I don't have any suggestions. Sorry!
  13. Welcome to the forums, dogboy!
  14. Welcome to the TCH family and forums, rjjd!
  15. This assertion is not correct: Image links aren't the same thing as image maps. The script does not position the menu in the proper position because the method the script uses to figure out where the menu should go does not work with image maps. The script adds together the left and top offsets from each successive outer containing element to figure out where the menu needs to go. Neither Internet Explorer nor Firefox correctly trace the successive level of containing tags surrounding a <map> and <area> element, so neither of them can correctly calculate a particular <area> element's position to put the menu in the correct place. You'll need to 1) find a different script, 2) remove the image map and use ordinary text links, or 3) write your own javascript code to correctly calculate an <area> element's left and top offsets from the upper left corner of the web page. I'd probably recommend option 2. I tried doing #3 (writing my own code) and gave myself a headache trying to come with something that works in both IE and Firefox.
  16. Welcome to the forums, bobhilke!
  17. Glad to hear you've got it working! I thought a lot about your problem and didn't see any way to effectively solve it without having separate domain names for each site. It took me a while to remember that you could set up dummy domains to point at 127.0.0.1 in /etc/hosts, and after that, solving the problem got much easier. I was originally going to suggest 'lazytiger.localdomain' for the domains, but I wasn't 100% sure if that would work or not. I like the '.local' even better - it's shorter, and therefore easier to remember and type.
  18. Google has to crawl and index the other sites that have linked to you, which does take time. Also, I don't believe Google updates the incoming links index as frequently as the content index (not sure about that, just something I heard somewhere). The Googlebot should be able to follow your site's nav menu links to find the rest of your site's pages. It should find them in all in time. I don't think so, but that's just my opinion.
  19. I didn't know I was subliminal posting before!
  20. I don't really know anything about DreamWeaver, but to do what you're asking, it sounds like you need to have DreamWeaver perform a query that joins the table you're using with whatever table contains the parent ID numbers and names. The query would pull data from both tables, getting the parent name for the parent ID number stored in the first table. The parent name would then be a field in your recordset that you can display like any other field in your recordset. I don't know what kind of query you have DreamWeaver performing now, but assuming it a simple query like this: >SELECT * from people ('people' is the name of the table you're querying now) ...you could join it with a 'parents' table to get the parent name like this: >SELECT people.*, parents.name as parentName from people JOIN parents ON people.parentID = parents.id Hope this helps...
  21. I think you'd need to use an actual domain name for each site that you want to set up a separate DocumentRoot for. Once you've done that, then you can set up a VirtualHost on the web server for each domain. Make up a domain name for each site, and add it to the /etc/hosts file on your server so the domain name will resolve and point back at your machine. In the /etc/hosts file, it should already have the following in it at a minimum: >127.0.0.1 localhost I'm going to suggest here 'jeff.com' as the main 'dummy' domain, and set up each site as a subdomain of 'jeff.com'. For the two sites you've mentioned, we'll use 'lazytiger.jeff.com' and 'bluestars.jeff.com' as the new domains we want your machine to recognize. Add these subdomains to your /etc/hosts file and point them at your machine (127.0.0.1): >127.0.0.1 localhost 127.0.0.1 lazytiger.jeff.com 127.0.0.1 bluestars.jeff.com After you've made these changes and saved them, I believe you'll need to restart your network so the /etc/hosts file will be re-read. Once you have the domain names set up in /etc/hosts, then you can set up a VirtualHost on the web server for each one. In your httpd.conf file: >NameVirtualHost *:80 <VirtualHost *:80> ServerName localhost DocumentRoot /Users/jeff/Sites </VirtualHost> <VirtualHost *:80> ServerName lazytiger.jeff.com DocumentRoot /Users/jeff/Sites/lazytiger </VirtualHost> <VirtualHost *:80> ServerName bluestars.jeff.com DocumentRoot /Users/jeff/Sites/bluestars </VirtualHost> The first VirtualHost block is necessary because it will be the configuration used if the host name in a request does not match any of domain names specified by the ServerName directive in any VirtualHost block. (The first VirtualHost block is a 'default'.) I don't know what you've configured as 'ServerName' in the main section of your httpd.conf file - whatever you've configured there, you should use the same thing for the ServerName in the first VirtualHost block. After you've added the virtual hosts and saved the httpd.conf file, then you'd need to restart the web server. You should now be able to view your sites by browsing to http://lazytiger.jeff.com/ and http:/bluestars.jeff.com/. Each site will use the DocumentRoot specified, and your relative URLs/links should work correctly. I've tested this on a Windows server running Apache, and it works as I have explained it. You may need to make minor adjustments if I've misunderstood something about your machine or web server configuration (Apache on OS X). Hope this helps...
  22. Welcome to the forums, Rhye! (waves at Rhye sitting about 5 feet away )
  23. What's happening is that the menu item 'Frequently Asked Questions' is being line wrapped, making the div it is contained in be two lines tall. The other menu items rest at the bottom of the div, and the menu with 'shop by', etc., is overlaying this now new second row of your menu, covering up all of the other menu options. Playing around with your page in FrontPage, I was able to restore the menu to its proper appearance by replacing the spaces in 'Frequently Asked Questions' with non-breaking space characters: ><li>Frequently Asked Questions</li> The menu options then all appeared, but they were *really* spaced out. I was able to correct this somewhat by reducing the width of the <li> elements from 107px to 75px: >#topnav ul li { display: inline; height: 17px; padding: 0px 10px 0px 10px; text-align: center; width: 75px; } Hope this helps...
  24. Thank you to everyone who voted! (Even those who didn't vote for me! ) And thank you TCH! I'll be putting the new PC to good use: blowing up bad guys in Unreal Tournament and (hopefully) Doom 3!
  25. What you're seeing is the #banner div extending just slightly below the image in IE. The following seems to fix the display in IE without disturbing the display in Firefox: In your stylesheet, set the height for the #banner div equal to the image height. >#banner { font-family: Verdana, Arial, sans-serif; color: #fff; background-color:#006; text-align: left; height: 70px; } Then add a style to set a negative bottom margin for the image, just enough to make the 'line' go away: >#banner a img { margin-bottom: -3px; }
×
×
  • Create New...