php 5.3.2 includes a function name wholes themselves

Regards

Luis

Now the query method allows to pass a sql as argument, but this sql is not getting processed, it sounds to me that the *only* way to avoid the process should be using setBareQuery, all the others methods have to process the sql.

<td align="left">
<?php
if ( $row->checked_out && ( $row->checked_out != $my->id ) ) {
	echo $row->name;
} else {
	?>
	<a href="<?php echo $link; ?>" title="<?php echo T_('Edit Banner'); ?>">
	<?php echo $row->name; ?>
	<br /><img src="/images/banners/
	<?php echo $row->imageurl; ?>
	">
	</a>
	<?php
}
?>
</td>

It Rocks to see the banners graphically when managing them.

Of course, optionally, it would also require a modification to the number of elements per page, 50 banner ads up and being displayed like this will be rather boggy. Perhaps a checkbox at the top of the list for switching to “Show Graphics” mode causes a page reload with the limit set to, say, 25 per page?

I recently upgraded from 4.6.2 to 4.6.5. The upgrade went smoothly, and I edited the new config with our site settings - including our offset of +18.

When creating a new content item, the time displayed on the front end is correct.

However, when we modify the item, the offset is applied again (i.e. the Server time + the offset + the offset)!

e.g. I created a test item, and the front end displayed the time/date of “Dec 22, 2009 at 10:15 AM " as expected.

I edited the content, just adding a line of text and nothing else, and now the time/date displays “Dec 23, 2009 at 04:15 AM” on the front end.

If I edit again, the offset gets added once again (”Dec 23, 2009 at 10:15 PM”).

When editing an existing content item, I note that the “Override created date” field is populated with the time currently displayed on the frontend - the offset is then applied to that when saving. If I edit the content again, the “Override created date” field is again populated, with the new “front end displayed time”.

I attempted to troubleshoot and got some help at:

http://forum.mambo-foundation.org/showthread.php?t=17838

... to no avail.

We also tried a fresh install with a fresh database and saw the exact same behaviour with the sample data (i.e. we did not use our production database or site files, only the clean install code / database).

Install is on:

PHP version 5.2.11
MySQL version 4.1.22-standard

Thanks in advance.

There are two versions.
The service, which plugs in:

http://www.afterthedeadline.com/

And the source code, which is open source and GPL: http://open.afterthedeadline.com/

At the moment, it only supports English so is not appropriate to use in the core. It would be useful to add support into the core and to make it into an optional core extension though.

option=com_blahblah&Itemid

i am using mambo vs 4.6.0 and our host server updated to php vs 5.3 as of today without letting me know and i am getting various warnings allover our site.

Warning: Parameter 3 to showSection() expected to be a reference, value given in ........./www/includes/Cache/Lite/Function.php on line 100

code is:
} else { // function
$result = call_user_func_array($target, $arguments);
}

function: sendNewPass

global: $mosConfig_mailfrom is not declared, therefore causing an error on line 92:

mosMail($mosConfig_mailfrom, $mosConfig_fromname, $confirmEmail, $subject, $message);

when attempting to request a password reminder sent to the user/email address specified.

here is the apache log file error proving the condition:

PHP Notice: Undefined variable: mosConfig_mailfrom in C:\\blah\\components\\com_registration\\registration.php on line 92, referer: http://www.example.com/index.php?option=com_registration&task=lostPassword

The fix is to add $mosConfig_mailfrom to the list of global declarations at the start of the sendNewPass function.