Jump to content

ajetrumpet

Members
  • Content Count

    152
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ajetrumpet

  • Rank
    Advanced Member
  • Birthday 05/26/1980

Profile Information

  • Gender
    Male
  • Location
    Iowa City, IA, USA
  • Age
    39

Recent Profile Visitors

676 profile views
  1. req, I just want to make sure that these 2 things are not related. it doesn't make sense that they would be. Are the "allowed PHP modules" on a shared server related at all to the HTTPD software implementations listed here? https://en.wikipedia.org/wiki/Httpd . Your instruction guide says it is HTTPD. considering that HTTP is a protocol and PHP is a language, I'm thinking this is completely irrelevant. from GoDaddy: https://techmipro.com/php-mods-on-godaddy-shared-hosting/
  2. are you talking about SSH? apparently programs like PUTTY can be used for this, purpose.
  3. Req, In that resource you pointed me to, it looks like everything that has to be done is being done through the command line and the appropriate statements in it. is that correct? is this a common way to do things when working with a server directly?
  4. this might be exactly what I'm looking for, mac! thanks! so the rest of you guys....I have changed all of the files on my website to this: <?php include("relative_path_pointer/r/pagevisit.php"); ?> so essentially what I did for a file that is nested ''x'' dirs deep, to capture traffic, is THIS: <?php include("../../../r/pagevisit.php"); ?> there's nothing wrong with that, is there you guys? that isn't a security risk, is it? thanks!
  5. I appreciate it, cyberR.. I will bookmark the manual.
  6. that's always a good idea, ian. good for you.
  7. did you check the spam folder? additionally, perhaps you need more lines of REQUIRE() code, like in my script? don't quote me, ian, I'm no PHP expert.
  8. ian, I worked with a veteran on this very issue for 3 days a long time ago. we found out that the package I downloaded from github was coded incorrectly. he had to use another method to put the body of the HTML message together. can you possibly get anything from this script of mine? https://drive.google.com/file/d/1Cj8RIDPOUe8hWUBUQjtjGUjKgQG2u3t_/view?usp=sharing the new code from him, that he wrote to solve the problem of me not getting the message and/or the message coming incorrectly was this portion: $temp_HTML = "<!DOCTYPE html> <html> <head> <title>Website Form Submission</title> </head> <body> <p>$email_body</p> </body> </html>"; he also had to add a few other lines of REQUIRE() function code.
  9. hey you guys, I have a bunch of files on a server and I had to populate each one with this code: <?php include("https://www.domain.com/r/pagevisit.php"); ?> however, I'm getting an error, which I understand: This gentleman on SO suggests that doing this is not the right way, and will always throw the error: https://stackoverflow.com/a/23285648 This site is getting quite large now, and I might just have to throw the content of all the files into a DB and pull it out when each page is requested. however, for now everything is just PHP files sitting on the server. so the question => is there anyway I can keep the include() code I currently have on each page, or does each file have to have it changed to the relative URI path? if I can keep it the way it is, where is the configs to change it? I might not even have access to it since this is shared hosting. thanks! Adam
  10. I won't when i get your solution implemented. I currently have a pw on the root via the method I just showed you, using goDaddy's tool in that image. but that doesn't work, as stated.
  11. I *do* have the option to password protect different directories, however I tried this long ago and it doesn't work because if I protect the root and then protect a subdir underneath that root with another pw, the pw for the root is used for both. the pw for root takes precedence over every other one. thus, goDaddy's tool can't do this. see attached image, or here: https://drive.google.com/file/d/1RF8KnyP5tKzdG-R0Axrr116E-L-iYeFr/view?usp=sharing
  12. that looks like something similar to what I need, req. however, a part of that page says this: this website is hosted with GoDaddy, and I have no idea if I have access to that dir or those appropriate files. this is on a shared server, and goDaddy tells me that access to deep level config files under that kind of hosting account is not possible. the root dir on this website, per an FTP client, is: public_html however, there *is* a directory underneath that root called: .htpasswds the apache version they have is 2.4.33 it looks like we're on the right track then here, no?
  13. YES. sorry for the long winded answer, requinix. I know you tech experts like it simple in the manner of "question-answer". 😃
  14. well here's what it is, requinix.... .....I have a site that has "index.php" files inside each subdir. so the architecture looks similar to this: www.domain.com => www.domain.com/concept1/program1/ => www.domain.com/concept1/program1/advanced => www.domain.com/concept1/program1/tutorials => www.domain.com/concept2 ....(same as above) so....someone will contact me that is trained in program1 and want to learn more about that program. I would then want to give them access to these dirs ONLY: www.domain.com/concept1/program1 www.domain.com/concept1/program1/advanced www.domain.com/concept1/tutorials but I would *not* want that same user to have access to these dirs: www.domain.com www.domain.com/concept2 so....is this even possible with PHP/MYSQL?? in general, the password given to this examples user I'm referring to in this post would be the exact same password given to anyone that wanted to learn about program1. thus, it would *not* be a different password for each person. but rather, a different password for each *dir* and its associated *subdirs*. thanks requinix!
  15. req, I'm sorry it took forever for me to get back to you on this. to answer you....this page will be looked at by many people. I need a different UN and PASS for each directory. "subdirectory", that is, that, is each nested underneath the root site name: e.g. => www.domain.com I'm assuming the simple-stupid apache method for this would not be appropriate, correct? this is a bit more complex than "stupid" methods....thanks.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.