Hey guys,
So I haven't stuck my head here in a while. I'll give a quick update before I jump into my question. Things here are going very well. I have just moved to Boston, and started my job/internship with TechMission as I told some of you about earlier. I've been working there for about 1 & 1/2 weeks now. We run Drupal, and it turns out that as one of the "Web Developers" almost all of what I've been doing is installing Drupal modules onto our test environment, making sure they work, and then installing them onto our live environment. In addition to this, they have me doing some server administration tasks like database backups, and work in our local network, like adding a staff member to Active Directory when we get new staff, helping with the IP phone system, stuff like that. I'm really enjoying it up here so far.
So now to my question.
We're running Drupal 6.x. I noticed today on our test site as I went to manually run a cron that I got fatal errors preventing the cron to run. After doing a couple things and then refreshing the page to try again, I got a totally different fatal error. I then realized that if I just refreshed the page long enough, the fatal errors just cycled through until there were no more left, and then the cron would run.
So my question is, WHY? Why are the fatal errors showing up and then not appearing again? What's going on behind the scenes that I don't know about??
The 2nd question that I have is this:
Any opinion on whether or not opening up allow_url_fopen in php.ini would create a security hole in a production environment? I did some research on this today, because the fact that it is OFF is creating some problems with a module I am trying to install (which is Link Checker). I think I've come to the conclusion that there IS a security hole that could potentially open up if I were to turn it on. So I don't think I'm going to open it. Instead, I'm going to try to hack the module and come up with a different function or a different way of doing what it's trying to do.
As I was doing some research today on upgrading Audio module, I saw some comments from Rob on the Drupal website about it. That was kind of funny, and I was tempted to send him a message with my specific question, but I think I've got that one figured out.
What are the errors? Might just be one of the modules with a bad hook_cron.
/ * Begin Signature */
It's a strange thing about determined seekers-after-wisdom that, no matter where they happen to be, they'll always seek that wisdom which is a long way off. Wisdom is one of the few things that looks bigger the further away it is.
Hey guys,
So I haven't stuck my head here in a while. I'll give a quick update before I jump into my question. Things here are going very well. I have just moved to Boston, and started my job/internship with TechMission as I told some of you about earlier. I've been working there for about 1 & 1/2 weeks now. We run Drupal, and it turns out that as one of the "Web Developers" almost all of what I've been doing is installing Drupal modules onto our test environment, making sure they work, and then installing them onto our live environment. In addition to this, they have me doing some server administration tasks like database backups, and work in our local network, like adding a staff member to Active Directory when we get new staff, helping with the IP phone system, stuff like that. I'm really enjoying it up here so far.
So now to my question.
We're running Drupal 6.x. I noticed today on our test site as I went to manually run a cron that I got fatal errors preventing the cron to run. After doing a couple things and then refreshing the page to try again, I got a totally different fatal error. I then realized that if I just refreshed the page long enough, the fatal errors just cycled through until there were no more left, and then the cron would run.
So my question is, WHY? Why are the fatal errors showing up and then not appearing again? What's going on behind the scenes that I don't know about??
The 2nd question that I have is this:
Any opinion on whether or not opening up allow_url_fopen in php.ini would create a security hole in a production environment? I did some research on this today, because the fact that it is OFF is creating some problems with a module I am trying to install (which is Link Checker). I think I've come to the conclusion that there IS a security hole that could potentially open up if I were to turn it on. So I don't think I'm going to open it. Instead, I'm going to try to hack the module and come up with a different function or a different way of doing what it's trying to do.
As I was doing some research today on upgrading Audio module, I saw some comments from Rob on the Drupal website about it. That was kind of funny, and I was tempted to send him a message with my specific question, but I think I've got that one figured out.
Thanks guys,
David
IT consulting, Technical Support, and Web Hosting Solutions
http://www.huntsources.com - Hunting Resources