CMS Builder 2.13 Preview Issue

5 posts by 2 authors in: Forums > CMS Builder
Last Post: December 16, 2011   (RSS)

I'm having an issue on a site that I'm developing. When I attempt to preview an edit to a current page I'm brought to a page displaying ?preview-9999999999 After the file name.

This page is displaying the correct current page minus the edit that I'm attempting to make.

Any thoughts on what may be causing this?

Thank you.

Re: [bragg31] CMS Builder 2.13 Preview Issue

By Jason - December 15, 2011

Hi,

Could you please attach a copy of the page you're using for previewing the record?

thanks
---------------------------------------------------
Jason Sauchuk - Project Manager
interactivetools.com

Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/

Re: [Jason] CMS Builder 2.13 Preview Issue

Hi Jason,

Thank you for responding. I've attached one of the pages for your review.
Attachments:

personal-insurance.php 3K

Re: [bragg31] CMS Builder 2.13 Preview Issue

Jason,

I just compared the detail page code generated from this site to an older site I did using version 2.07 of your software and I did find a difference that seems to have solved the issue for me in this particular case.

This is the code generated from 2.07 for the detail page:

// load records
list($tid_bitsRecords, $tid_bitsMetaData) = getRecords(array(
'tableName' => 'tid_bits',{
'where' => whereRecordNumberInUrl(1),
'limit' => '1',
));
$tid_bitsRecord = @$tid_bitsRecords[0]; // get first record


Here is the code from the current version 2.13:

// load records
list($personal_insuranceRecords, $personal_insuranceMetaData) = getRecords(array(
'tableName' => 'personal_insurance',
'allowSearch' => '0',
'limit' => '1',
));
$personal_insuranceRecord = @$personal_insuranceRecords[0]; // get first record


The hightlighted line in the older version is what seemed to get the previews working again for me.

I guess my question now is did you phase that out of the current code generator for a reason? Should this be achieved a different way with the current v2.13?

Thank you.