If I just hit 'Reply' I'll send my reply to the individual who created the
message. If I hit 'Reply All' my reply will be sent to: Govinda <
govinda.webdnat...@gmail.com>, PHP-General List
and the creator of the message.
Neither option seems correct. What's up with that?
Thanks
As I use outlook, I just hit "Reply to Group.
--
João Cândido de Souza Neto
"Sam Smith" escreveu na mensagem
news:aanlktikarnvhn-gzexe8qedngeewgqqgs7cpchzav...@mail.gmail.com...
> If I just hit 'Reply' I'll send my reply to the individual who created the
> message. If I hit 'Reply All' my re
On Thu, Dec 16, 2010 at 06:44, Sam Smith wrote:
> If I just hit 'Reply' I'll send my reply to the individual who created the
> message. If I hit 'Reply All' my reply will be sent to: Govinda <
> govinda.webdnat...@gmail.com>, PHP-General List
> and the creator of the message.
>
> Neither option s
The PHP development team would like to announce the immediate
availability of PHP 5.2.16. This release marks the end of support for
PHP 5.2. All users of PHP 5.2 are encouraged to upgrade to PHP 5.3.
This release focuses on addressing a regression in open_basedir
implementation introduced in 5.2.1
Couldn't we just have a reply-to address for the list in the header of the
email? So all a fella had to do was hit reply, and it would work?
This is how the Apache and the MySQL list works. The PHP list is the only list
that I have to manually edit my reply every time.
For example, I hit reply
[snip]
Couldn't we just have a reply-to address for the list in the header of
the email? So all a fella had to do was hit reply, and it would work?
This is how the Apache and the MySQL list works. The PHP list is the
only list that I have to manually edit my reply every time.
For example, I hit r
On Thu, Dec 16, 2010 at 09:19, Nicholas Kell wrote:
>
> Couldn't we just have a reply-to address for the list in the header of the
> email? So all a fella had to do was hit reply, and it would work?
The easiest (and most accurate) answer: no.
> This is how the Apache and the MySQL list work
On Dec 16, 2010, at 8:26 AM, Daniel Brown wrote:
> On Thu, Dec 16, 2010 at 09:19, Nicholas Kell wrote:
>>
>> Couldn't we just have a reply-to address for the list in the header of the
>> email? So all a fella had to do was hit reply, and it would work?
>
>The easiest (and most accurate) a
On Thu, Dec 16, 2010 at 08:19:52AM -0600, Nicholas Kell wrote:
>
> Couldn't we just have a reply-to address for the list in the header of
> the email? So all a fella had to do was hit reply, and it would work?
>
> This is how the Apache and the MySQL list works. The PHP list is the
> only list t
On Dec 16, 2010, at 9:28 AM, Paul M Foster wrote:
> On Thu, Dec 16, 2010 at 08:19:52AM -0600, Nicholas Kell wrote:
>
>>
>> Couldn't we just have a reply-to address for the list in the header of
>> the email? So all a fella had to do was hit reply, and it would work?
>>
>> This is how the Apach
Let me give a formal apology to the list, for unscrewing the cap off
the can of worms.
NIcholas, just so you know you are appreciated for asking the Q in the
first place:
..some of us are new here.. or only lurk enough to catch some of the
threads... and so I was also missing some of the su
On Thursday 16 December 2010,
Sam Smith wrote:
> If I just hit 'Reply' I'll send my reply to the individual who created
> the message. If I hit 'Reply All' my reply will be sent to: Govinda <
> govinda.webdnat...@gmail.com>, PHP-General List
> and the creator of the message.
>
> Neither option
On Thu, Dec 16, 2010 at 8:09 AM, Daniel Molina Wegener wrote:
> If your MUA (or email client) is smart enough, it should have at least
>
> "Reply", "Reply to Sender", "Reply to All" and "Reply to Mailing List".
>
To which my client adds "Reply to /dev/null", "Reply to Those Who Actually
Care", a
[snip]
To which my client adds "Reply to /dev/null", "Reply to Those Who
Actually
Care", and "Reply to Al Gore". It's much smarter than the average MUA.
[/snip]
It could be argued that replying to Al Gore might not be all that smart.
--
PHP General Mailing List (http://www.php.net/)
To unsubscrib
I'm in the process of migrating customer websites off an old legacy
server that's pushing EOL, and starting to show hardware failures.
One site is throwing errors on what, so far as I can tell, should be
perfectly working code.
The original code works fine on both CentOS 3 (PHP 4.3.2) and Cen
> -Original Message-
> From: Kris Deugau [mailto:kdeu...@vianet.ca]
> Sent: Thursday, December 16, 2010 11:57 AM
> To: php-general@lists.php.net
> Subject: [PHP] String passed to object constructor turning into an
instance of
> that object?
>
> I'm in the process of migrating customer webs
Tommy Pham wrote:
class SelectBoxOption extends Tag {
function SelectBoxOption($name, $value, $selected=false) {
parent::Tag("option", $name);
$this->addAttribute("value", $value);
if($selected) {
$this->addAttribute("selected", '', false);
}
if ($name
On Thu, Dec 16, 2010 at 2:29 PM, Kris Deugau wrote:
> Tommy Pham wrote:
>
>> class SelectBoxOption extends Tag {
>>> function SelectBoxOption($name, $value, $selected=false) {
>>> parent::Tag("option", $name);
>>> $this->addAttribute("value", $value);
>>> if($selected) {
>
Nathan Nobbe wrote:
Why not test for the type of $name at each point of interest in the
SelectBoxOption
constructor? If you're passing a string value to the constructor it almost
has to be getting changed by the Tag constructor, right ?
class SelectBoxOption extends Tag {
function SelectBo
On Thu, Dec 16, 2010 at 3:21 PM, Kris Deugau wrote:
> Nathan Nobbe wrote:
>
>> Why not test for the type of $name at each point of interest in the
>> SelectBoxOption
>> constructor? If you're passing a string value to the constructor it
>> almost
>> has to be getting changed by the Tag construct
It's acting as if Tag's constructor a) declares $name as a reference using
&$name, and b) is assigning itself ($this) to $name for some (probably bad)
reason. That's the only way I can see that $name inside SelectBoxOption's
constructor could change from a string to an object.
A peek at Tag's cons
Nathan Nobbe wrote:
probly something screwy going on w/ the old style of naming constructors. 2
things,
1. can you post the Tag constructor as it reads now?
function Tag($tag='', $tagContent='') {
$this->tagContent = $tagContent;
$this->tag = $tag;
$this->showEndTag = false;
$this->a
On Thu, Dec 16, 2010 at 4:04 PM, Kris Deugau wrote:
> Nathan Nobbe wrote:
>
>> probly something screwy going on w/ the old style of naming constructors.
>> 2
>> things,
>>
>> 1. can you post the Tag constructor as it reads now?
>>
>
> function Tag($tag='', $tagContent='') {
> $this->tagContent
I've never used the old-style constructors, but perhaps the semantics of
"parent::" changed and you need to instead use "$this->" as in
$this->Tag("option", $name);
That's a total guess. I don't have 5.2 handy to try it out, but both work in
5.3 using a simple example. Can you post the constr
According to the manual page for setAccessible() [1] the feature is
available with 5.3.2, and I'm running
5.3.2-1ubuntu4.5 with Suhosin-Patch (cli) (built: Sep 17 2010 13:49:46)
so I should be good to go. However, even the simplest test to make a
protected or private method accessible fails.
On Thu, Dec 16, 2010 at 3:21 PM, Kris Deugau wrote:
> Nathan Nobbe wrote:
>
>> Why not test for the type of $name at each point of interest in the
>> SelectBoxOption
>> constructor? If you're passing a string value to the constructor it
>> almost
>> has to be getting changed by the Tag construct
On Thu, Dec 16, 2010 at 6:37 PM, David Harkness
wrote:
> According to the manual page for setAccessible() [1] the feature is
> available with 5.3.2, and I'm running
>
>5.3.2-1ubuntu4.5 with Suhosin-Patch (cli) (built: Sep 17 2010 13:49:46)
>
> so I should be good to go. However, even the simpl
It seems like there are several questions emerging, but ...
Try echoing your query to the page by putting echo $query in your code before
you call mysql, then copy it and run it in phpmyadmin. If it runs then you know
your problem is somewhere else like the connection. This can really help you
On Thu, 16 Dec 2010 00:13:31 +0700, "Daniel P. Brown"
wrote:
Well, phpinfo() does, by default, divulge some things that could
be considered security concerns --- particularly in poorly-managed
environments. Primarily, this is by giving a synopsis of versions and
paths of software, but so
29 matches
Mail list logo
