Numeric value in URL causing problems with page PHP output

5 posts by 4 authors in: Forums > CMS Builder
Last Post: March 31, 2011   (RSS)

By gadefgaertgqe - March 30, 2011 - edited: March 30, 2011

Hey all,

This one is a bit quirky. I have a search option via drop downs. All works well, except when one of the drop downs is a numeric value greater than 1 (so anything 2 or over causes problems).

When the page is rendered the following code shows no output on the page.

<?php echo $mainRecord["dealer_title"] ?>

If there are no numbers in the URL (a numeric 1 is fine as I mentioned), then the above code works fine.

This smells of a 'record number' issue, but no idea where to go from here.

Url examples as follows:

Works:
peugeot-scooters-list.php?model_range=Vivacity&engine_size=&cooling_system=&colours=&submit=Search

Fails:
peugeot-scooters-list.php?model_range=Speedfight+3&engine_size=&cooling_system=&colours=&submit=Search

I have tested the number theory with other fields and get consistent results.

On a side and possibly related note, I seem unable to get useSeoUrls' => True to work.

Thanks

Paul

Re: [Pixels & Beats] Numeric value in URL causing problems with page PHP output

By robin - March 30, 2011

Hey,

Could you post your peugeot-scooters-list.php code or mail it to support@interactivetools.com? We'll take a look.

Thanks
Robin
Programmer
interactivetools.com

Re: [Pixels & Beats] Numeric value in URL causing problems with page PHP output

By gkornbluth - March 30, 2011

Hi,

Just a wild guess which probably has no relevance.

Is there an errant

'where' => whereRecordNumberInUrl(1),

in one of the record calls at the top of your page?

Jerry Kornbluth
The first CMS Builder reference book is now available on-line!







Take advantage of a free 3 month trial subscription, only for CMSB users, at: http://www.thecmsbcookbook.com/trial.php

Re: [gkornbluth] Numeric value in URL causing problems with page PHP output

By gadefgaertgqe - March 31, 2011

Bingo Jerry!

'where' => whereRecordNumberInUrl(1), is indeed causing the problem.

I just need to work out why I was using it now. I keep getting pulled off this project and then back on it.... lol

Thanks to everyone else who contributed :)

Paul