A couple of issues with RC4

[Miika]

1. Considering the zip archive: when extracted directly under linux, almost all files and directories get write permission to world (rwxrwxrwx).

I noticed that the (1.22) installation instructions tell you specifically to download and unzip the archive first on your PC, and extract/edit there before uploading the files to a server. This extra maneuver of course avoids the problem above... But I like more the black background PuTTY/ssh/VT220 display and editing on the server with emacs or pico rather than using windows Notepad. Old dog won't learn new tricks. Sorry.

I saw a quick mention of some folders requiring write permisssions (the upload and picture folders), these could be listed in the FAQ.

2. It might be something wrong with the installation (I did the full RC4 installation), but the EE has a little bit exaggurated idea of my camera equipment.

The php server I try to run the software doesn't have an EXIF module, so this could be a bug of the EXIF (INTERNAL) module.

Suggestion: instead of the guess option (based on the the EXIF data), the user could force camera/lens information when uploading the pictures. Changing information of 200+ pictures with the EE photo editor is a little bit painful. (Of course this is done in less than a second with one SQL update query, but on the first day experimenting with the software I won't try the easy solution).

Great job, Pekka!

Miika

[Pekka]

1. Considering the zip archive: when extracted directly under linux, almost all files and directories get write permission to world (rwxrwxrwx).

I noticed that the (1.22) installation instructions tell you specifically to download and unzip the archive first on your PC, and extract/edit there before uploading the files to a server. This extra maneuver of course avoids the problem above... But I like more the black background PuTTY/ssh/VT220 display and editing on the server with emacs or pico rather than using windows Notepad. Old dog won't learn new tricks. Sorry.


I saw a quick mention of some folders requiring write permisssions (the upload and picture folders), these could be listed in the FAQ.

Ok, I'll make a note of it. Sounds odd that 777 is default permission - in my server is seems to be 755.

2. It might be something wrong with the installation (I did the full RC4 installation), but the EE has a little bit exaggurated idea of my camera equipment.

The php server I try to run the software doesn't have an EXIF module, so this could be a bug of the EXIF (INTERNAL) module.

The relational database of EE can contain many items which you may not neccessarily use for your photos. This excess data is not a bad thing, if you see optimize link in editor it will explain why.

Visitors see only those items which are assigned to your photos. All other items in database editors will be totally hidden from public.

Suggestion: instead of the guess option (based on the the EXIF data), the user could force camera/lens information when uploading the pictures. Changing information of 200+ pictures with the EE photo editor is a little bit painful. (Of course this is done in less than a second with one SQL update query, but on the first day experimenting with the software I won't try the easy solution).

The set default photodata editor lets you set default lens and most other settings, so that when you untick guess commands on upload page they will be used instead. There are many shooting detail settings in default data, those are obviously overridden if more valid data is found in image.

If you need powerful global commands, see EE powertools in editor area.

IMPORTANT NOTE: Please do not edit the database with any homemade SQL - only with EE editors and tools they provide. I do not give support to EE's which have database altered by any other method. Chances are that when doing homemade SQL you do not know how EE's table and data relations work and what affects what - speed may be crippled or it may render you galleries unusable. Can't debug those kind of problems.

Great job, Pekka!
Miika

Thanks Miika. Best regards to Opera basses - btw: I saw Sami in women's magazine as a "model" the other day. :)

[Miika]

Ok, I'll make a note of it. Sounds odd that 777 is default permission - in my server is seems to be 755.


My bash profile defaults to 644 for files created from scratch and 755 for directories.

A tar-archive would preserve original file permissions, I think the problem is with zipping; encoding or decoding.

If you need powerful global commands, see EE powertools in editor area.

The Powertools fixed the problem with weird lens information for my G3, although I managed to get a couple of "0 rows affected" -messages. Unfortunately I didn't document how I got them.

It looks like EE is up and running! 8)

Miika