Thread

I wanted to make a quick broadcast to third party developers about a potential issue in the upcoming ExpressionEngine 2.1 release with your add-ons, depending on how you were building file paths with CodeIgniter.  If affected, your add-ons will break in ExpressionEngine 2.1, so it is very important for users of your add-ons to have updated code prior to its launch.  If you have been building your file paths with PATH_THIRD or APPPATH*, you should not be affected.

Read on…

Thank you for this information!

Will we have clean documentation for creating EE 2.1 modules like we have now for 1.x?

I’m getting ready to whip up something fun, and I will certainly need help. I’m specifically interested in developing an EE module - not a standalone CI application.

Warmly,

Bill

Bill, that’s existed for a long time, beginning in April of last year for registered developers, and December to the general public. 😉

Derek, I presume the initial

<?php  if ( ! defined('BASEPATH')) exit('No direct script access allowed');

as per the module tutorial is unaffected?

Or do I need to replace those?

Correct, unaffected.  That is simply a sanity/safety check to make sure that the file is being accessed in the context of a CodeIgniter instance.

Great. Thanks for the prompt response Derek.