Openx插件开发
我刚刚进入OpenX的世界，发现新版本是用PLUGIN Framework构建的。我已经阅读了 Openx 插件开发文档，但它有点复杂，而且解释得一半。
作为一名 php 开发人员，我想涉足 openx 的插件开发。
如果有人能指出我的起点，并提供良好的参考和教程？
谢谢， 坦美
I have just entered in the world of OpenX, and as figured out that new version is built with PLUGIN Framework. I have gone through the Openx plugin development documentation, but its quite bit complicated and half explained.
Being a php developer, I would like to jump into plugin development for openx.
If anyone can point me to a starting, with good reference and tutorial?
Thanks,
Tanmay
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我没有得到太多参考，但这里是可以帮助您创建插件的链接
https://svn.openx.org/openx/trunk/plugins_repo/release /openXDeveloperToolbox.zip
使用它您可以创建插件框架。这对于理解文件结构有很大的帮助。
希望有人能得到帮助
I didn't got much reference but here is the link which can help you create plugins
https://svn.openx.org/openx/trunk/plugins_repo/release/openXDeveloperToolbox.zip
With this you can create a framework of plugin. This will be a great help to understand the file structure.
Hope some one will be helped
通过使用 openX Developer Toolbox，我们可以创建新的模拟插件，基本上它将创建一个新的模拟插件文件，您必须根据要求更改这些文件，然后就可以安装该插件。这不是构建插件的完全好的解决方案，但它会帮助您构建插件。
by using openX Developer Toolbox we we can create new mock plugins, basically it will create a new mock plugin files and you have to change those files as per requirement and you can install that plugin. It is not fully good solution for building a plugin but yes it will help you build a plugin.
这是插件的另一个资源（包括上面工具箱的链接以及演示插件）：
http://blog.openx.org/05/plugin-framework-exposed/
Here is another resource for plugins (includes a link to the Toolbox above as well as a demo plugin):
http://blog.openx.org/05/plugin-framework-exposed/
使用插件骨架生成器时要小心。它将生成名称错误的传递方法的函数名称。所以最后它根本不会被调用。
在函数名称中添加“_adRender”（作为后缀）应该可以解决此问题。
Take care when using the plugin-skeleton generator. It will generate the function name of the delivery method with a wrong name. So at the end it will NOT be called at all.
Adding "_adRender" (as a postfix) to the function-name should fix this.