Page 1 of 1
Making it "Stick"
Posted: Thu Jul 25, 2002 6:58 pm
by Rookie
(Eyes bugged out from to much PHP surfing)
Hi,
I don't think I'll ever be a PHP junkie (unless you "guys" can convert me), but I would greatly appreciate a little assistance.
I've just started looking into PHP and think it might make a good language for an online website content editor I want to build for interactive client use on my site.
I've started the editor and have the form boxes set-up and the PHP pages functioning so that when the content from the editable areas is submitted, it gets transferred to the corresponding PHP page. My question is:
After the content gets submitted and is on display online in its editted format, how do I get the content to "stick" when a user attempts to re-edit a section and on subsequent visits to the site for multiple editing sessions?
I just have the first couple of pages active as I didn't want to waste time if I'm on the wrong track, but you can view what little there is at:
http://www.burnabywebdesign.com/editor/enter.html
Am I just missing a few snips of code or do I need a whole different set-up to make this thing fly?
Any suggestions how to rectify this or ideas for an alternate set-up would be greatly appreciated.
Thanks
Posted: Thu Jul 25, 2002 9:17 pm
by RandomEngy
First, don't make anything full screen. It's very rude to your users.
Secondly, you want to look into databases (mysql) for keeping data permanently, and sessions in PHP for keeping data for however long the user keeps the browser open.
If you haven't done any database work at this point, you have a ways to go before you get things running smoothly.
Posted: Fri Jul 26, 2002 12:46 pm
by Rookie
Thanks for the info "R.E." I guess its back to the drawing board.
As for the full-screen bit:
I agree that it's rude if applied to a main window, but applied to a child window it is often beneficial for those with small monitors in the case of frames (such as my content editor uses) or small font Flash presentations. When the user exits the full-sized child they are free to navigate through the parent window.
Posted: Fri Jul 26, 2002 12:50 pm
by RandomEngy
Well, you might give an option of running something full screen, but a lot of people have a high resolution and don't need the extra space. When you automatically pop up a full screen window, the user loses all of their familiar naviagation bars, (along with that their ability to print the page, look at the source, go somewhere else) and basically many people just can't do anything with the browser until that full-screen window is gone.
You may get a little extra space, but the drawbacks of annoying your user should be more than enough of an incentive to make full screen at least optional.
Posted: Sat Jul 27, 2002 3:45 am
by daemorhedron
While I don't want to start a war here, I must agree that the fullscreen/kill my toolbars thing is a most annoying feature, but at least you have a 'close editor' bit. Regardless, I wrote filters in proximitron to prevent that from happening to me anymore, just so sick of it. As for your code, gj. Seems like it has some issues, but since it's a work in progress, it's not worth it to mention anything at this point. Keep it up.