Thread

Hi Robin,

Please partially ignore me 😉

I actually have a support thread online about this as I (thought) I wasn’t seeing how to set the watermarks although now I can see that the server path field is indeed showing up. No idea why I couldn’t see it previously though. The text one isn’t there though so I can’t set what text I want on the image.

I think I understand now what is meant by the server path. I was taking it that was the path to the image to use for the watermark but now I see that it’s actually a path to an image to apply the watermark to for testing?

If that’s right then my next question would be where do you set the image that you want to use as the watermark then? Also how do you set the text that you want if you choose a text watermark?

Best wishes,

Mark

Please totally ignore me. Definitely having a blind spot day today. Can see both the image and text watermark fields :-(

Please collapse my posts above so as not to detract from this thread, thanks.

Best wishes,

Mark

Thank you.
After 2.1.3 to 2.2 file manager has taken a hit or unable to load documents from file location. See thread.

Watermarking was/is good idea but can’t help it to ask…what is the point if we are still lacking multi-file upload or decent (without matrix module) ability to add images into a gallery?

Thank you for a great update - the improvements certainly makes the life easier for me:

* Native file enumeration (one less plugin to care for)
* Automatic additional image resize (one less plugin to care for)
* File meta data, picture title/caption for galleries (very nice)
* Much improved file views

Last but certainly not least, the ability to only allow a certain directory for the file field type… Brilliant!

Great news, congratulations on the 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?

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?

What he said.

It would be good if this was explained in the docs somewhere rather than having to search around the forums for info.

I don’t understand how admin.php does anything to mask system folder…other than shorter path to install.

I don’t understand how admin.php does anything to mask system folder…other than shorter path to install.

Your users don’t need to know the name or location of the system folder when they’re using admin.php. In fact, our best practices page suggests moving the system folder above the webroot and just using admin.php .

Oh right, I thought that new install places ‘system’ folder above the root since admin.php is nothing more than redirect and still shows ‘system’ in URL.

Some feedback from me:

Overall the CP is a lot more responsive, excellent

Exclude from Channel or Field Category Assignment?
- scratching my head on this one, how’s it meant to work?

Debugging
- bit of a pain having another thing to turn off 😊

Accordions still a bit jerky FF5
- lots faster but do we really need the animation, why can’t it just be open or closed?

Yep please do turn off the debugging as standard.

I can understand the thought process behind it but it was the first thing I turned off upon installing 2.2

I do use those options and have managed to get rid of quite a few slower parts of sites by utilising it but I do find it really distracting being on as standard and I’d rather choose myself whether it should be on or off.

Best wishes,

Mark

If the majority of folks want debugging on as standard then that’s fair enough, I can live with that.

Of course one possibility on an install/upgrade is to have an option in the setup wizard to turn it on/off as required.

Wonderful update!

I’m going over the File Module changes and trying to understand the extra metadata stuff. In the docs it says you can display {custom_field_one}, {custom_field_two} etc. But how are these created? I have a local install I’m running through and just don’t get it.

Robin, I would just like to add to the consensus here, that your team’s EE 2.2 is a particularly satisfying release.

There’s an expected level of initial teething moments, but they are being responded to very effectively and rapidly, and in the community, which is the great thing that makes EE go.

I’m particularly impressed by the level of very visible involvement of all helpful staff, especially you, Pascal, and other developers.

You are making this work for people. That is the future.

And, to say what prompted me to finally comment here, you, Robin, are particularly doing this both with verve and with style.

I hope you like that 😉. Compliments deserved, and for your effective results ownership, I am pretty sure.

Best,
Clive

Another thank you.

In January I attempted to update my company’s site and encountered a failure that I won’t go in to here. As a result, I asked EngineHosting to roll back the site and just waited until 2.2 came out.

So it was with some trepidation that I started the update process on Friday. My worrying was unwarranted. With the exception of getting slightly confused about the new admin file (nothing in the update instructions mentions said newness) and forgetting to change the MSM specific paths in index.php, the process went smoothly. One or more of Pixel and Tonic’s addons threw some PHP errors, but only until I updated them as well.

And it could be my imagination, but the speed optimization in this release seems significant. Every page tested seems to load faster; I did not expect a difference that noticeable.

Nice job.