[ixian]

Originally Posted by krohnathlonman

Whats the best way to handle a multi page submission like that? just have say 2 pages at a time and post them into hidden form elements?

I wrote this completely with the display end speed in mind. I had to make sure it could handle 150k+ pageviews a day because my site spikes up there often enough that I have to worry about it. I don't want my server crawling from it. In the next release you'll see in the admin panel where it's real easy to turn features off. I'm also writing some global variables for you guys to define!

Thanks for point that <> out... I overlooked it! I'll start testing it after I get my feature list taken care of Something that big will be one of the last things I do! I want to make sure everythings stable and working great before I throw something as big as that into the mix.

This shouldn't affect display speed, it's all on the admin side.

The best way for THIS hack, I think, is as I kind of went into above:

Have ONE text area on the submit page.

Instead of one submit button, have two - one that says submit, one "Next Page" or "Continue" or whatever.

If the user hits submit, that means they are done adding pages, and the article is submitted exactly as it is done now.

If they hit "Next Page", then you have a subroutine that:

Submits the textarea data in the form to it's space in the db table.

Brings up a new window, textarea field called p2 like you have it now.

And so on.


OR

Have it be all one page for submitting the form/textarea data, and have the user insert a custom tag like <pagebreak> or something where they want new pages to start. Adding a button to do that automatically in HTMLArea - so the user just puts the cursor where they want the new page to start and clicks "New Page" - is so simple it's not even funny.

Now, I know you are worried about load, and that is a valid concern of course. However, you are missing something here. The <pagebreak> tag I talk about above isn't something that gets processed every time someone views an article. It's post-processing done when you submit the article. In fact, your article.php and the rest of your code won't need to be modified at all. Just the add article file.

What you do is add a routine for the pagebreak tag, and have each section submit to your table/pages. Something like this:

PHP Code:

$textarray=spliti("\[PAGEBREAK]",$text); 


Would work. Use spliti to split the text for you (spliti is case-insensitive unlike split). Now you have php doing all the work for you when you submit an article. And as I said, this is NOT done on the viewing side - it doesn't change a thing. This is all done on the submit side.

If you want, when you get your latest changes uploaded (you really need something to handle categories, but you already know that) I'd be happy to work on part of this for you. Just let me know.