Thread

We are pleased to announce that ExpressionEngine 2.2 is now available for download.  This is a major release and brings improvements on a number of fronts: a new file module (and related enhancements), speed/code optimization, a developer friendly authorization library, 180+ bug fixes, CP user experience tweaks, and improved documentation. This is a recommended upgrade for all ExpressionEngine installations.  See the changelog for a full list of changes.  If you’re updating from the current stable version (2.1.3), remember to check the version notes for all relevant versions (2.1.4, 2.1.5 and 2.2).  Want more details before you hit the installer?  Then read on for the juicy details!

Right that is THE release I was looking forward to today!  😊)

What do you know- me too!  😉

Hi Robin,

I downloaded 2.2 as soon as I had seen it had gone live and had a problem on a localhost install where the installer seemed to take ages to do anything but then came up with a memory error. I can’t unfortunately remember the exact error so I will have to have another go at installing in order to get that message again but when I refreshed the page thinking that my browser had perhaps had a benny for some reason it told me I had finished updating the site to 2.2.

I wasn’t updating actually, just installing as a brand new version. That aside though it did allow me into the control panel and most everything that I can see so far seems to work well.

Only thing I’m not sure of is the Watermarking preferences. I’m not sure if I’m perhaps missing something from there due to the install going wonky but I set up a couple of watermarking preferences, one for text and one for image but nowhere could I see where to place the text or choose the image so not sure if that’s due to the install problem or maybe watermarks aren’t fully implemented yet?

Apart from that all is looking good so I’m going to give it a good kicking around to see how things go.

Awesome work ExpressionEngine team, keep it up.

Best wishes,

Mark

Yea- the watermarking stuff is different than in 1.x.  You assign it in ‘File Upload Prefs’ to a File Resize pref.  You can’t assign it to the original image- in large part because you can have different watermarks for different thumbnails.

See Image Manipulations in File Upload Prefs.

The bad news is, it’s a little more work than 1.x.  1.x you just had 1 watermark pref for a whole set of images.  Of course- a FR was so you could do it per thumbnail- so like your initials on a tiny thumb, maybe an image watermark on a big one.  You can do that w/2.x, but you’ll probably want to customize the size of your watermarks to work with the individual sizes you want to apply them to.  (1.x did it by just applying to large image and then shrinking- which is why you could only have one watermark per set.)

And now you know more than you ever wanted to about watermarks in 2.x!  😉

I’m sorry, but something has to be said here about this.  You cannot say “keep ExpressionEngine ahead of the curve when it comes to password security” when you just now are salting password hashes.  People have been salting passwords for YEARS.  Also, if you want to be even close to “ahead of the curve” then you should really be checking to see if bcrypt is installed and use that for true password encryption.  Hashes are insecure…simple as that, whether salted or not (salted is better than not obviously).  Hashes were never meant to encrypt passwords.  They are meant to ensure the content of a file/string…not keeping passwords secure.

You are headed in the right direction, but please don’t flaunt this as some new idea that no one else is doing yet.  What’s worse is that someone had to assist you with this idea?  What is so special about it?  Determining which hashing algorithms the server supports and using the highest one?  Appending a few strings together before hashing?

UPDATE - Just upped the memory limit for MAMP and installed again. No problems with the install this time however the watermark preferences still aren’t showing me all the fields I need. I did this time see them flash on the page very very quickly when first loading the preferences page and they are there in the source but not showing on the screen. There’s a definite Javascript error happening here for me as the fields that I need are being hidden.

Hi Robin,

Thanks for the info although I think there must be something wrong with my install then as I’ve done all that the documentation states but I don’t see some items such as Server Path to Test Image when I choose Image in the watermark preferences. It is there in the source code but doesn’t show up on the page.

Going to give installing another go to see if something went wrong when installing ExpressionEngine 2.2

Best wishes,

Mark

There may be some redundancy some redundancy in the changelog that should be addressed.

Thanks for getting this out early enough in my day (West Coast USA), to play with it today!

Hah. Blue State Digital (Whitehouse.gov) have an EE job post with “EE 2.2” as a requirement:

http://www.authenticjobs.com/jobs/8957/front-end-ee-web-developer

Nice to see this. And congrats on the new release!

is it me or is the admin.php file new inside the root? I can’t find any info on that file in the version upgrade notes.

Does that change anything in the update process when running system folder above root?

is it me or is the admin.php file new inside the root? I can’t find any info on that file in the version upgrade notes.

Does that change anything in the update process when running system folder above root?

Yep, the admin.php file is now in the web root! Take a look at the new installation document, and you’ll see a much more simplified installation process. Part of that process was to mask the system folder right off the bat rather than offer it to users as a best practice.

It won’t break anything in a standard pre-2.2 installation being upgraded, but if your system folder is above web root, just make sure the path is set correctly in admin.php.

is it me or is the admin.php file new inside the root? I can’t find any info on that file in the version upgrade notes.

Does that change anything in the update process when running system folder above root?

Yep, the admin.php file is now in the web root! Take a look at the new installation document, and you’ll see a much more simplified installation process. Part of that process was to mask the system folder right off the bat rather than offer it to users as a best practice.

It won’t break anything in a standard pre-2.2 installation being upgraded, but if your system folder is above web root, just make sure the path is set correctly in admin.php.

Ok but the system/index.php file is also still there? Do you have to set the system folder path in both files now?

Oh Mark- our docs are confusing you.  I hope/think.  The server path to test image and ‘Test Watermark’ button?  Shouldn’t be showing up.  It was removed from the form (yes, it will be going back in in the future).  There is currently no test option like there was in 1.x.  We’ll get those docs updated to remove confusion.

You can’t currently see a test watermark like you could in 1.x.  And testing will have to differ a bit, probably point to a folder rather than a single image- as watermarks will be customized per size rather than one size fits all.

Hope that hasn’t driven you nuts today!

There is currently no test option like there was in 1.x.

You can’t currently see a test watermark like you could in 1.x.  And testing will have to differ a bit, probably point to a folder rather than a single image- as watermarks will be customized per size rather than one size fits all.

Hmm now I think I’m really confused 😉

I’m not really following what you mean by test option and testing although I must admit that I don’t know what you are referring to when you mention 1.x? I can’t for the life of me remember a watermark setting in 1.x?

So do these watermark preferences do anything for now or not?

Best wishes,

Mark

Yep- they work.  But in the watermark docs at the bottom of the form it is currently showing a field for ‘server path to test image’, and then one of the buttons says ‘Test Watermark’.

That field and that button?  Do not exist in the release.  So you can’t test the watermark before applying it.

But- they should be working just fine as long as the watermark is set correctly.  Both the text version and the image version of watermarking were tested extensively.  You do need the correct full path to the image if you’re using one, but if you assign a watermark to a resized image in Image Manipulations in the Directory Prefs- all thumbs for that pref should have the mark added when you upload or sync.