TweezerMan

Welcome to the forums, KL21!

Yes, once you've used up your disk space, the server will refuse to write additional files until you either delete some files or purchase additional disk space.

To my knowledge, there is no way to zip or tar/gzip a folder from CPanel. You'd need use a custom script to do this.

Welcome to the forums, lapinos!

Welcome to the forums, Lorraine!

There's a number of sites noting the 0 PRs, but no one's heard anything from Google about why or what's going on. I doubt that PR is going to be discontinued - I'm betting that it's due to some sort of bug or a change in the PR algorithm.

I don't believe your problem is static vs. dynamic pages. I'm a little fuzzy on exactly how you've set up your dynamic pages, but from your earlier description: ...I got the impression that these search pages displayed their results via the same URL, regardless of what the user searches for. The AdSense ads are being delivered based on content that Google saw from some other search, which would explain why the ads don't correspond with the content on the page. If you're interested in using an application to manage your content, there is a whole host of apps to choose from. If a blogging application would meet your needs, the more popular ones now include WordPress, Movable Type, TextPattern, and Expression Engine. If you'd rather use a full-blown CMS, I've know of Drupal and Mambo (but I don't really know that much about CMS systems).

It looks to me like the server path to the cron.php isn't quite right - the public_html directory is missing from the path. I think your cron command should be the following: >php /home/andymansker/public_html/moodle/admin/cron.php

The Apache manual recommends against configuring the server to parse .html and .htm pages for server-side includes: What is recommended instead is to use the XBitHack directive in your .htaccess file: >XBitHack on With XBitHack enabled in your .htaccess file, you can have specific .html pages parsed for server-side includes by setting the permissions on those files to be executable.

Welcome to the forums, dancedevotee!

I took a look at phpinfo() on server 49, and this is what it's showing for the PATH environment variable: >/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin What's notable here is that the /usr/local/bin and /usr/local/sbin directories are not in your PATH environment. Since 'convert' is only available in the /usr/local/bin directory, you'd have to specify a full path to execute it: >echo shell_exec('/usr/local/bin/convert -version'); I'd be willing to bet that if you run your script after modifying it like I suggested above, you'll see an error like the following: >sh: line 1: convert: No such file or directory ...because 'convert' isn't in any of the directories listed in the PATH environment variable. I'd suggest reopening your Help Desk ticket (or submit a new one) and request that /usr/local/bin and /usr/local/sbin directories be added to the PATH environment variable.

I agree that it looks odd. One thing I'd suggest - modify your shell_exec() command so errors are redirected to standard output (where your script can capture them): >echo shell_exec('convert -version 2>&1'); // What is the version of imagemagick running As your script is, you won't see any error messages from commands run by shell_exec() if one occurs. With the above change, error messages will be output to the page.

Welcome to the forums, orgcoco!

Welcome to the forums, hyspah!

You shouldn't have had to create any folders other than the GPS2 directory. Based on the error message that you were initially receiving: >[7307] VDB# exec failed for '/home/users/lilsadam/www/lilsadam.cogia.net/netgps.pl' [11] ... /home/users/lilsadam already exists. If you're logging with an FTP program, this may be masked from you - you may not see the "/home/users/lilsadam" part of the directory tree. If this is the case, I believe you should see the "www" directory in the list of folders when you first log in. You would need to create the GPS2 directory right there, so it appears in the folder list along with "www". The path to the GPS2 folder would still need to be what I specified above, as that is the absolute file path (which isn't masked from a script running on your account). However you managed to upload the netgps.pl script to your server, it looks to me like you should be able to go up 1 or 2 levels in the directory structure to where you can see the "www" folder and create the GPS2 directory there. If you had your account here, your script would already be up and running. However, since you need the script up and running before tomorrow (Saturday), signing up for an account today isn't going to be of much help, as it can take 24-72 hours for a domain name to propagate through DNS. It's possible, but I wouldn't guarantee that you'd be able to access your script through your domain by tomorrow.

Earlier you said that you set $filedir to the following: >my $filedir = '/sys/Home/Users/lilsadam/'; # NOT in the webroot! Are you sure this is a valid directory, and one that you are authorized to access from a script running in your account? I don't know what you thought was wrong with my suggestion for the location of $filedir: >my $filedir = '/home/users/lilsadam/GPS2/'; # NOT in the webroot!

I personally find it irritating to see a thread with 4-5 responses, and the person who started the thread deleted everything in the original post after the replies were posted, replacing it with something like "Never mind." The time limit on editing prevents that from occurring (for the most part).

Your URLs needed a little editing to actually test them: >http://lilsadam.cogia.net/netgps.pl http://lilsadam.cogia.net/netgps.pl?un=joe&pw=bloggs http://lilsadam.cogia.net/netgps.pl?un=joe&pw=bloggs&cds=$GPRMC,065954,V,3244.2749,S,14809.9369,E,21.6,0.0,211202,11.8,E,S*07 http://lilsadam.cogia.net/netgps.pl?un=joe&pw=bloggs http://lilsadam.cogia.net/netgps.pl?un=joe&pw=bloggs33 URLs #2 and #4 are the same URL, but your testing instructions indicate that they should generate different results for some reason. URL #1 produced this error: >GPSERROR:Incorrect password/unknown username.: URLs #2, #4, and #5 produced this error: >GPSERROR:Proc error: RCV-FN1: URL #3 produced this error: >GPSERROR:{Proc error: REM-FN1: Where the RCV-FN1 and REM-FN1 errors occur in the script, the script is trying to open a file ($filedir$filename). I would first suspect a permissions problem on whatever file "$filedir$filename" is supposed to represent, but it's also possible that either $filedir or $filename may not be specified correctly (whatever "$filedir$filename" evaluates to isn't a valid path/filename).

It was similar for me - when I started writing that post, there weren't any replies yet. After I finished it and did my first preview, there were 15 replies.

Sorry - I was just answering a question with step-by-step instructions (but no pictures).

Well, you've come to the right place then! Yes, you can design your site in DreamWeaver and have it placed where MT will use it. What they're probably talking about is MT's "Link this template to a file" feature. When you link an MT template to a file on the server, you can edit the linked file on the server, and when you rebuild your weblog, MT will read any changes in the linked file, update the template in the MT database, then write the new page to the server. In your case, what a linked template allows you to do is create or edit a template in DreamWeaver on your machine. When you are finished, you use DreamWeaver's built-in FTP to upload the new template to the server, overwriting the previously existing linked template file. Then you rebuild your weblog, and MT will read the new template file you uploaded via DreamWeaver to build the page. The first thing you'd need to do is create a directory to hold the linked template files - you don't want them in the same directory as your weblog pages. I usually create a directory for them in my MT directory (the directory where mt.cgi is located). If you plan on having more than one weblog, I'd suggest creating a separate directory for each weblog's templates - the file names get very messy and confusing if template files for several weblogs are mixed together in one directory. In your FTP program, or CPanel's File Manager, navigate to your public_html/mt directory. Create a new directory and name it "templates". Now that you have a place to store the linked template files, you need to configure MT to link a template to a file, and tell MT where the linked template file will be. Log into mt.cgi, and click on the "Templates" link for your weblog. Click the "Main Index" link to edit your main index template. In the "Link this template to a file" box, enter the server path and filename you want to use for the linked template file: >/home/cpanelName/public_html/mt/templates/main_index.tmpl The path above is the server path to the "templates" directory you created earlier (be sure to replace 'cpanelName' with your actual CPanel username), and the name "main_index.tmpl" is whatever name you want to use for the linked template file so you know what it is. I use ".tmpl" file extensions so I know that the files are templates and not true HTML files that should be served by the web server. After entering the linked template file name, click the Save button. MT will save the path and filename for the linked file in the MT database, and automatically create the "main_index.tmpl" file in the public_html/mt/templates directory. The above step will need to be repeated for each template that you want to link to a file (and thus be able to edit from DreamWeaver). I've never used DreamWeaver, so I'm not sure how you need to set it up to work with the linked template file. You may need to download the linked template file first, so you have a copy of the template locally to edit, containing both the HTML and MT tags necessary to build a weblog page. Once you have a copy of the template to work with, you should be able to edit it normally in DreamWeaver, and when you are finished, upload it to the public_html/mt/templates directory to have MT use the new template. After a linked template file has been updated, rebuild your weblog to see the changes reflected on your weblog pages. The only caveat I've heard in working with MT templates in DreamWeaver is that if you're not careful, DreamWeaver may mangle MT tags in the template, because DreamWeaver doesn't recognize them. I don't believe it would that much different for MT, but to generate "previous" and "next" links, your code would need to use MT tags in certain places so MT will insert the correct links for you. It would go into "Master Archive Index" template (although technically it's an index template, not an archive template), but it would also need to go into any true archive templates that you are using on your weblog (Category Archive, Date-Based Archive, Individual Entry Archive). You would just create another index template for your links page. You can create a link to the page by using the MTLink template tag: ><a href="<$MTLink template="Links Template"$>">My Links Page</a> ...where "Links Template" is the name of the template you created. It looks like Marie has your other questions covered.

The correct path to perl must be the first line of your script. You need to change the first line from this: >#!/usr/local/bin/perl ...to this: >#!/usr/bin/perl

Does your host allow executable scripts outside of the cgi-bin directory? If not, you'd need to place the script in the cgi-bin directory (or a subdirectory of cgi-bin).

Are the permissions on the netgps.pl script set to 0755, making it executable?

Welcome to the forums, Adam! The GPS2 folder needs to be created outside of or above your www directory. Once you've picked a location and created the directory, then you need to edit the script so $filedir contains the path of that directory. Example: >my $filedir = '/home/users/lilsadam/GPS2'; # NOT in the webroot!