Adding text boxes with ezpages

[cjsmiff]

Hi,

I used to use this solution on V1.3.9h:

<div id="contact_content">
<?php
$page_query = $db->Execute("SELECT pages_html_text FROM ezpages WHERE pages_title='Contact Us Bottom'");
$seo_text = $page_query->fields['pages_html_text'];
echo $seo_text;
?>
</div>

But it doesn't work on V1.5.1, I get the following error message:
WARNING: An Error occurred, please refresh the page and try again.

Does anyone know if it's possible to do on V1.5.1 and if so how please?

[kobra]

I used to use this solution on V1.3.9h:

And in what file did you use this?

[cjsmiff]

And in what file did you use this?

templates/classic/templates/tpl_contact_us_default.php

It's from this thread http://www.zen-cart.com/showthread.p...on-to-homepage

[kobra]

Do you have a define page named "Contact Us Bottom"
With the spaces??

[cjsmiff]

Hi Kobra,

No, it's an ezpage.

Following your suggestion I tried closing the gaps but I still got the original error.

This all worked fine as it is on my 1.3.9h version.

[kobra]

This all worked fine as it is on my 1.3.9h version

Compare files & admin settings for this on the 1.5.1 install to your 1.3.9h install

[cjsmiff]

Hi Kobra,

I copied all admin settings when doing the rebuild. I've double checked my ezpage settings and ezpages. Anywhere else you think I should look please?

Many thanks for your time.

[rbarbour]

try

<div id="contact_content">
<?php
$page_query = $db->Execute("SELECT pages_html_text WHERE ezpages.pages_title='Contact Us Bottom'");
$seo_text = $page_query->fields['pages_html_text'];
echo $seo_text;
?>
</div>

[rbarbour]

this should work as well

<?php
$sql = "select pages_html_text from " . TABLE_EZPAGES . " where pages_title = 'Contact Us Bottom'";
$seo_text = $db->Execute($sql);
echo $seo_text->fields['pages_html_text']
?>

[gjh42]

Yes, this would take care of the possibility that your new installation uses a db table prefix. A hard-coded table name like you show would not be able to account for any prefix, so you would get a "not found" kind of error when looking if your new site uses a prefix.