A few questions

[Greg M]

I couldn't get the thumbs to show up in the exhibition editor but I figured that out. Now when I add photos in the "pick a photo to edit" all I get is a box with an X in it. It shows my filenames in the select filename box but no pictures show up.

Warning: Offset 0 is invalid for MySQL result index 6 in /...gallery/.../verify.php on line 88
SIZE AVAILABILITY CHECK PAGE
for
PRESS REFRESH ON YOUR BROWSER AFTER HAVING DONE SIZE PATH CHANGES


This is the error I get when I check the validity of size paths for this filename. The path to my pictures is /...gallery/.../Church/D30_photos/"folders of diff sizes". How do I fix this?

Is there a link to a suggested workflow for setting up a new exhibition?

Thanks to whomever takes the time to help me with this.

Also, is there a place to insert a link back to my main website?

[Pekka]

Greg M wrote:
I couldn't get the thumbs to show up in the exhibition editor but I figured that out. Now when I add photos in the "pick a photo to edit" all I get is a box with an X in it. It shows my filenames in the select filename box but no pictures show up.

Warning: Offset 0 is invalid for MySQL result index 6 in /...gallery/.../verify.php on line 88
SIZE AVAILABILITY CHECK PAGE
for
PRESS REFRESH ON YOUR BROWSER AFTER HAVING DONE SIZE PATH CHANGES

This is the error I get when I check the validity of size paths for this filename. The path to my pictures is /...gallery/.../Church/D30_photos/"folders of diff sizes". How do I fix this?

Is there a link to a suggested workflow for setting up a new exhibition?

You path /...gallery/.../Church/D30_photos/"folders of diff sizes" soes not sound as a correct relative path. New photo photo selection page uses relative paths to display the directory. See FAQ for explanation how relative paths are defined. BUt if you can see the filenames, then you may have problem with capital letter extension (JPG) or spaces in filenames (1.22 did not handle those). You may want to upgrade to 1.3RC (see other message in this area) so that you may not have to change any filenames.

The validity checker checks size paths URL part. Seems like you have no URL defined (1.22 gave that ugly error, 1.3RC explains it in english).

Basic rules are:

1. Each size, thumb and microthumb have identical filename which the database refers to.

2. In EE 1.22 don't use any spaces or special characters in paths or filenames, and you must use small file extensions.

3. When you put a filename in the end of a size path and try that directly on browser: if you see a photo, EE will see a photo, if you don't EE don't either.

Example:

you have set path

http://www.mysite.com/photos/big/

and you have a filename

xxxxxxxx.jpg

now you can try pasting
http://www.mysite.com/photos/big/xxxxxxxx.jpg
to browser address line and see if it shows you a photo - if it does you have set it right.


Also, is there a place to insert a link back to my main website?

1.3RC will have this feature (headers).

[Greg M]

Thank you Pekka for your quick reply. I decided to just go ahead and install 1.3. I tried the upgrade and kept getting "the page can not be displayed". Since I didn't have anything setup that I was concerned about keeping I went ahead and erased everything, including the database. I installed 1.22 and did the upgrade right after. It worked perfectly. I guess that I must have messed up something in the Mysql database because I know that 1.3 wouldn't upgrade until I wiped out the old database and installed a fresh copy.

Dont' know if this info is useful or not, but I figured that I'd share it anyways.

[Pekka]

Greg M wrote:
Thank you Pekka for your quick reply. I decided to just go ahead and install 1.3. I tried the upgrade and kept getting "the page can not be displayed". Since I didn't have anything setup that I was concerned about keeping I went ahead and erased everything, including the database. I installed 1.22 and did the upgrade right after. It worked perfectly. I guess that I must have messed up something in the Mysql database because I know that 1.3 wouldn't upgrade until I wiped out the old database and installed a fresh copy.

Dont' know if this info is useful or not, but I figured that I'd share it anyways.

"the page can not be displayed" is not MySQL, PHP or EE error message but error message from server when a page has permission problems or its filename can not be found (e.g. out of www root folder).

But good to hear that you got it up and running.