On Sat, Jul 12, 2008 at 8:59 PM, Bradley Giesbrecht <[EMAIL PROTECTED]> wrote:
> Add a blank live or two before 1352 and if the error is still at 1352 then
> it's a cache or the wrong file.
I actually commented out the function and rebooted the computer. it
still points to the line
1352 error even
Add a blank live or two before 1352 and if the error is still at 1352
then it's a cache or the wrong file.
BTW, I know nothing about drupal so keep that in mind. I'd be
interested in knowing what $code equals.
Add something like this at the top of the drupal_eval function to see
what the
On Sat, Jul 12, 2008 at 8:06 PM, tom lee <[EMAIL PROTECTED]> wrote:
>
> allow_url_fopen is on, but allow_url_include is off. could it be
> allow_url_include issue?
Just checked. allow_url_include is not related.
I don't understand why it still generateed the error even if I
commented out the ful
On Sat, Jul 12, 2008 at 4:56 PM, j k <[EMAIL PROTECTED]> wrote:
>> -
>
> it's trying to open a file via a url and as I recall that may be switched
> off by default in php 5.2.6.
> afaik apache 2.2.8 works just fine with php 5.2.6
On Sat, Jul 12, 2008 at 4:06 PM, tom lee <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I used apache with php and drupal.
>
> I got the following error in my web browser.
>
> warning: file_get_contents(http://abc.mywebsite.com/?prt=test)
> [function.file-get-contents]: failed to open stream: Connection
Hello,
I used apache with php and drupal.
I got the following error in my web browser.
warning: file_get_contents(http://abc.mywebsite.com/?prt=test)
[function.file-get-contents]: failed to open stream: Connection
refused in /var/www/html/includes/common.inc(1352) : eval()'d code on
line 22.
he
Struggled with this for almost 2 months and finally got it working.
And woeehh i still dont know what was wrong. May be i had wrong module
installed, downloaded the latest Apache source, complied it and that solved the
issue.
Thanks guys for your help.
Saachin Mandloi,
Manager - Technology,
ht
On Fri 11 Jul 2008, Mike Friedman wrote:
> I've got a mod_perl handler setup like so, within a vhost:
>
>
> SetHandler perl-script
> PerlResponseHandler MyApp::Dispatcher
>
>
> Under this setup, if I navigate to /myapp/foo/bar/baz, I get:
>
> PATH_INFO => /foo/bar/baz
> SCRIPT_NAM
On Fri, 2008-07-11 at 18:27 -0700, Infocom Admin wrote:
> Yes it has write pemission too...
SELinux. It's probably in enforcing mode (rather than permissive) and is
preventing you doing things you believe you can.
Try "setenforce 0" as root, and run make install again. Then to turn
SELinux back i
