Help installing 1.5

[devenh]

I'm a newbie so pardon what may be obvious questions.

I've uploaded to my site EE 1.5 with all the patches, have run and deleted install.php and renamed my input directory. phpMyAdmin shows a large number of ee_ tables created.

Now I am trying to follow the instructions in http://www.photography-on-the.net/ee/beta/setup_upload_system.php. Step 1 says to "open EE's server info in editor." First, I assume you mean serverinfo.php in the input directory. It would help if you were more specific on the file names. Next, do you mean open with an editor like notepad? Or open and run the script in my browser? If I try opening it in a browser, I get this error:

Error in performing query fetch_one: Unknown column 'ee_use_custom_list_settings' in 'field list'

So I am stuck on step 1.

Deven

[Pekka]

Open gallery/input/index.php - this is the editor and menu items there are referred in manual. Sorry about not being clear about that.

[devenh]

Okay, I tried running index.php, but I got the same error message:

Error in performing query fetch_one: Unknown column 'ee_use_custom_list_settings' in 'field list'

Deven

[Pekka]

Oh, you've forgotten to run 15_b4_fix_pack_2.php from EE15_b4_fix_2.zip

[devenh]

Okay, I've gotten 1.5 up and running. Couple of more questions:

1. Performance seems a slow. Are there any settings I can change to improve performance?

2. I created three sizes: small, normal, and large. When I uploaded my photos, I selected all three sizes and resized copies of the images were placed in all three directories. I understand this may improve performance by resizing them ahead of time, but it does use more disk space. Can I just upload to the large directory and will EE resize on the fly? If an image is resized, will EE keep a copy on disk or will it delete the smaller version after some period of time?

3. Are any more 1.5 docs available? When do you anticipate 1.5 being final?

Deven

[smeyer]

1. Performance seems a slow. Are there any settings I can change to improve performance?
I've tried setting up 1.5 with all the fixpacks as well, and it's VERY slow; it litterally takes minutes to fire up an exhibition.

What could be wrong?

[Pekka]

1. Performance seems a slow. Are there any settings I can change to improve performance?
I've tried setting up 1.5 with all the fixpacks as well, and it's VERY slow; it litterally takes minutes to fire up an exhibition.

What could be wrong?

You need to have at least 7 photos in EE database.
Run both optimize commands in editor "optimize".

[Pekka]

Okay, I've gotten 1.5 up and running. Couple of more questions:

1. Performance seems a slow. Are there any settings I can change to improve performance?

You need to have at least 7 photos in EE database.
Run both optimize commands in editor "optimize".

2. I created three sizes: small, normal, and large. When I uploaded my photos, I selected all three sizes and resized copies of the images were placed in all three directories. I understand this may improve performance by resizing them ahead of time, but it does use more disk space. Can I just upload to the large directory and will EE resize on the fly? If an image is resized, will EE keep a copy on disk or will it delete the smaller version after some period of time?

In path editor select resize method "NONE" for the path holding the biggest size (uploaded). That will make EE just copy the big photo to correct folder.

I don't see why EE would delete the smaller size(s) automatically?

3. Are any more 1.5 docs available?

There will be more docs (online help) with RC version and more on final. Feel free to ask anything.

When do you anticipate 1.5 being final?

"soon"

[devenh]

I don't see why EE would delete the smaller size(s) automatically?


I would think it would be useful to have an option that conserved disk space. Here's how it would work:

1. Upload the largest viewable size to a directory (e.g. /large)
2. Visitor has option to view multiple sizes (e.g. small, medium, large)
3. If visitor requests large view, EE provides file from /large
4. If visitor requests small or medium view, then EE checks /small or /medium for existing copy, if not found, it creates a smaller copy
5. If the smaller copy is not viewed again within N minutes, then delete the smaller copy (essentially creating a MRU cache)

This approach would would great for exhibitions containing a large number of infrequently viewed images.

Deven

[Pekka]

I don't see why EE would delete the smaller size(s) automatically?


I would think it would be useful to have an option that conserved disk space. Here's how it would work:

1. Upload the largest viewable size to a directory (e.g. /large)
2. Visitor has option to view multiple sizes (e.g. small, medium, large)
3. If visitor requests large view, EE provides file from /large
4. If visitor requests small or medium view, then EE checks /small or /medium for existing copy, if not found, it creates a smaller copy
5. If the smaller copy is not viewed again within N minutes, then delete the smaller copy (essentially creating a MRU cache)

This approach would would great for exhibitions containing a large number of infrequently viewed images.

Deven


I'll add this to my "features to think about" list to further investigation. Generally I do not want any realtime image resizing happen in public interface for server load reasons.

[smeyer]

You need to have at least 7 photos in EE database.
Run both optimize commands in editor "optimize".

That did the trick - thanks! :D

Additional question: I do NOT have ftp-access via php :( Does this mean, that I can't use 1.5? For instance: how do I delete a pic from an exhibition?

/Steffen

[TomKa]

This should be change with the 1.5RC and the new ftp-system. Is this right Pekka?

[Pekka]

Yes. 1.5 RC does not need PHP ftp module at all. Also EXIF can be chosen to be handled internally, and XMP reader is also inbuilt.

[wcbert]

Yes. 1.5 RC does not need PHP ftp module at all. Also EXIF can be chosen to be handled internally, and XMP reader is also inbuilt.

Pekka

Version 1.5RC, is there a new version EE out now?

Bill

[smeyer]

Yes. 1.5 RC does not need PHP ftp module at all.Sounds good - What is 1.5 RC ?

[Pekka]

RC = Release Candidate. This will be the last version before version which can be called release version (or gold version).

I've pretty much coded all features required - today I added a userdefinable "insert category from IPTC" system. Now I'll do online helps and check few things - not many days til I can put it out to final testing.

[smeyer]

RC = Release Candidate. This will be the last version before version which can be called release version (or gold version).

I've pretty much coded all features required - today I added a userdefinable "insert category from IPTC" system. Now I'll do online helps and check few things - not many days til I can put it out to final testing.

KEWL!

[TomKa]

GOOD news, do I have to stay at home in front of my monitor over the weekend.... 8)