11
Unfortunately, the French example about XoopsObject and XoopsObjectHandler usage is incorrect.
Its method of including the class definition file and then calling xoops_gethandler can be replaced with a call to xoops_getmodulehandler('sortof_name_of_class');
I say 'sortof...' because e.g. in an article module, you could call xoops_getmodulehandler('article') and XOOPS will look for a file called article.php inside the module's class folder. That file must contain a class called [module's dirname]ArticleHandler. But if it does, you don't need to include any files before calling xoops_getmodulehandler().
There are some other mistakes in that tutorial as well, but not regarding XoopsObject/XoopsObjectHandler usage.
Its method of including the class definition file and then calling xoops_gethandler can be replaced with a call to xoops_getmodulehandler('sortof_name_of_class');
I say 'sortof...' because e.g. in an article module, you could call xoops_getmodulehandler('article') and XOOPS will look for a file called article.php inside the module's class folder. That file must contain a class called [module's dirname]ArticleHandler. But if it does, you don't need to include any files before calling xoops_getmodulehandler().
There are some other mistakes in that tutorial as well, but not regarding XoopsObject/XoopsObjectHandler usage.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."
Cusix Software
Cusix Software
)
