chad, when posted the arrays should be available using $_POST['name'],
$_POST['position'], etc
try doing print_r($_POST['name']) to check this
i am not seeing an input type="submit" on your form...which should be there
if the user is submitting everything after filling the fields
fernando
On Tu
In "tbody",I can add or remove more "name[]","position[]","city[]","state[]"
and "zip[]" through "add" or "remove" buttons.
On "create.php" page, I expect to show all like:
1.
name
position
city
state
zip
2.
name
position
city
state
zip
3.
name
position
city
state
zip
--
I think it was called "Securing Php Applications"
-Original Message-
From: talk-boun...@lists.nyphp.org [mailto:talk-boun...@lists.nyphp.org] On
Behalf Of Chris Shiflett
Sent: Monday, January 26, 2009 3:39 PM
To: NYPHP Talk
Subject: Re: [nyphp-talk] Php off root
Hi Michele,
> Anyway, I p
Hi Michele,
Anyway, I picked up Chris Shiftlett's book "Essential Handbook on Php
Security". Nestled in the 100 page book was don't keep php in
webroot.
I hope you enjoy the book. :-)
The recommendation you're referring to is probably to reduce risk
wherever possible. For resources that
Michele,
I'm happy you found your way!
-- Elijah
On Mon, Jan 26, 2009 at 12:22 PM, Ajai Khattri wrote:
> On Mon, 26 Jan 2009, Michele Waldman wrote:
>
> > So, anyway for anyone that I caused concern for the solution for me is
> keep
> > code off webroot and in webroot just include those file.
Brent,
Thanks for the feedback, we are going to do the XML file in batches but it is
interesting to see that the memory from within the foreach never gets returned
(tested with memory_get_usage). Now there are a couple of other variables to
assume with this application. It is Drupal based so
foreach makes a copy of the array element you are processing. If the
current "value" is large, like another array, then you have 2 large
arrays. Use a for loop instead or use a reference for the value
variable:
foreach ( $array as &$value ) ...
If you are running into memory problems, you probably
On Mon, 26 Jan 2009, Brent Baisley wrote:
> I don't think you need to strip anything down. Apache/PHP/MySQL would
> run just fine on a G4 in their standard setup, just some standard
> configuration tweaking.
Im running that on a G3 (not a production server!), but to be fair, the G3
is running Li
On Mon, 26 Jan 2009, Paul A Houle wrote:
> I've tried a number of "lightweight web servers" including
> "lighthttpd" and, so far, I've always had problems when they're used
> in production systems.
Generally, lighty is great for image servers and other static resources.
Since it can hand
On Sun, 25 Jan 2009, Jesse Callaway wrote:
> Example #3 Connecting to remote php-fastcgi instances
>
> fastcgi.server = ( ".php" =>
>(( "host" => "10.0.0.2", "port" => 1030 ),
> ( "host" => "10.0.0.3", "port" => 1030 ))
> )
Yeah, Ive been using a similar setup for about a year now...
No
When working with foreach constructs do the functions and variables defined get
returned to the garbage collector on each iteration or does the foreach have to
finish execution before things can be returned to the garbage collector?
The reason that I ask is because we are generating data for Goo
On Mon, 26 Jan 2009, Michele Waldman wrote:
> So, anyway for anyone that I caused concern for the solution for me is keep
> code off webroot and in webroot just include those file. Worries over. Bad
> sys admin or no.
Yeah, generally code that doesn't need to be opened in a browser, doesn't
ne
On Mon, Jan 26, 2009 at 9:56 AM, Paul A Houle wrote:
> Jesse Callaway wrote:
>>
>> I was about to install php on a G4 I have and thought I should maybe
>> go lightweight with it. Really I'm sure it can handle Apache 2 just
>> fine, since it's just for development... but why not make it fun?
>>
>
>
Jesse Callaway wrote:
I was about to install php on a G4 I have and thought I should maybe
go lightweight with it. Really I'm sure it can handle Apache 2 just
fine, since it's just for development... but why not make it fun?
Personally I avoid off-brand web servers. Many of them have
corr
I don't think you need to strip anything down. Apache/PHP/MySQL would
run just fine on a G4 in their standard setup, just some standard
configuration tweaking.
The hardware would actually be a good setup to optimize your code,
which is where the biggest slow downs usually occur. If it runs fine
on
Guys,
I posted a while back about php dumping to the screen for God knows what
reason, the sys admin or something.
Anyway, I picked up Chris Shiftlett's book "Essential Handbook on Php
Security". Nestled in the 100 page book was don't keep php in webroot.
I can't remember the reason for that
16 matches
Mail list logo
