On 3 Jul 2003 at 9:06, Adam Voigt wrote:
> Well spamming doesn't get them any money. I believe
> I read they use this info to transfer money from your bank
> account, after convincing you to scan your passport for
> them, or something like that.
Actually, the scam is fairly sophisticated. They as
On 2 Jul 2003 at 13:00, Mike Migurski wrote:
> You may find it easier to include, in the e-mail, a
> uniquely-generated, limited-time URL that the person can visit to
> verify that they have received the e-mail. This will remove the burden
> of having to set up a system that responds to e-mail com
I am in the process of scripting a site which requires
authentication. I've no problems with the scripts allowing folk to
register, login, logout, change password, etc. However, this morning
I've begun to work on providing some "security" in the form of
preventing someone from registering as an
On 30 Jun 2003 at 22:34, Derick Rethans wrote:
> > I disagree with you Derick. In many (most? all?) programs, the
> > reply- all function will send an email back to the list **and** one
> > to the author. This wastes bandwidth needlessly, in my opinion. I
> > receive the messages to the list and d
On 30 Jun 2003 at 21:23, Derick Rethans wrote:
> > I'm wondering why the listed "Reply To" address is not
> > "[EMAIL PROTECTED]"
> > Thing would be so much easier to just reply than cut-n-paste when
> > reply to the entire list on a subject (which is the norm).
>
> That's an evil thing, and mi
On 30 Jun 2003 at 11:20, - Edwin - wrote:
> > Warning: Error parsing /mydirectory/mysql.ini on line 4 in Unknown
> > on line 0 Array ( [host] => spore.org [uid] => myuserid [passwd] =>
> > mypassword)
> >
> > The error message still remains, though now the test confirms that
> > mysql.ini is bei
On 30 Jun 2003 at 10:25, - Edwin - wrote:
> > [mysql_info}
>
> I think you meant [mysql_info]? (Check the closing bracket.)
It is correct on the server. My fingers didn't type what my brain
told
them to for this email.
> Notice that you need to do something like this: (based on your
> example)
On 25 Jun 2003 at 16:42, Dan Joseph wrote:
> Store that file outside the docroot. That way there is no chance
> they can
> get it from the web site. I myself use an ini file that is no where
> near the docroot, and use parse_ini_file() to load the DB
> information in, and then I connect to it.
On 24 Jun 2003 at 4:33, Philip Olson wrote:
> No. (btw, be sure to quote your strings). In reading
> the table found here:
Thanks. That is a mistake I make frequently. The "good" thing about
that is that if there is an error the first thing I look for is
whether I have quoted my strings. ;-
On 23 Jun 2003 at 13:22, CPT John W. Holmes wrote:
> The first two characters are opening up a PHP block of code, so you
> get a parse error. Either disable short open tags in php.ini,
I don't have access to php.ini. Can I do this on a script by script
basis with
ini_set(short_open_tag, off)
When I include in my html
code, I get a parse error. The version is 4.1.2; phpinfo() reports
that XML support is turned on. Can anyone help with this?
Doug
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
11 matches
Mail list logo
