Thread

Great news! Congrats on the milestone. Can’t wait for the next update. 😊

As of this week ExpressionEngine 2.0 has achieved “feature lockdown,” meaning its highly unlikely anything new will be added to the initial release at this point.

So if we can find the key we can have it? 😊

The jQuery module will allow people to use jQuery and its plugins in their templates without worrying about the location of the jQuery files. This way developers have access to jQuery in a secure way from just about anywhere in EE’s template engine.

Sorry, I must be missing something. What’s the point of this?

I can access jQuery just fine right now using EE templates without worrying about the location of the jQuery files (I use a global variable to point to them from the end of the web page). Why do I need a module for this? What are the possible advantages to me? Or is the advantage related to the jQuery functionality in the EE 2.0 back-end (admin panel)?

I believe the point is focused more towards developers that want to use jQuery, not necessarily the designer building the website.

However, in my opinion I think they decided to make it available for the templates just to take EE one more step towards the one stop shop setup. One less thing to do on an EE install is time I can spend working on the site. This is going along with the blog entry derek had a while ago: http://ellislab.com/blog/entry/a_present_for_your_friday/

The jQuery module will allow people to use jQuery and its plugins in their templates without worrying about the location of the jQuery files. This way developers have access to jQuery in a secure way from just about anywhere in EE’s template engine.

Sorry, I must be missing something. What’s the point of this?

I can access jQuery just fine right now using EE templates without worrying about the location of the jQuery files (I use a global variable to point to them from the end of the web page). Why do I need a module for this? What are the possible advantages to me? Or is the advantage related to the jQuery functionality in the EE 2.0 back-end (admin panel)?

2.0’s CP uses jQuery already. If you want to use jQuery for your templates, you could hard link to it but then you’d risk the possibility of exposing a path to your system folder or other things you don’t want prying eyes to see. The point of the module is to give you secure access to jQuery from whenever you are working in EE so you don’t need multiple jQuery files and can easily standardize on the version the CP is using. Of course, this is optional and you can hook up jQuery or your library of choice however you wish.

To expand on what Les just said with a more technical note, it’s capable of serving the jQuery files from a non-public directory, meaning that you can put your system folder a level above the public HTML root directory, and still utilize the jQuery files that reside there.

Thank you both for this clarification. I keep my jQuery (and other javascript library) files outside the EE system folder now for precisely the reasons you mention. I haven’t tried putting them above the level of the document root, so I’m not sure if that would work. But I don’t think that calling jQuery (in a root level directory) from an ordinary EE template represents a security problem. Does it?

... And while I have your attention, may I ask one other question about EE 2.0?

I have hacked out a few utilities that have more php than html or EE tags in the page. These are data-based utilities like this: http://www.petergallagher.com.au/index.php/agi-db/

In these pages I rely on accessing the EE ‘development’ libraries to do a number of things for me (Database, Display, Functions classes for example). Will my access to these libraries be changed in 2.0? Will I need to change the functions in my pages that access these libraries?

Thank you.

So, has anyone started a ‘Guess the big day” pool yet?

I would say Valentine’s day, I’m feeling the love there 😊
But for real the announcment at last years SXSW Interactive Festival, and this year’s is March 13-17, 2009… slogan/cutline “The Brightest Minds in Emerging Technology”. Not putting any undue pressure here, just I would think if at all possible it will be released by then, or a lot of momentum might be lost. Once you buy in you love the ee product still, but there’s a very wide audience there at the fest. 😊

Any word on if EllisLabs is planning to attend or be a vendor or be a presenter again this year?

Thank you both for this clarification. I keep my jQuery (and other javascript library) files outside the EE system folder now for precisely the reasons you mention. I haven’t tried putting them above the level of the document root, so I’m not sure if that would work. But I don’t think that calling jQuery (in a root level directory) from an ordinary EE template represents a security problem. Does it?

Unless you write a secure script to deliver them from a non-public folder, you can’t place your jQuery files in a non-accessible location.  ExpressionEngine allows you to do this.  It’s not for security of jQuery, but to prevent people from identifying the location of your system folder, but still allowing you to use the jQuery files that are distributed with ExpressionEngine.  And, incidentally, just knowing the location of your system folder does not represent a security threat; security through obscurity is not the control panel’s primary security.  It’s simply good practice.

I have hacked out a few utilities that have more php than html or EE tags in the page. These are data-based utilities like this: http://www.petergallagher.com.au/index.php/agi-db/

In these pages I rely on accessing the EE ‘development’ libraries to do a number of things for me (Database, Display, Functions classes for example). Will my access to these libraries be changed in 2.0? Will I need to change the functions in my pages that access these libraries?

Yes, you will, as this would be akin to an add-on, the only difference being that all of your PHP is in a template.  If you have not already done so, subscribe to the ExpressionEngine blog, and keep your eye open for a post calling for applications for the developer’s preview of ExpressionEngine, which is just for that purpose: to teach developers how and to assist in converting code used for 1.x to 2.0.  You can get a leg up on the syntax and many of the libraries by learning CodeIgniter, our open-source PHP framework.

Many thanks for the additional information Derek.

I have to add “bugger!”. On the other hand, from what I remember of CI when I last looked at it (more than a year ago) the facilities weren’t terribly dissimilar in the areas I’m using (SQL utilities, segment parsing, HTTP header parsing etc). So I’ll take another look.

And I’ll ask to take a look at the ‘developer’ preview of 2.0 (although I’m no developer).

O.k., I’ve got 5 bucks in the pool for March 26th release.
Any takers?

O.k., I’ve got 5 bucks in the pool for March 26th release.
Any takers?

I think I’ll pass, just lost a bet that Obama would announce EE2.0 during his inauguration speech yesterday.

But seriously, really happy for you guys! It’s going to be nice having you back after you release 2.0, it’s not that you’ve left anywhere but you’ve just been keeping yourself too busy.

I looked around but couldn’t find exactly what will happen with CI when EE2.0 gets released? Will it get updated as well and can we expect a merging of the EE and CI forum (at least have one common account)?

I think the member accounts between EE and CI forums are already linked. 😊