Page Content in Table

BrentNorin

Ok instead of including like 5 pages, or putting 5 pages inside my PHP code, I figured I would put them in mySQL and then retrieve them as needed. My code is passing the right info on to mySQL to retrieve it, but it's not retrieving it correctly.

include("./mysql.php");
$query = "SELECT content FROM pages WHERE name='$page'";
$result = mysql_query($query) or die("Extracting");
$result = mysql_fetch_array($result);
print $result[0];
mysql_close();

Say $page = newsdelete.

In mySQL I have this:

<p>Are you sure you want to delete this article?</p>
<?php echo '<p><a href="./news.php?mode=5&name=' . $name . '&id=' . $id . '">Yes</a>&nbsp;&nbsp;<a href="./index.php">No</a></p>'; ?>

However when the page executes I only get Are you sure you want to delete this article?

Whats going in!

devinemke

if you are storing PHP code in your db then you cannot simply echo the contents, you need to use [man]eval[/man].

BrentNorin

Great now this is complicated, and I'm totally confused. 😕

Roger_Ramjet

Why store your code in a db?? Unless you are grabbing code form other pages, storing it in the db means several statements just to extract and format it, as oppossed to 1 statement to include a code fragment file.

I personally chain my fragments: accesscontrol need db connection so I include that there along with my common functions file. I then include accesscontrol in my header file, which is included in every page to provide a standard set of html cache control headers and the standard <head> section acroos the whole site. This ends up meaning that production pages only need the 1 require statment rather than 4 or 5.

BrentNorin

Well I think I'm going to change the way I plan on doing this. From what I'm reading, eval() is the root of all evil and extracting my php from mySQL is going to be more complicated than the simple idea seems. I mean doesn't it just seem simple to put it in and pull it out? Why does it have to be so complicated.

Roger_Ramjet

Well, storing and retrieving text from a db is easy, it is getting the text to execute as code that is the problem (eval is the solution). This is one of those things that sounds like a good idea at first, but then you work out the processing:

store in db
1 open base file on webserver
2 connect to db server
3 process query
4 process results
5 generate and execute new code

store in file
1 open base file on webserver
2 open included file on webserver
3 execute code

The biggest overhead here will be the db connect and query.