Thread

With such new features as Strict URLs, better Auto-XHTML typography, advanced control parameters for the weblog entries tag, an included extension to enable jQuery in your control panel for third party add-ons that utilize it, 1.6.5 brings a lot of goodness to the table.

To read about the 60-some changes to ExpressionEngine 1.6.5, please see the Change Log in the user guide.  Head on over to your download area and grab the update!

Thank you thank you thank you (to all 3 updates that came)!

I was hitting my head (at one thing that i didnt manage to get working with Safari) and these came just about right time. Now i have something other to think about and see what there comes when updating!

Yeah, i know, im addicted to these updates =)

Already DLed and later tonight updating.. *lal lalala laaa*

Cheers:
- Tuittu

EDIT: what is the right way to make all updates - 1.6.5 then forums and last MSM?
Or does this matter in any way?

EDIT: what is the right way to make all updates - 1.6.5 then forums and last MSM?
Or does this matter in any way?

They are independent of one another, but you should do them all together, i.e. back them all up, update them, and then turn your site back online.

I see you finally caved on adding redirect as a global variable.  I remember unsuccessfully trying to convince you that should be added.  Notice I said “caved” and not convinced, not sure you are convinced even though you added it.  😉

The change on the embed tag is nice too.

Thanks!

I see you finally caved on adding redirect as a global variable.  I remember unsuccessfully trying to convince you that should be added.  Notice I said “caved” and not convinced, not sure you are convinced even though you added it.  😉

The change on the embed tag is nice too.

Thanks!

The landscaped changed a bit since then, actually.  In order to give users the most flexible interpretation of Strict URLs, {redirect=} is a necessary component, which means that for a redirect action, it’s no longer a best solution to recommend PHP or a non-native plugin.  And you’re welcome. 😉

Why is that any more awkward?  Your still going to have to check a global object external to your own add-on.

Actually, the end of that conversation led to developers saying that nGen Work’s extension was the solution they’d support.  That’s what we implemented, and made easier for lay-people to use.  And there’s no need to dive into to the hooks array:

isset($EXT->version_numbers['Cp_jquery'])

True enough.  I’m going to drop back into the original thread for this, so we can spare non-developers from this conversation in this thread.

Great, looking forward to update, especially {redirect} will be more than helpful.

Before answering here, I wanted to ask how to check for the jQuery extension now, guess I’ll relocate to the other dev thread again 😉

It’s all good…
Thanks for getting this version posted right before the weekend.
I had a quick question too, there had been talk of search and replace in V.2 for developers to get things up to task. Was that still the plugin that was being referred too that is here:
Find and Replace plugin or was it going to become a native functionality in v.2? Just wondering if I should check out the plugin now then.
Thanks again!

I don’t have any idea what you’re talking about, ™T.Gee., and I’m not being coy: I honestly don’t know what you’re referring to.

Hi Derek,

Can you elaborate on this a bit:

Modified data storage to allow for a higher theoretical maximum number of custom entry fields.

Has the way custom fields are stored in exp_weblog_data changed?

Hi Derek,

Can you elaborate on this a bit:

Modified data storage to allow for a higher theoretical maximum number of custom entry fields.

Has the way custom fields are stored in exp_weblog_data changed?

No, just the formatting columns, details are in ud_165.php if you’re curious.

I don’t have any idea what you’re talking about, ™T.Gee., and I’m not being coy: I honestly don’t know what you’re referring to.

Judging by your reply that would be a “no” on the native functionality.
You had mentioned search and replace here. What do you use for search and replace, maybe just an IDE was what your reference meant or using the plugin then maybe.
Thanks anyways.

Ah, that was in reference to how a developer would go about making their add-on compatible with 2.0.  Meaning that a step by step list of things to perform find/replace in their code.