Okay, I just had a thought as I was pouring through the PHP code and looking at the database structure of Comikaze. Basically the app already has a total of four tables and are as follows: News, Comics, Users, and Configuration.
I don't think the solution I'm after has to do with screwing with the tables at all, rather in the variables used on the PHP end. I've already figured out how to create a page that displays *just* the comics, or *just* the news posts. The hurdle I'm up against is when the navigation buttons are used to pull the information from the database they are referencing a defined set of variables.
Those variables direct the user to a new page called "archive_page.php". I already figured out how to edit the "archive_page.php" to display what I want, either just the *comic* or just the *news*. Thus one possible solution would be to create a second set of variables that directs the user to a *new/different* archive page.<?=$comic->firstButton?>
<?=$comic->prevButton?>
<?=$comic->archiveButton?>
<?=$comic->nextButton?>
<?=$comic->latestButton?>
So assuming that the variable set
<?=$comic->firstButton?>
<?=$comic->prevButton?>
<?=$comic->archiveButton?>
<?=$comic->nextButton?>
<?=$comic->latestButton?>
Directs the user to archive_page.php.
How could I create a second set, something like:
<?=$comic->firstButton?>
<?=$comic->prevButtonNews?>
<?=$comic->archiveButtonNews?>
<?=$comic->nextButtonNews?>
<?=$comic->latestButtonNews?>
that would direct the user to the new "News" archive file called news_archive_page.php?
If anyone can tell me how I would create/define the new variables (I can probably figure out what page I need to do this on if I know what to search for) I think I could actually do this!
I feel like I'm *so* close; as always any help would be absolutely wonderful! Did I mention you would be contributing to helping me launch a really awesome website?