xajax extension 1.1
April 24th, 2006
Once again, Bruce Morisson was so kind to update the xajax library in the eZ publish xajax extension. Thanks Bruce!
On my turn, I’ve updated the xajax contribution on ez.no. It’s numbered 1.1 now, and beside the update to the xajax library, the default xajax.ini settings file was moved from the extension’s settings directory to the install directory. It’s not necessary anymore (it’s only advised) to move it to the main settings directory of eZ publish.
A very useful function was added in xajax 0.2.4: addScriptCall. I will update the xajax_classattributes extension soon to use this function instead of calling JavaScript functions with the addScript method. Also the contribution page on ez.no will be updated with a release containing the new features and fixes that are already in SVN.
Entry Filed under: eZ Publish,xajax
3 Comments Add your own
1. Paul Borgermans | April 24th, 2006 at 9:24 pm
Cyberwolf did it again!
2. Kristof | April 25th, 2006 at 7:23 am
No, Bruce did it again
3. Marcel Gomez | June 19th, 2008 at 3:51 pm
Hi Kristof !
I already have my site finished, but now I’m trying to plug it with xajax 1.1.
I have this PHP code (from the eZ forum):
function xxxx($object_id) {
// HTTP Response
$objResponse = new xajaxResponse();
// template init
$tpl =& templateInit();
// Add Variable to the template
$tpl->setVariable(‘object_id’, $object_id);
// fetch template
$html = $tpl->fetch(
“extension/mod_myextension/design/standard/templates/foo/bar.tpl” );
$objResponse->addAssign(“mydiv”, “innerHTML”, $html);
// response
return $objResponse;
}
I need to know where to write this code, and how can I invoke this function from any of my links, given the objectID of the node which content will be shown.
Plase, any hints will be really appreciated because we are almost in deadline of our project.
thanks in advance,
Marcel
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed