Re: [PHP] Best way to save reports, comments and suggestions welcome
Hey Rob, > > I have done very little SUM queries with time, can > you > > give me a quick example or any site where i can > find a > > few sample queries? > > This is basic MySQL so you should RTFM, and > generally should be asking > on a MySQL list :) Hehehe, true... Dont really like the MySql manual...its so much more complicated compared to the php manual. And dont really fancy joining a high traffic list like the mysql one just for a simple q like the above when there are so many experts here like you who take a moment to help guys like me out. I usually dont ask such basic q's anyway, although I admit the defination of a "basic q" is very different to many ppl here... > SELECT SUM( UNIX_TIMESTAMP( logout_time ) - > UNIX_TIMESTAMP( login_time ) > ) AS seconds FROM some_table WHERE user_id = 1; > > If you have MySQL >= 4.1.1 then you should probably > use the TIMEDIFF() > function. Got it, Thanks! Ryan -- - The faulty interface lies between the chair and the keyboard. - Creativity is great, but plagiarism is faster! - Smile, everyone loves a moron. :-) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save reports, comments and suggestions welcome
On Mon, 2006-05-29 at 08:55, Ryan A wrote: > > Regardless of how you determine the end of the > > logged in time, you > > shouldn't track all the different sums in every > > entry since that's > > redundant. You don't even need the extra data since > > the database will > > happily allow you to perform the SUMs via queries. > > I have done very little SUM queries with time, can you > give me a quick example or any site where i can find a > few sample queries? This is basic MySQL so you should RTFM, and generally should be asking on a MySQL list :) SELECT SUM( UNIX_TIMESTAMP( logout_time ) - UNIX_TIMESTAMP( login_time ) ) AS seconds FROM some_table WHERE user_id = 1; If you have MySQL >= 4.1.1 then you should probably use the TIMEDIFF() function. Cheers, Rob. -- .. | InterJinn Application Framework - http://www.interjinn.com | :: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save reports, comments and suggestions welcome
Hey Robert, > > I have to write a kind of logging script which > will keep records of how long a person used the site > and its functions, so far this is what I have come up > > with: ... > Presuming you know when they logged out or can > calculate it: > > user_id > login_time timestamp > logout_time timestamp > Your username values are probably nice and unique > but a great big waste > of space as a criteria by which to relate data. You > should associate a > unique integer value for each username. Theres an idea I didnt think about, thanks! > Regardless of how you determine the end of the > logged in time, you > shouldn't track all the different sums in every > entry since that's > redundant. You don't even need the extra data since > the database will > happily allow you to perform the SUMs via queries. I have done very little SUM queries with time, can you give me a quick example or any site where i can find a few sample queries? Thanks! Ryan -- - The faulty interface lies between the chair and the keyboard. - Creativity is great, but plagiarism is faster! - Smile, everyone loves a moron. :-) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save reports, comments and suggestions welcome
On Sun, 2006-05-28 at 18:49, Ryan A wrote: > Hi, > I have to write a kind of logging script which will > keep records of how long a person used the site and > its functions, so far this is what I have come up > with: > > login_username varchar(50) > as_guide <- You can ignore this,its for a special func > > login_time timestamp > logout_time timestamp > this_session_inlogged_time float > this_month timestamp > this_year timestamp > sum_total_time_inlogged varchar or float > > Any suggestions on changing any of the above, adding > fields or changing types? > I am not 100% sure of the timestamp type for most of > the fields. Presuming you know when they logged out or can calculate it: user_id login_time timestamp logout_time timestamp Your username values are probably nice and unique but a great big waste of space as a criteria by which to relate data. You should associate a unique integer value for each username. Regardless of how you determine the end of the logged in time, you shouldn't track all the different sums in every entry since that's redundant. You don't even need the extra data since the database will happily allow you to perform the SUMs via queries. Cheers, Rob. -- .. | InterJinn Application Framework - http://www.interjinn.com | :: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Best way to save reports, comments and suggestions welcome
Hi, I have to write a kind of logging script which will keep records of how long a person used the site and its functions, so far this is what I have come up with: login_username varchar(50) as_guide <- You can ignore this,its for a special func login_time timestamp logout_time timestamp this_session_inlogged_time float this_month timestamp this_year timestamp sum_total_time_inlogged varchar or float Any suggestions on changing any of the above, adding fields or changing types? I am not 100% sure of the timestamp type for most of the fields. Any URLs,code examples or pointers to specific parts of the manual would be appreciated too. Thanks! Ryan -- - The faulty interface lies between the chair and the keyboard. - Creativity is great, but plagiarism is faster! - Smile, everyone loves a moron. :-) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save program prefs to a file?
In larger applications, I prefer to serialize the array because it allows
you to store the data in _any_ variable, not just the pre-named variable.
For example, if your page is already using a variable named $user_settings,
you would run into problems with your solution. My solution allows you to
name the data however you want, however many times you want.
Of course, this is usually not necessary for a smaller application where you
wouldn't run into such a problem.
Sincerely,
A.J. Brown
BitNotion Technologies
[EMAIL PROTECTED]
- Original Message -
From: "Edward Vermillion" <[EMAIL PROTECTED]>
To: "A.J. Brown" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, September 27, 2005 10:48 AM
Subject: Re: [PHP] best way to save program prefs to a file?
A.J. Brown wrote:
Are you wanting the preferences to be real-time changeable? For example,
user preferences that can be modified then saved? If so, just store them
in an array, then serialize the array and save it to a file. Read the
file at every page load.
[code]
//save the settings
$user_settings['setting1'] = 'foo';
$user_settings['setting2'] = 'bar';
$fh = fopen('user_settings.dat');
$serialized = serialize($user_settings);
fwrite ($fh, $serialized, strlen($serialized));
fclose($fh);
//reload the settings
$user_settings = unserialize(file_get_contents('user_settings.dat'));
[/code]
Hope this helps.
I may be showing my ignorance here, but why bother to serialize the array?
Why not just write it out to a php file, then all you have to do is
include the file when you need it and it's ready to go?
$setingsFile = " $val)
{
$settingsFile .= "$userSettings[$key] = $val\n";
}
$settingsFile .= "\n?>";
$fh = fopen('/path/to/settingsFile.php', 'w');
fwrite($fh, $settingsFile); // with error handling of course...
fclose($fh);
Then in your script, include '/path/to/settingsFile.php'; and you're ready
to use $userSettings and any changes get written back to the file.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save program prefs to a file?
Cool...that's exactly what I was looking for!! "Torgny Bjers" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Chris wrote: >> I'd like to save some program preferences to a txt file where they can be >> recalled and updated at a later time. Basically this will be a variable >> name >> and a value. Can someone suggest a reference or method to best perform >> this >> task? >> >> Thanks >> Chris >> BTW: I do not want to use MySql. > > Write a regular Windows .ini file like: > > ; My INI-file (this is a comment line): > key = value > key2 = value2 > ; It even works with PHP constants (defines) in the ini file > key3 = E_ALL > > Reading it in is simple, use parse_ini_file(): > http://www.php.net/manual/en/function.parse-ini-file.php > > You can also keep sections in the .ini file such as: > > ; a section name uses [] > [section1] > key = value > [section2] > key = value > > To write this down is easy, just do a foreach on your associative array > and write to a string that you then save into a file if you wish to > update the values here. > > Warm Regards, > Torgny -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save program prefs to a file?
On 9/27/05, Chris <[EMAIL PROTECTED]> wrote: > I'd like to save some program preferences to a txt file where they can be > recalled and updated at a later time. Basically this will be a variable name > and a value. Can someone suggest a reference or method to best perform this > task? While learning Rubyonrails recently I discovered Yaml. It's sorta like .ini files on steroids. There's a PHP implementation available here: http://whytheluckystiff.net/syck/ And the main site is here: http://yaml.org/ -- Greg Donald Zend Certified Engineer MySQL Core Certification http://destiney.com/
Re: [PHP] best way to save program prefs to a file?
A.J. Brown wrote:
Are you wanting the preferences to be real-time changeable? For example,
user preferences that can be modified then saved? If so, just store them in
an array, then serialize the array and save it to a file. Read the file at
every page load.
[code]
//save the settings
$user_settings['setting1'] = 'foo';
$user_settings['setting2'] = 'bar';
$fh = fopen('user_settings.dat');
$serialized = serialize($user_settings);
fwrite ($fh, $serialized, strlen($serialized));
fclose($fh);
//reload the settings
$user_settings = unserialize(file_get_contents('user_settings.dat'));
[/code]
Hope this helps.
I may be showing my ignorance here, but why bother to serialize the
array? Why not just write it out to a php file, then all you have to do
is include the file when you need it and it's ready to go?
$setingsFile = " $val)
{
$settingsFile .= "$userSettings[$key] = $val\n";
}
$settingsFile .= "\n?>";
$fh = fopen('/path/to/settingsFile.php', 'w');
fwrite($fh, $settingsFile); // with error handling of course...
fclose($fh);
Then in your script, include '/path/to/settingsFile.php'; and you're
ready to use $userSettings and any changes get written back to the file.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save program prefs to a file?
Are you wanting the preferences to be real-time changeable? For example,
user preferences that can be modified then saved? If so, just store them in
an array, then serialize the array and save it to a file. Read the file at
every page load.
[code]
//save the settings
$user_settings['setting1'] = 'foo';
$user_settings['setting2'] = 'bar';
$fh = fopen('user_settings.dat');
$serialized = serialize($user_settings);
fwrite ($fh, $serialized, strlen($serialized));
fclose($fh);
//reload the settings
$user_settings = unserialize(file_get_contents('user_settings.dat'));
[/code]
Hope this helps.
--
Sincerely,
A.J. Brown
"Jay Blanchard" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> [snip]
> I'd like to save some program preferences to a txt file where they can be
> recalled and updated at a later time. Basically this will be a variable
> name
>
> and a value. Can someone suggest a reference or method to best perform
> this
> task?
> [/snip]
>
> Open a new file, save stuff to it, close the file.
> Include the file where you need the prefs.
>
> http://www.php.net/fopen
> http://www.php.net/explode
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save program prefs to a file?
Chris wrote: > I'd like to save some program preferences to a txt file where they can be > recalled and updated at a later time. Basically this will be a variable name > and a value. Can someone suggest a reference or method to best perform this > task? > > Thanks > Chris > BTW: I do not want to use MySql. Write a regular Windows .ini file like: ; My INI-file (this is a comment line): key = value key2 = value2 ; It even works with PHP constants (defines) in the ini file key3 = E_ALL Reading it in is simple, use parse_ini_file(): http://www.php.net/manual/en/function.parse-ini-file.php You can also keep sections in the .ini file such as: ; a section name uses [] [section1] key = value [section2] key = value To write this down is easy, just do a foreach on your associative array and write to a string that you then save into a file if you wish to update the values here. Warm Regards, Torgny -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] best way to save program prefs to a file?
[snip] I'd like to save some program preferences to a txt file where they can be recalled and updated at a later time. Basically this will be a variable name and a value. Can someone suggest a reference or method to best perform this task? [/snip] Open a new file, save stuff to it, close the file. Include the file where you need the prefs. http://www.php.net/fopen http://www.php.net/explode -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] best way to save program prefs to a file?
I'd like to save some program preferences to a txt file where they can be recalled and updated at a later time. Basically this will be a variable name and a value. Can someone suggest a reference or method to best perform this task? Thanks Chris BTW: I do not want to use MySql. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save preferences?
On Sun, 2004-09-26 at 10:00, Victor SpÃng Arthursson wrote: > Which is the best way to save preferences (for a site) to make them > easily accessable for changes? > > What I want is a way to save arrays and read them in again without > having to use a databaseâ > > Thankful for suggests, > > sincerely > > Victor http://www.sqlite.org/ perhaps? -- /*** * Robby Russell | Owner.Developer.Geek * PLANET ARGON | www.planetargon.com * Portland, OR | [EMAIL PROTECTED] * 503.351.4730 | blog.planetargon.com * PHP/PostgreSQL Hosting & Development / signature.asc Description: This is a digitally signed message part
Re: [PHP] Best way to save preferences?
Pahlevanzadeh Mohsen wrote: Dear,I mean that you can't read XML file in multiuser mode. Can you elaborate? And what about other files? Are they different? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save preferences?
Dear,I mean that you can't read XML file in multiuser mode. --- Marek Kilimajer <[EMAIL PROTECTED]> wrote: > Pahlevanzadeh Mohsen wrote: > > You should use XML files,But XML files will be > lock > > when you want to multiuser read it. > > It's not necessery to lock files for reading. > > > Also arrays is having overhead for your > server.Best > > way is using databses. > > Yours,Mohsen. > > --- Victor Spång Arthursson <[EMAIL PROTECTED]> > > wrote: > > > > > >>Which is the best way to save preferences (for a > >>site) to make them > >>easily accessable for changes? > > ini files, pure php (fastest), some custom format > (slowest) > > >> > >>What I want is a way to save arrays and read them > in > >>again without > >>having to use a database > >> > >>Thankful for suggests, > >> > >>sincerely > >> > >>Victor > >>-- > >>PHP General Mailing List (http://www.php.net/) > >>To unsubscribe, visit: > http://www.php.net/unsub.php > >> > >> > > > > > > > > = > > -DIGITAL SIGNATURE--- > > ///Mohsen Pahlevanzadeh > > Network administrator & programmer > > My home phone is: +98213810146 > > My email address is > > > m_pahlevanzadeh at yahoo dot com > > > My website is: http://webnegar.net > > > > > > > > > > > __ > > Do you Yahoo!? > > New and Improved Yahoo! Mail - Send 10MB messages! > > http://promotions.yahoo.com/new_mail > > > > = -DIGITAL SIGNATURE--- ///Mohsen Pahlevanzadeh Network administrator & programmer My home phone is: +98213810146 My email address is m_pahlevanzadeh at yahoo dot com My website is: http://webnegar.net ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save preferences?
On Monday 27 September 2004 01:00, Victor Spång Arthursson wrote: > Which is the best way to save preferences (for a site) to make them > easily accessable for changes? > > What I want is a way to save arrays and read them in again without > having to use a database… serialize(). Or if you want to use databases but do not want to run a full blown database server then check out sqlite. -- Jason Wong -> Gremlins Associates -> www.gremlins.biz Open Source Software Systems Integrators * Web Design & Hosting * Internet & Intranet Applications Development * -- Search the list archives before you post http://marc.theaimsgroup.com/?l=php-general -- /* Never sleep with anyone crazier than yourself -- Murphy's Laws on Sex n14 */ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save preferences?
Pahlevanzadeh Mohsen wrote: You should use XML files,But XML files will be lock when you want to multiuser read it. It's not necessery to lock files for reading. Also arrays is having overhead for your server.Best way is using databses. Yours,Mohsen. --- Victor Spång Arthursson <[EMAIL PROTECTED]> wrote: Which is the best way to save preferences (for a site) to make them easily accessable for changes? ini files, pure php (fastest), some custom format (slowest) What I want is a way to save arrays and read them in again without having to use a database… Thankful for suggests, sincerely Victor -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php = -DIGITAL SIGNATURE--- ///Mohsen Pahlevanzadeh Network administrator & programmer My home phone is: +98213810146 My email address is m_pahlevanzadeh at yahoo dot com My website is: http://webnegar.net __ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save preferences?
You should use XML files,But XML files will be lock when you want to multiuser read it. Also arrays is having overhead for your server.Best way is using databses. Yours,Mohsen. --- Victor Spång Arthursson <[EMAIL PROTECTED]> wrote: > Which is the best way to save preferences (for a > site) to make them > easily accessable for changes? > > What I want is a way to save arrays and read them in > again without > having to use a database > > Thankful for suggests, > > sincerely > > Victor > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > = -DIGITAL SIGNATURE--- ///Mohsen Pahlevanzadeh Network administrator & programmer My home phone is: +98213810146 My email address is m_pahlevanzadeh at yahoo dot com My website is: http://webnegar.net __ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Best way to save preferences?
Which is the best way to save preferences (for a site) to make them easily accessable for changes? What I want is a way to save arrays and read them in again without having to use a database… Thankful for suggests, sincerely Victor -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
Isn't it simplier to just do like when you purchase something? You also need a prove then that you have paid and are expecting the merchandise to be shipped. That is simply solved with mailing a copy plus a registration number for future reference. Should be more than enough. -- Maxim Maletsky [EMAIL PROTECTED] Petre Agenbag <[EMAIL PROTECTED]> wrote... : > Hi > I have a rather annoying problem regarding forms. > I have built an app that allows the users to fill in a rather large form > (much like a claim form) and then have the data pumped into a mysql db. > The problem is: the users want to be able to "save" their forms on their > systems as a) backup/proof that they have filled it in and b) for their > records for future use and c) the hope is that it would also allow for a > reliable method to complete the form off-line and then submit it when > online again. > > So, I'm not sure what the best way is to tackle this situation. My gutt > says it would need some kind of client stand alone app, but I wouldn't > want to go there unless I am proven beyond reasonable doubt that it is > the only way. > > The users are mostly in computer limbo, and if they had their way, they > would want to use "Word or Excel" to complete the forms, save it to > their hard drive and "click to send it away"... > > Help!, Please?! > > > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
You could use the mail() function to automatically send an email to your user. In the email could be an html page with the same form they'd filled out plus some hidden input fields which would tell you that they are updating their stored information. With this, your user gets confirmation of what was submitted, a way to edit their initial input and a record which they can keep on their own computer. Hope this helps, Hugh - Original Message - From: "Petre Agenbag" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 28, 2003 11:35 AM Subject: [PHP] best way to save form data on user side > Hi > I have a rather annoying problem regarding forms. > I have built an app that allows the users to fill in a rather large form > (much like a claim form) and then have the data pumped into a mysql db. > The problem is: the users want to be able to "save" their forms on their > systems as a) backup/proof that they have filled it in and b) for their > records for future use and c) the hope is that it would also allow for a > reliable method to complete the form off-line and then submit it when > online again. > > So, I'm not sure what the best way is to tackle this situation. My gutt > says it would need some kind of client stand alone app, but I wouldn't > want to go there unless I am proven beyond reasonable doubt that it is > the only way. > > The users are mostly in computer limbo, and if they had their way, they > would want to use "Word or Excel" to complete the forms, save it to > their hard drive and "click to send it away"... > > Help!, Please?! > > > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
on 29/01/03 6:35 AM, Petre Agenbag ([EMAIL PROTECTED]) wrote: > Hi > I have a rather annoying problem regarding forms. > I have built an app that allows the users to fill in a rather large form > (much like a claim form) and then have the data pumped into a mysql db. > The problem is: the users want to be able to "save" their forms on their > systems as a) backup/proof that they have filled it in and b) for their > records for future use and c) the hope is that it would also allow for a > reliable method to complete the form off-line and then submit it when > online again. > > So, I'm not sure what the best way is to tackle this situation. My gutt > says it would need some kind of client stand alone app, but I wouldn't > want to go there unless I am proven beyond reasonable doubt that it is > the only way. There are different issues here If they want to save a half-completed form, you *could* save that data server side in either a table, temporary table, or file, and have them log-in to continue using it. I have done this many times. You could also save the data client-side with cookies, but there's no guarantee that cookies will work on a specific client. If they want back-up/proof of doing it, then they can print the browser screen as they fill it in, AND, you can give them a confirmation page which prints all the form values back to the browser as a printable HTML page which they can either print or save as TEXT or HTML. Writing something that works offline for completion online later sounds like you're trying to make the web do something it wasn't designed for. The only solution I can think of is client-side javascript saving the form information as a browser cookie, but there's no way I'd bother, because it would require the user to have both javascript and cookies enabled, and I think there's also issues with the issuing domain of the cookie. > The users are mostly in computer limbo, and if they had their way, they > would want to use "Word or Excel" to complete the forms, save it to > their hard drive and "click to send it away"... You can create a form inside a PDF document, and it can POST the completed data to a URL. So they could complete the form offline, print it, whatever, then connect, and hit submit. It would open a browser window with a URL like http://yourdomain.com/parseThePDFForm.php and then you would have your submitted data. Whilst not as a elegant, they COULD fill in an excel file, and upload it via a browser. Same with word. I'm not sure if wither excel or word has any method of POSTing data. With all these client-side options, there's zero hope of getting them to correct missing fields though :) Decide if this is something you want to achieve on the web, or offline. If on the web, keep it basic, with perhaps a save to server option and a printable thankyou/proof page. If offline, I think PDF forms are the best of a bad bunch. Justin French -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
I agree on leveraging your position to guide this thing. Here you've added the requirement of being able to revisit the data in a year. Why not simply have them fill out the form, put it in the database and then use another page with queries to draw the data into a similar template and change it as needed? Simple forms should handle this just fine, and you can require passwords to the data. As far as filling it out online, let them pull up the form, fill it out and reconnect, then press submit. Wouldn't this cover what you want? Petre Agenbag <[EMAIL PROTECTED]To: [EMAIL PROTECTED] za> cc: [EMAIL PROTECTED] Subject: Re: [PHP] best way to save form data on user side 01/28/2003 03:17 PM Hi Chris On Tue, 2003-01-28 at 22:09, Chris Shiflett wrote: > --- Petre Agenbag <[EMAIL PROTECTED]> wrote: > > I have a rather annoying problem regarding forms. > > I have built an app that allows the users to fill > > in a rather large form (much like a claim form) > > and then have the data pumped into a mysql db. > > The problem is: the users want to be able to > > "save" their forms on their systems as a) > > backup/proof that they have filled it in and b) > > for their records for future use and c) the hope > > is that it would also allow for a reliable method > > to complete the form off-line and then submit it > > when online again. > > Well, this sounds like a bad idea in general, but if you > have no choice in the matter, I suppose cookies can fulfill > the need. > > Anything you implement like this is going to lessen the > security of the data, because rather than the client > sending it to you once, you are going to expose it over the > Internet several times. If this risk is acceptable for > whatever reason, then cookies are probably no less secure > for this data than anything else. > > Normally, I would highly recommend *not* storing client > data on cookies, because that opens you up to several types > of attacks, but you can accomplish what you want to do with > this method. Only "punish" those who want this feature by > setting these cookies only for those who choose to save > this data locally. You could help the situation by > encrypting the data in your cookies, so that only > presentation attacks are a concern, but your users wouldn't > be able to easily look at their data as verification of > anything. > > My recommendation is to leverage your position as the > technical expert to advise a more proper solution, one that > you agree to, not them. They should not be consulted > regarding application design unless they have experience > with it. Rather, they should be describing their needs and > let you (or the technical lead / project manager) do the > technical design. This is exactly what I'm looking to do; but my problem remains: I don't know what the best solution is. The problem is clear: the users actually need an electronic copy of the data they submit; they must revisit certain issues annually, and would need to access the data they submitted the previous year; either for review purposes, or to make the new submission a speedy matter of simply changing the details that are different from last year. It's much like a normal office scenario: each person works on Word docs that need to be shared with others, yet needs to be editable and must be saved etc, BUT the difference here is that the data of all the collective sources must be entered into a central db. So the "non technical" solution would be for the users to do the forms in "word", then fax it to the central office, where you have a temp type the data into the db... we can't have that now... Any ideas? PS, I don't think cookies are
Re: [PHP] best way to save form data on user side
On Wednesday 29 January 2003 04:17, Petre Agenbag wrote: > > > "save" their forms on their systems as a) > > > backup/proof that they have filled it in and b) > > > for their records for future use and c) the hope > > > is that it would also allow for a reliable method > > > to complete the form off-line and then submit it > > > when online again. > This is exactly what I'm looking to do; but my problem remains: I don't > know what the best solution is. > The problem is clear: the users actually need an electronic copy of the > data they submit; they must revisit certain issues annually, and would > need to access the data they submitted the previous year; either for > review purposes, or to make the new submission a speedy matter of simply > changing the details that are different from last year. > It's much like a normal office scenario: each person works on Word docs > that need to be shared with others, yet needs to be editable and must be > saved etc, BUT the difference here is that the data of all the > collective sources must be entered into a central db. So the "non > technical" solution would be for the users to do the forms in "word", > then fax it to the central office, where you have a temp type the data > into the db... we can't have that now... > Any ideas? > > PS, I don't think cookies are going to do this. Remember, the user needs > to be able to access and re-submit the form at any stage. As has already been pointed out, saving the form data on the user's computer is a _bad_ idea and provides no assurance to either party. There is no way to prove that the data saved is what the user submitted. So to satisfy (a), you can do this: after the user has submitted the data, write them out to a textfile and GPG/PGP sign it, then let the user download that signed file. You can do something similar using md5() as well (don't forget to add a "secret"). -- Jason Wong -> Gremlins Associates -> www.gremlins.biz Open Source Software Systems Integrators * Web Design & Hosting * Internet & Intranet Applications Development * /* Riches cover a multitude of woes. -- Menander */ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] best way to save form data on user side
Hi Why don't you take the form in many smaller parts, save them away as each part is completed, allowing the user to go back and forth between the parts. This would give the advantage of securing the data which as already been submitted. You can then give other functions to review in one page (for printing off) or copying to another form which could be used for next years data Regards Adam White -Original Message- From: Petre Agenbag [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 20:17 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [PHP] best way to save form data on user side Hi Chris On Tue, 2003-01-28 at 22:09, Chris Shiflett wrote: > --- Petre Agenbag <[EMAIL PROTECTED]> wrote: > > I have a rather annoying problem regarding forms. > > I have built an app that allows the users to fill > > in a rather large form (much like a claim form) > > and then have the data pumped into a mysql db. > > The problem is: the users want to be able to > > "save" their forms on their systems as a) > > backup/proof that they have filled it in and b) > > for their records for future use and c) the hope > > is that it would also allow for a reliable method > > to complete the form off-line and then submit it > > when online again. > > Well, this sounds like a bad idea in general, but if you > have no choice in the matter, I suppose cookies can fulfill > the need. > > Anything you implement like this is going to lessen the > security of the data, because rather than the client > sending it to you once, you are going to expose it over the > Internet several times. If this risk is acceptable for > whatever reason, then cookies are probably no less secure > for this data than anything else. > > Normally, I would highly recommend *not* storing client > data on cookies, because that opens you up to several types > of attacks, but you can accomplish what you want to do with > this method. Only "punish" those who want this feature by > setting these cookies only for those who choose to save > this data locally. You could help the situation by > encrypting the data in your cookies, so that only > presentation attacks are a concern, but your users wouldn't > be able to easily look at their data as verification of > anything. > > My recommendation is to leverage your position as the > technical expert to advise a more proper solution, one that > you agree to, not them. They should not be consulted > regarding application design unless they have experience > with it. Rather, they should be describing their needs and > let you (or the technical lead / project manager) do the > technical design. This is exactly what I'm looking to do; but my problem remains: I don't know what the best solution is. The problem is clear: the users actually need an electronic copy of the data they submit; they must revisit certain issues annually, and would need to access the data they submitted the previous year; either for review purposes, or to make the new submission a speedy matter of simply changing the details that are different from last year. It's much like a normal office scenario: each person works on Word docs that need to be shared with others, yet needs to be editable and must be saved etc, BUT the difference here is that the data of all the collective sources must be entered into a central db. So the "non technical" solution would be for the users to do the forms in "word", then fax it to the central office, where you have a temp type the data into the db... we can't have that now... Any ideas? PS, I don't think cookies are going to do this. Remember, the user needs to be able to access and re-submit the form at any stage. > > Good luck to you. > > Chris -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
> On Tue, 2003-01-28 at 22:09, Chris Shiflett wrote: > > --- Petre Agenbag <[EMAIL PROTECTED]> wrote: > > > I have a rather annoying problem regarding forms. > > > I have built an app that allows the users to fill > > > in a rather large form (much like a claim form) > > > and then have the data pumped into a mysql db. > > > The problem is: the users want to be able to > > > "save" their forms on their systems as a) > > > backup/proof that they have filled it in and b) > > > for their records for future use and c) the hope > > > is that it would also allow for a reliable method > > > to complete the form off-line and then submit it > > > when online again. > > > > Well, this sounds like a bad idea in general, but if you > > have no choice in the matter, I suppose cookies can fulfill > > the need. > > > > Anything you implement like this is going to lessen the > > security of the data, because rather than the client > > sending it to you once, you are going to expose it over the > > Internet several times. If this risk is acceptable for > > whatever reason, then cookies are probably no less secure > > for this data than anything else. > > > > Normally, I would highly recommend *not* storing client > > data on cookies, because that opens you up to several types > > of attacks, but you can accomplish what you want to do with > > this method. Only "punish" those who want this feature by > > setting these cookies only for those who choose to save > > this data locally. You could help the situation by > > encrypting the data in your cookies, so that only > > presentation attacks are a concern, but your users wouldn't > > be able to easily look at their data as verification of > > anything. > > > > My recommendation is to leverage your position as the > > technical expert to advise a more proper solution, one that > > you agree to, not them. They should not be consulted > > regarding application design unless they have experience > > with it. Rather, they should be describing their needs and > > let you (or the technical lead / project manager) do the > > technical design. > This is exactly what I'm looking to do; but my problem remains: I don't > know what the best solution is. > The problem is clear: the users actually need an electronic copy of the > data they submit; they must revisit certain issues annually, and would > need to access the data they submitted the previous year; either for > review purposes, or to make the new submission a speedy matter of simply > changing the details that are different from last year. > It's much like a normal office scenario: each person works on Word docs > that need to be shared with others, yet needs to be editable and must be > saved etc, BUT the difference here is that the data of all the > collective sources must be entered into a central db. So the "non > technical" solution would be for the users to do the forms in "word", > then fax it to the central office, where you have a temp type the data > into the db... we can't have that now... > Any ideas? Do they really have to be able to do this "offline"? You've got the data in the database, why not just program a feature that lets you go in and edit data? Or copy one report to submit as a new one? Wouldn't that be a better solution than some system where you copy everything to the user's computer? ---John Holmes... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
--- Petre Agenbag <[EMAIL PROTECTED]> wrote: > This is exactly what I'm looking to do; but my problem > remains: I don't know what the best solution is. The > problem is clear: the users actually need an electronic > copy of the data they submit; they must revisit certain > issues annually, and would need to access the data they > submitted the previous year; either for review purposes, > or to make the new submission a speedy matter of simply > changing the details that are different from last year. In this case, it sounds like you need to just keep this data on the server in your database like you are already doing, then you simply provide another Web application that uses the same database and allows them to search, modify (?), and display the data for printing. You can generate reports, graphs, and all sorts of things that they will appreciate. Don't restrict yourself to their line of thinking. :-) > It's much like a normal office scenario: each person > works on Word docs that need to be shared with others, > yet needs to be editable and must be saved etc, BUT the > difference here is that the data of all the collective > sources must be entered into a central db. So the "non > technical" solution would be for the users to do the > forms in "word", then fax it to the central office, > where you have a temp type the data into the db... we > can't have that now... The solution is for the users to "do the forms" in a Web application that you build, and your Web application stores the data in the database. Forget about data entry personnel. Chris -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
Hi Chris On Tue, 2003-01-28 at 22:09, Chris Shiflett wrote: > --- Petre Agenbag <[EMAIL PROTECTED]> wrote: > > I have a rather annoying problem regarding forms. > > I have built an app that allows the users to fill > > in a rather large form (much like a claim form) > > and then have the data pumped into a mysql db. > > The problem is: the users want to be able to > > "save" their forms on their systems as a) > > backup/proof that they have filled it in and b) > > for their records for future use and c) the hope > > is that it would also allow for a reliable method > > to complete the form off-line and then submit it > > when online again. > > Well, this sounds like a bad idea in general, but if you > have no choice in the matter, I suppose cookies can fulfill > the need. > > Anything you implement like this is going to lessen the > security of the data, because rather than the client > sending it to you once, you are going to expose it over the > Internet several times. If this risk is acceptable for > whatever reason, then cookies are probably no less secure > for this data than anything else. > > Normally, I would highly recommend *not* storing client > data on cookies, because that opens you up to several types > of attacks, but you can accomplish what you want to do with > this method. Only "punish" those who want this feature by > setting these cookies only for those who choose to save > this data locally. You could help the situation by > encrypting the data in your cookies, so that only > presentation attacks are a concern, but your users wouldn't > be able to easily look at their data as verification of > anything. > > My recommendation is to leverage your position as the > technical expert to advise a more proper solution, one that > you agree to, not them. They should not be consulted > regarding application design unless they have experience > with it. Rather, they should be describing their needs and > let you (or the technical lead / project manager) do the > technical design. This is exactly what I'm looking to do; but my problem remains: I don't know what the best solution is. The problem is clear: the users actually need an electronic copy of the data they submit; they must revisit certain issues annually, and would need to access the data they submitted the previous year; either for review purposes, or to make the new submission a speedy matter of simply changing the details that are different from last year. It's much like a normal office scenario: each person works on Word docs that need to be shared with others, yet needs to be editable and must be saved etc, BUT the difference here is that the data of all the collective sources must be entered into a central db. So the "non technical" solution would be for the users to do the forms in "word", then fax it to the central office, where you have a temp type the data into the db... we can't have that now... Any ideas? PS, I don't think cookies are going to do this. Remember, the user needs to be able to access and re-submit the form at any stage. > > Good luck to you. > > Chris -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
--- Petre Agenbag <[EMAIL PROTECTED]> wrote: > I have a rather annoying problem regarding forms. > I have built an app that allows the users to fill > in a rather large form (much like a claim form) > and then have the data pumped into a mysql db. > The problem is: the users want to be able to > "save" their forms on their systems as a) > backup/proof that they have filled it in and b) > for their records for future use and c) the hope > is that it would also allow for a reliable method > to complete the form off-line and then submit it > when online again. Well, this sounds like a bad idea in general, but if you have no choice in the matter, I suppose cookies can fulfill the need. Anything you implement like this is going to lessen the security of the data, because rather than the client sending it to you once, you are going to expose it over the Internet several times. If this risk is acceptable for whatever reason, then cookies are probably no less secure for this data than anything else. Normally, I would highly recommend *not* storing client data on cookies, because that opens you up to several types of attacks, but you can accomplish what you want to do with this method. Only "punish" those who want this feature by setting these cookies only for those who choose to save this data locally. You could help the situation by encrypting the data in your cookies, so that only presentation attacks are a concern, but your users wouldn't be able to easily look at their data as verification of anything. My recommendation is to leverage your position as the technical expert to advise a more proper solution, one that you agree to, not them. They should not be consulted regarding application design unless they have experience with it. Rather, they should be describing their needs and let you (or the technical lead / project manager) do the technical design. Good luck to you. Chris -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] best way to save form data on user side
> I have a rather annoying problem regarding forms. > I have built an app that allows the users to fill in a rather large form > (much like a claim form) and then have the data pumped into a mysql db. > The problem is: the users want to be able to "save" their forms on their > systems as a) backup/proof that they have filled it in and b) for their > records for future use and c) the hope is that it would also allow for a > reliable method to complete the form off-line and then submit it when > online again. Saving the form would be useless because how would you ever know if they really submitted it or not? It seems like the easiest thing to do would be to show them a "confirmation" page that says "your claim has been accepted" and here is the data you submitted. "Save or print this page for your records" like you see on many other systems. Would that work? I guess it wouldn't do anything for option C above, but that option is always present unless you're using some kind of timeout feature? ---John Holmes... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] best way to save form data on user side
Hi Bryan Thanks for the suggestions. Can you elaborate on the pdf option? Wouldn't that mean the users would need a copy of adobe acrobat writer? On Tue, 2003-01-28 at 21:53, Bryan Brannigan wrote: > 3 choices as I see it.. > > a) create a PDF for download > b) let the users create the form in Excel and then figure out a way to > import that into your database using a webapp > c) client side app :( > > > -Original Message- > > From: Petre Agenbag [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, January 28, 2003 2:35 PM > > To: [EMAIL PROTECTED] > > Subject: [PHP] best way to save form data on user side > > > > > > Hi > > I have a rather annoying problem regarding forms. > > I have built an app that allows the users to fill in a rather > > large form > > (much like a claim form) and then have the data pumped into a > > mysql db. > > The problem is: the users want to be able to "save" their > > forms on their > > systems as a) backup/proof that they have filled it in and b) > > for their > > records for future use and c) the hope is that it would also > > allow for a > > reliable method to complete the form off-line and then submit it when > > online again. > > > > So, I'm not sure what the best way is to tackle this > > situation. My gutt > > says it would need some kind of client stand alone app, but I wouldn't > > want to go there unless I am proven beyond reasonable doubt that it is > > the only way. > > > > The users are mostly in computer limbo, and if they had their > > way, they > > would want to use "Word or Excel" to complete the forms, save it to > > their hard drive and "click to send it away"... > > > > Help!, Please?! > > > > > > > > > > > > > > -- > > PHP General Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] best way to save form data on user side
Hi I have a rather annoying problem regarding forms. I have built an app that allows the users to fill in a rather large form (much like a claim form) and then have the data pumped into a mysql db. The problem is: the users want to be able to "save" their forms on their systems as a) backup/proof that they have filled it in and b) for their records for future use and c) the hope is that it would also allow for a reliable method to complete the form off-line and then submit it when online again. So, I'm not sure what the best way is to tackle this situation. My gutt says it would need some kind of client stand alone app, but I wouldn't want to go there unless I am proven beyond reasonable doubt that it is the only way. The users are mostly in computer limbo, and if they had their way, they would want to use "Word or Excel" to complete the forms, save it to their hard drive and "click to send it away"... Help!, Please?! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best way to save?
You can wrap some output buffering around your PHP script. Then flush the buffer at the end to a variable and write it to a .html file. Full details in the manual, I'm sure... ---John Holmes... - Original Message - From: "Shane" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 01, 2002 6:48 PM Subject: [PHP] Best way to save? Besides using fOpen to save the output of a script to a file, What would be your best recommendation for a way to save the output of a PHP script to an HTML doc. Images will be included. Thanks gang. - NorthBayShane -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Best way to save?
Besides using fOpen to save the output of a script to a file, What would be your best recommendation for a way to save the output of a PHP script to an HTML doc. Images will be included. Thanks gang. - NorthBayShane -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
