Frontend Template Parsing Error on >

Max:

I have made many attempts today to solve the problem I have mentioned in some other posts, and I think I have detected the root source of the problem with the interpreting of php code in the front end template. It appears that after the starting tag for the php code, the very first greater than sign is interpreted as the end of php code tag. It does not matter what character comes before the greater than tag. For example, if the php code includes "$room->room" everything after that greater than sign is treated as html code and not php code. Same thing for the end of an html tag that might be echo'd by some php code.

Hope this helps,
George

Hi george, ok, thank you, I will test this but tomorrow, but if you added the select tag in PHP it still doesn't work then ?

Max

Any fix for this problem yet? Thanks.

Brian

Hi Brian,

George found a work around and posted it here in another post, check his posts, the issue is not fixed yet!

Regards
Max

Max,

Thanks for the quick reply. However, the work-around doesn't really work for me. I've built a major application for a client based on ChronoForms and ChronoConnectivity (over 50 forms). Any idea when a true fix will be available? Thanks.

Brian

Hi Brian,

Show me the code which fails and I will try to find a quick fix, explain the problem in more detail, I'm busy nowadays in a new release for Chronoforms to come out by the new year hopefully!

Regards
Max

Max,

Here's sample code (and these are the first lines of code in the form) which fails in the frontend template but works perfectly in the admin template:

<?php
$database =& JFactory::getDBO();
$user = JFactory::getUser();

$query_houseid_list = "SELECT jos_chronoforms_house.cf_id, jos_chronoforms_house.house_address1 FROM jos_chronoforms_house WHERE jos_chronoforms_house.cf_user_id = $user->id";
$houseid_list = mysql_query($query_houseid_list);
$row_houseid_list = mysql_fetch_assoc($houseid_list);
$totalRows_houseid_list = mysql_num_rows($houseid_list);
?>
<p>
  <select name="houseid" id="houseid">
    <?php
do {  
?>
    <option value="<?php echo $row_houseid_list['cf_id']?>"><?php echo $row_houseid_list['house_address1']?></option>
    <?php
} while ($row_houseid_list = mysql_fetch_assoc($houseid_list));
  $rows = mysql_num_rows($houseid_list);
  if($rows > 0) {
      mysql_data_seek($houseid_list, 0);
	  $row_houseid_list = mysql_fetch_assoc($houseid_list);
  }
?>
  </select>
</p>

I get the following error when editing a record in the frontend:

Parse error: parse error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in /htdocs/www/myprepareplan/components/com_chronoconnectivity/chronoconnectivity.html.php(281) : eval()'d code on line 2

Any help would be greatly appreciated.

Brian

Hi Brian,

I'm largely guessing here but the only thing I see on line 2 is that you may need =& to reference the user object, though I'm not sure why.

Bob

Bob,

Thanks for the idea but that didn't work. Also, tried similar combinations. Not sure where to go from here.

Brian

Hi Brian,

Thats ok, I will test this soon and get back!

Regards
Max

Hi Max,

Happy New Year. Any update on this issue yet?

Brian

Hi Brian,

Happy new year!

No news yet sorry, busy with Chronoforms update at the moment! will have free time once I finish it!

Regards
Max

Hi Max,

Any chance for a fix to this problem soon? Thanks.

Brian

Hi Brian,

10 minutes ago I posted the new release for Chronoforms, so soon I will look into the issue!

Regards
Max

Hi Max,

That's great news. I look forward to using the new ChronoForms and hopefully you can help me with the ChronoConnectivity bug soon. Cheers.

Brian

Hi Max,

Any chance that this bug will get resolved soon?

Brian

Hi Brian,

I know it has been a long time now, I will check it just after I add V3.1 RC3 of Chronoforms.

Regards,
Max

Hi Max,

Has there been any progress on this question? At the moment it would be really needed!


Cheers,
Jeffrey

Hallo Max,

In the between time I have now met the next problem. While trying to enter a simple   in the front permissions, I always end up with a lovely question mark on the page, but it works perfectly in the admin config. Does this problem perhaps have the same origin?

Greetings
Jeffrey