Exhibit Engine 1.3 (update) Release Candidate [Archive]

Pekka

26th of October 2002 (Sat), 16:31

Feel free to try out Exhibit Engine 1.3 (update) Release Candidate.

http://photography-on-the.net/gallery/122to130RC.zip

It UPDATES Exhibit Engine 1.22.

See http://photography-on-the.net/gallery/whatsnew_130.html

Please do these steps:

1. Backup all 1.22 files you may have modified (originals can be redownloaded). Backup add/connect.php (although it is NOT overwritten by updated files). OLD INDEXSTYLES WILL BE OVERWRITTEN. ALL FILES HAVE CHANGED A LOT.

2. Close your current gallery by changing the name of its folder to something else so it can not be accessed.

for example: I have my EE at http://photography-on-the.net/gallery/

So I renamed it to http://photography-on-the.net/galleryX/ - then updated - and renamed it back to http://photography-on-the.net/gallery/

3. Copy all the files to the correct locations in the above mentioned Changed Gallery folder. Note that all files from folder "input" go to your renamed input folder.

4. As a safety measure you may want to be able to revert back to 1.22. So, set up EE Backup first: open backup/ee_backup_prefs/preferences.php (with NOTEPAD or equivalent text editor) and edit your own database info there. Use same data you have now in add/connect.php. Readme.txt explains more about file structure.

Again: set EE Backup's preferences first before running it. It needs to know you database name and pass.

If your current EE connect.php has:

-----------------------------
$servername = "localhost";
$databasename = "mydatabase";
$username = "myusername";
$password = "mypass";
-----------------------------

EE backup's preferences.php should have:

-----------------------------
// DATABASES

connect_menu ("localhost", "mydatabase", "myusername", "mypass", "100" );
-----------------------------

5. Chmod folder backup/ee_backup_files/ to 777 . This means in english that the EE backup's file backup directory needs full read/write permissions for OWNER, GROUP and OTHER.

PHP needs to have the folder owned by "nobody" in UNIX. For owner change use chown command from telnet. This is rarely needed, though.

Most ftp programs have a command for changing folder and file permissions. For example, I use WS_FTP Pro ftp client where you just select a folder and right click it to issue the chmod command.

See http://www.suncoastlug.org/permissions.html

6. Back up your current 1.22 database using EE Backup. Check that you have no CRC errors in backup. You may backup to a file, too and download it for extra safety.

Note: Backup is not completed when browser infobar says "done". EE will print a confirmation text to its own report area, wait for that to appear. Each database backup set is tagged COMPLETE or PARTIAL or INCOMPLETE. INCOMPLETE backups are defective (interrupted, timed out), PARTIAL contains only some of the tables (what you selected) and COMPLETE contains a full backup.

After a database backup (to database) you'll see a listing of database backup blocks with CRC.

EE backup is pretty easy to use: on the left hand side pane select command "Do backup from source db to both target db and file" and press "DO THE BACKUP". Then you can see on the right hand size a report of the backup. You can also view the actual data of the backup by selectÃ*ng the backup set, selecting a "display data method" from dropdown menu and pressing "display data".

You can dowload the file backup by selecting it from "restore file" list and clicking "download". EE Backup has tons of other commands, too, but you don't need to use them now.

7. Run the updater 122_to_130.php. When you see text "OK ZERO ERRORS" all was updated just fine.

8. Run Analyze/Repair tool from Utilities page.

9. Make one database backup and restore. Check that you restore the newest backup, not the old version! Backups are tagged by GMT date/time.

(step 9 will kick the MySQL indexes back to work among other things like getting rid of extra backslashes)

10. Rename changed gallery folder to original name.

That's it. Make sure you do ALL the steps above in correct order.

THIS IS A RELEASE CANDIDATE VERSION WHICH MEANS IT MAY STILL HAVE BUGS IN IT (although it is very thoroughly tested). PLEASE BACKUP YOUR DATA BEFORE INSTALLING.

All Misc. Settings will be preserved by the updater. You may want to change some settings (hide search, hide sorting...) as there are many new features in 1.3. All helps are not yet there (what a surprise). Run Analyze and Repair utility to make sure it's all together. If you have problems please report them back.

The header (fixed bar on top of the page) is freely editable (header.php), consider the included one as an example.

You can see 1.3 online at http://photography-on-the.net/gallery/index.php . I'll try to make a public editor demo later.

The internal online help works by placing the mouse over items on page - it works with Javascript and only browser so far which does not run it is Opera. Not all help items are written yet, but e.g. photo editor, misc settings, ee commerce and path editor helps are there.

EE backup has similar help system but it is activated and deactivated within EE Backup (it is a standalone version).

DATABASE STRUCTURE WILL NOT CHANGE ANY MORE, SO ALL FIXES TO RC WILL BE FILE-BASED.

All comments and questions are welcome.

PS. EE Commerce demo is at http://photography-on-the.net/gallery/photo.php?photo=1&exhibition=1 (click link below photo). The appearance and location of the "sell link" is not fixed yet. Also, there will be a "photos for sale" listing in output list etc.

seanspeng

26th of October 2002 (Sat), 21:28

Pekka,

That is a great news! We've been waiting so long and now too excited to upgrade it right away

Just a suggestion on the update instruction. I am a little concerned because the instruction is not very clear to me. Maybe it is very clear to anyone has web background.

#2: You mean to Change the name of "GALLERY" which contains all the EE files to something else? So that there will be no interruption when updating? And step 9 will change the name back to "GALLERY"?

for example: I have my EE at http://photography-on-the.net/gallery/

So I renamed it to http://photography-on-the.net/galleryX/ - then updated - and renamed it back to http://photography-on-the.net/gallery/

#3: You mean copy all the files to the correct locations in the above mentioned Changed Gallery folder?

Yes.

If I did some modification on my main index already, will it erase what I added before?

The index templates will be replaced by a new system. You may edit those, too. If you need help with that let me know.

#5 is not clear to me on what to do exactly.

Most ftp programs have a command for changing folder and file permissions. For example, I use WS_FTP Pro ftp client where you just select a folder and right click it to issue the chmod command

#6: How to use EE backup here? Where do I go?

After you have copied files you'll have EE Backup in input/backup/index.php

But set EE Backup's preferences first before running it. It needs to know you database name and pass.

EE backup is pretty easy to use: on the left hand side pane select command "Do backup from source db to both target db and file" and press "DO THE BACKUP". Then you can see on the right hand size a report of the backup. You can also view the actual data of the backup by selectÃ*ng the backup set, selecting a "display data method" from dropdown menu and pressing "display data".

You can dowload the file backup by selecting it from "restore file" list and clicking "download". EE Backup has tons of other commands, too, but you don't have to use them.

When I first setup 1.22, I dared to do anything because my EE has not been set up yet. Now with it running, I am afraid that I did anything wrong to ruin it.

If you do the backup of the version you are now using (both php files and database) you have no worries. I just updated my site with same procedure.

If you can kindly ADD some more explaination to your instruction list, that will be a great help. I may sound stupid, but I'll ask anyway.

I added the new info.

daddy0

27th of October 2002 (Sun), 04:44

I have little problems with URL's.

My domain name is forwarded using frames to other server (the real one containing all the data).

If I set in multieditor f.g. photo url for camera in form http://www.myserver.com/photos/camera.jpg it doesn't work. But if I use form http://www.realserver.com/~myaccount/photos/camera.jpg everything goes fine.

When I try with browser both ways work fine... Is this bug or feature?

Regards,

Mikko

ps. Pekka, you have done amazing job. Any idea of that Windows upload tool 's release date?

Pekka

27th of October 2002 (Sun), 06:27

Sean,

If you feel unsecure updating, just make a EE Backup's "file backup" of your current (1.22) EE database and mail it to me. I'll update it and send it back to you. Then all you need to do is restore the database and copy php files over old ones.

Pekka

Pekka

27th of October 2002 (Sun), 06:54

daddy0 wrote:
I have little problems with URL's.

My domain name is forwarded using frames to other server (the real one containing all the data).

If I set in multieditor f.g. photo url for camera in form http://www.myserver.com/photos/camera.jpg it doesn't work. But if I use form http://www.realserver.com/~myaccount/photos/camera.jpg everything goes fine.

When I try with browser both ways work fine... Is this bug or feature?

Hard to say. See the source code of the problem page to see what are the real URL's which EE has printed on html page.

Does multieditor show both URL's? Or do you see only one of them in gear.php?

Can you mail me a real URL to a camera image? I use normal URL's like http://photography-on-the.net/gallery/graphs/sigma14.gif which have always worked fine.

But there is still a function to be added to gear photos which converts spaces and special characters (all photos have that now).

ps. Pekka, you have done amazing job. Any idea of that Windows upload tool 's release date?

I have now TWO delevopers on it (one Windows and one Java) and they work on it together - perhaps the finished app will be Java only so Mac and UNIX users will be able to use it, too.

I have learned not to say any fixed release dates :) As with 1.3 it is better to deliver a stable and well-though product LATER, than release ASAP something that will need constant bug fixing.

When 1.3 will be released it will free my "resources" to code new features (1.3 is a BIG code update and acts as a steady foundation to all future improvements).

My next personal todo's will be:

- upload/resize which uses GD library. Useful for those who have it (and FTP) installed while waiting for standalone version. I have bought a new test server which has now all PHP bells and whistles installed for developement purposes.
- exhibition groups (nested exhibitions). This will most likely to be the first update and quite soon after 1.3 release.
- individual photo comments (and perhaps ratings).
- more styles

seanspeng

27th of October 2002 (Sun), 07:00

Pekka,

Thanks for your help.

1. For backup step, do I also need to backup all the photo files?

2. I particularly like one of the frames(style) which has a white pad and green frame (currently I am using). Can I keep that style and not overwrite with yours? I modified the original Dusk_1 and saved in that folder.

I am upgrading right now. Hopefully you will be there for a few minutes so I will ask you questions when I have difficulties.

Thanks,

seanspeng

27th of October 2002 (Sun), 08:01

I have done all the steps discribed. But I got this warning when I tried to open my page.

-------------------------------------------------

Warning: Failed opening './indexstyles/.php' for inclusion (include_path='./:/usr/local/lib/php') in /home/pengrus/pengrus-www/gallery/index.php on line 33

-----------------------------------------------------

Please help!

****I solved the problem by going into the editor and reselect the Index Style from the Misc Setting and Save changes. ********

It looks like working fine! I will post my add-ons for the procedure later. Thanks to Pekka.

Check here: http://www.pengrus.com/gallery/index.php

Pekka

27th of October 2002 (Sun), 09:59

seanspeng wrote:
I have done all the steps discribed. But I got this warning when I tried to open my page.

-------------------------------------------------

Warning: Failed opening './indexstyles/.php' for inclusion (include_path='./:/usr/local/lib/php') in /home/pengrus/pengrus-www/gallery/index.php on line 33

-----------------------------------------------------

Please help!

****I solved the problem by going into the editor and reselect the Index Style from the Misc Setting and Save changes. ********

Oops, that's a good finding. Thanks for pointing it out.

I have to fix the updater to force indexstyle 1. As you noticed the error comes because the database has some custom indexstyle value which is not there in the indexstyles folder. I could also do some code which would revert indexstyle automatically to default (1) if the chosen file was not found, just like the styles have now.

It looks like working fine! I will post my add-ons for the procedure later. Thanks to Pekka.

Check here: http://www.pengrus.com/gallery/index.php

Congrats!

PS. The music file there is definitely slowing down image download _initially_. You can see how EE builds (opens) the page really fast but the thumbnails appear quite slowly when the browser starts to load them to the page. Even when the browser has all thumbnails loaded the browser still loads something (the mp3). After it has loaded the music into cache it is really fast again.

Pekka

27th of October 2002 (Sun), 10:07

seanspeng wrote:
Pekka,

Thanks for your help.

1. For backup step, do I also need to backup all the photo files?

Generally it's a good idea can backup photo files but the update does not affect them in any way.

2. I particularly like one of the frames(style) which has a white pad and green frame (currently I am using). Can I keep that style and not overwrite with yours? I modified the original Dusk_1 and saved in that folder.

You can use your custom style files, just add them to the style list in style editor and then select and save them in exhibition editor.

Only change to style definition files in 1.3 is one new line in PHOTO PAGE section which changes color of the current microthumb in photo page's navigation microthumb list:

$s_photo_selected_microthumb_border_color = "000000"; // the 'current' microthumb's border color

If this value is not present EE uses other $s_photo_border_color instead so no harm done.

Pekka

27th of October 2002 (Sun), 10:32

Sorry for not noting this with 1.3RC announcement, but:

Note that EE backup _needs_ MySQL 3.23.20 or newer because it uses SHOW CREATE TABLE command found in that and later versions.

EE Backup has quite solid an internal check for the minimum version compatibility but I like to stress this requirement in case that check fails and you see a version below 3.23.20 on the right hand side info.

In any case it's always a good idea to update to the latest 3.23 series MySQL because they have done numerous bugfixes in new versions.

I did code a version which worked without SHOW CREATE TABLE but I decided not to use it because SHOW CREATE TABLE shows MySQL's own internal accumulated table creation data and so its the only correct, reliable, cross-version and safe way to rebuild table structures.

seanspeng

27th of October 2002 (Sun), 10:48

Thanks Pekka! I think I got it all working fine now. Some of my add-ons for the UPGRADE instruction:

On #4: "mydatabase" is the "Gallery Name", a little confusing here.

On #5: If you use WS_FTP, be sure to check the OWNER "read, write and EXECUTE"

Pekka: what about the GROUP and OTHER's permission? Same?

On #6: Run by going to your page: yourwebsite/gallery/input/backup/index.php

on #7: You need to scroll down to see "OK Zero errors" in a black box.

on #8: Where to run? Go to your page: yourwebsite/gallery/input/utils.php (assumed you changed your Gallery name back)

There are some files you are copying are older than the destination. I chose copy anyway.

And I am glad to report, the new 1.3 program improved my speed by more than 400%. It used to take 4-7 seconds to load one photo in Normal size, now it takes one second. I am so excited!!!

Hope this is helpful for others.

Thanks!

daddy0

27th of October 2002 (Sun), 11:55

Pekka wrote:
daddy0 wrote:
If I set in multieditor f.g. photo url for camera in form http://www.myserver.com/photos/camera.jpg it doesn't work. But if I use form http://www.realserver.com/~myaccount/photos/camera.jpg everything goes fine.

When I try with browser both ways work fine... Is this bug or feature?

Hard to say. See the source code of the problem page to see what are the real URL's which EE has printed on html page.

Does multieditor show both URL's? Or do you see only one of them in gear.php?

I can only see the "realserver" URL in gear.php.

Here is link to my exhibition, please test those Nova 2's in Accessories: http://www.mikkolevo.com/gallery/photo.php?photo=452&exhibition=5

As you probably notice the URL on browser will change automatically to following form when opening: http://www.estanet.fi/~mikkole/gallery/photo.php?photo=452&exhibition=5

Direct links to images used in Multieditor:
This one is OK: http://www.estanet.fi/~mikkole/gallery/photos/system/nv_2.gif
This one fails: http://www.mikkolevo.com/gallery/photos/system/nv_2.gif

I also found a NEW PROBLEM:

In Photo editor if I choose "[CREATE A NEW PHOTO FOR THIS EXHIBITION]" and then from next page "Return without selecting." a new blank photo is created. I suppose that is not the right way.

Pekka

27th of October 2002 (Sun), 12:12

Direct links to images used in Multieditor:
This one is OK: http://www.estanet.fi/~mikkole/gallery/photos/system/nv_2.gif
This one fails: http://www.mikkolevo.com/gallery/photos/system/nv_2.gif

I made a static web page which has only the plain image urls:

http://photography-on-the.net/gallery/test.html

And even then only the second URL was opened. So there is definitely some server redirect problem in your server which prevents images to show from short address. As you said you can reach the photo from browser address line. As you can not reach it from plain html page makes me think your server relies on http headers for redirecting and that fails when called from within a page.

I also found a NEW PROBLEM:

In Photo editor if I choose "[CREATE A NEW PHOTO FOR THIS EXHIBITION]" and then from next page "Return without selecting." a new blank photo is created. I suppose that is not the right way.

That is by design. Ugly but logical :)
I'll see later what can be done about it.

daddy0

27th of October 2002 (Sun), 12:41

Pekka wrote:
I made a static web page which has only the plain image urls:

And even then only the second URL was opened. So there is definitely some server redirect problem in your server which prevents images to show from short address. As you said you can reach the photo from browser address line. As you can not reach it from plain html page makes me think your server relies on http headers for redirecting and that fails when called from within a page.

Thank you for solving this for me. I guess I have to check if I should change service provider. Maybe some Finnish one this time (now I am using Namezero).

Mikko

Ps. Is there any possibility to have EE in Finnish? How about multi-lingual version where user can change language (or even autoselect based on browser settings)?

Scho

27th of October 2002 (Sun), 13:36

When I select Dusk Feel 2 style the frames appear broken around the image (as if gifs or jpgs for the frame are missing). This happens in both the style preview or on an actual image page. Did I make an error in uploading the files or is there another problem?

seanspeng

27th of October 2002 (Sun), 13:37

MULTIAREA NAVIGATION does not work on my EE. I remember that one thing is conflicting with this, but which one?

Thanks,

Scho

27th of October 2002 (Sun), 14:08

Scho wrote:
When I select Dusk Feel 2 style the frames appear broken around the image (as if gifs or jpgs for the frame are missing). This happens in both the style preview or on an actual image page. Did I make an error in uploading the files or is there another problem?
Sorry, my mistake - I forgot to upload the frames_1 folder - fixed now and all is working fine.

Pekka

27th of October 2002 (Sun), 14:55

seanspeng wrote:
MULTIAREA NAVIGATION does not work on my EE. I remember that one thing is conflicting with this, but which one?

Set Misc settings: "When image file is not found" to option 3

That option (and option 2) will enable image existence checker function which in turn will make multiarea navigation feature possible (it needs to know the image size in order to calculate the image map dynamically). Ain't that so logical? I just love programming :)

PS. I widened multiarea navigation areas by default so that it's easier to hit them - this means the center point (back to list) is a bit smaller.

seanspeng

27th of October 2002 (Sun), 15:46

Actually, I just noticed this Multiarea Navigation feature today! There are several times that I clicked your D30 Photos, I thought there are something mad happened! I never stopped to see what it says by the mouse. Your site is so fast! This is a great feature though!!!

Good to go! Hoo Ho!

seanspeng

27th of October 2002 (Sun), 22:13

I did not see a place to change the established Exhibition/Gallery name in the Editor.

Pekka

28th of October 2002 (Mon), 06:27

seanspeng wrote:
I did not see a place to change the established Exhibition/Gallery name in the Editor.

Just click the name and edit it. Same thing in photo editor.

Pekka

cdragut

29th of October 2002 (Tue), 06:48

First, thanks Pekka for your wonderful work! I upgraded to 1.3 without a glitch.

I have two questions:

- is EE Commerce going to be operational in the upcoming official final release ?
- Is it anyway to get rid of all comments undernith the displayed image (tried to set author, country, etc to no but they still show up)

Again, thank you.

Pekka

29th of October 2002 (Tue), 07:49

cdragut wrote:
First, thanks Pekka for your wonderful work! I upgraded to 1.3 without a glitch.

Good to hear!

- is EE Commerce going to be operational in the upcoming official final release ?

EE commerce is fully operational in 1.3RC. You need to edit the templates to match your own data (of edit them to match your needs in general, like email addresses etc.) and then use EE Commerce editor to add photos to each template.

To use Paypal you need to have a seller account in Paypal and you need to set taxes and shipping in their control panel, and for Shutterfly you need to do a C4P deal with them so that you get a share when people print through their services.

The mail template sends mail to me now, so you need to edit to the template your own existing mail accounts.

Is it anyway to get rid of all comments undernith the displayed image (tried to set author, country, etc to no but they still show up)

That's a bug.

To fix that change in photo.php edit line 1481

-------------
if ($ownername != "")
-------------

to

-------------
if ($ownername != "" && $ownername != "Unknown")
-------------

This will hide photographer info if photographer is "Unknown".

There are other things to code to hide Unknown from Javascript etc - full fix is on release version.

But I suggest that you do not use "Unknown" as photographer because all photos are copyrighted by someone and people do not always enter the gallery from front page.

Again, thank you.

You're welcome!

Pekka

seanspeng

29th of October 2002 (Tue), 09:17

Pekka,

How does the C4P work? I guess you have to upload the files (having the same name with the one displayed on your exhibition) to Shutterfly's web site? Then where there is an order, Shutterfly's system will match the files and process them?

How do you think Shutterfly's printing quality? I like to hear your opinion.

Thanks!

Pekka

29th of October 2002 (Tue), 11:32

seanspeng wrote:
Pekka,

How does the C4P work? I guess you have to upload the files (having the same name with the one displayed on your exhibition) to Shutterfly's web site? Then where there is an order, Shutterfly's system will match the files and process them?

http://www.shutterfly.com/business/c4p.jsp

EE commerce contains "EE Commerce path" which you select for each photo for each template. This path+imagename is what is sent to Shutterfly as "original" image URL. EE commerce paths are normal size paths, but it is good to separate them at least in thought because they act for different purposes.

Shutterfly then retrieves the image when they are going to print it. So the image is not send there, just its address.

Note: As Shutterfly needs photo URL and URL must be send by html form the URL is viewable by all. I'm studying URL encrypting techniques but I suspect that with services like Shutterfly they are not accepted as valid URL's.

How do you think Shutterfly's printing quality? I like to hear your opinion.

I have not used their services. I'm sure there are many others here who can comment Shutterfly.

seanspeng

29th of October 2002 (Tue), 11:37

Pekka wrote:

http://www.shutterfly.com/business/c4p.jsp

EE commerce contains "EE Commerce path" which you select for each photo for each template. This path+imagename is what is sent to Shutterfly as "original" image URL. EE commerce paths are normal size paths, but it is good to separate them at least in thought because they act for different purposes.

Shutterfly then retrieves the image when they are going to print it. So the image is not send there, just its address.

Sounds good. But that'll eat up my own space pretty quickly by storing the files for printing and maybe slowdown the loading speed with much bigger files. I will not be able to afford it.

Pekka

29th of October 2002 (Tue), 12:09

seanspeng wrote:
Sounds good. But that'll eat up my own space pretty quickly by storing the files for printing and maybe slowdown the loading speed with much bigger files. I will not be able to afford it.

You can always deliver the originals from some other server than you gallery server. That's the whole beauty of the size path system.

Which reminds me of one easy security method for keeping others out of your original files: you can set Apache's directory (with .htaccess directives) to accept requests from certain hosts only. If you know the host name Shutterfly uses to retrieve the images you can allow only that one host to enter a specific folder so no one else can touch those photos :)

Maybe some Apache gurus can tell if this indeed will work.

cdragut

29th of October 2002 (Tue), 14:06

seanspeng wrote:
Pekka,

How do you think Shutterfly's printing quality? I like to hear your opinion.

Thanks!

I found them to be one of the best. Worth giving a try, at least...

Harold

29th of October 2002 (Tue), 15:02

Hi Pekka,

Great work and thank you!
I would like to let you know that the upgrade from 1.22 to 1.30RC was easy and without any problems. Your upgrade instructions were perfectly clear to me.

My first impression is that with version 1.30RC, EE is a very robust and fully featured system. For me it's nearly perfect, except for some (minor) things:

1) It's a pity one can't set accessories or categories in the default photo data

2) The HTML code generated by EE does not completely conform to current HTML specifications. For instance, the first line of all generated pages (even before the tag) should be like:

Further there are some other (minor) non-conformities.
Maybe you would like to have a look at http://validator.w3.org/
On that page you can enter the URL of one of your EE gallery pages and let the validator analyse the generated HTML code. Any errors will then be reported.

cdragut

29th of October 2002 (Tue), 16:50

Pekka wrote:

EE commerce is fully operational in 1.3RC. You need to edit the templates to match your own data (of edit them to match your needs in general, like email addresses etc.) and then use EE Commerce editor to add photos to each template.

To use Paypal you need to have a seller account in Paypal and you need to set taxes and shipping in their control panel, and for Shutterfly you need to do a C4P deal with them so that you get a share when people print through their services.

The mail template sends mail to me now, so you need to edit to the template your own existing mail accounts.

Thanks Pekka...but I have one more problem. I tried with no success to identify in what template is the "Demo" on the paypal page generated.
How du I get rrd of it?!
(I have a paypal seller acount already)
Thanks,

Pekka

30th of October 2002 (Wed), 05:52

Harold wrote:
Hi Pekka,

Great work and thank you!
I would like to let you know that the upgrade from 1.22 to 1.30RC was easy and without any problems. Your upgrade instructions were perfectly clear to me.

My first impression is that with version 1.30RC, EE is a very robust and fully featured system. For me it's nearly perfect, except for some (minor) things:

1) It's a pity one can't set accessories or categories in the default photo data

I'll add this to todo list.

2) The HTML code generated by EE does not completely conform to current HTML specifications. For instance, the first line of all generated pages (even before the tag) should be like:

Further there are some other (minor) non-conformities.
Maybe you would like to have a look at http://validator.w3.org/
On that page you can enter the URL of one of your EE gallery pages and let the validator analyse the generated HTML code. Any errors will then be reported.

I have of course used validators while developing, but normally I leave doing final html fixes to the release version.

I fixed now photo.php on my site and added experimental DTD which accepts nobr tags, too (from Jukka Korpela). The rest of the errors from W3C could be taken care if suitable DTD could be generated (accept URL variables, quotes escaped within Javascript, some TD and BODY tag attributes).

See

http://validator.w3.org/check?uri=http%3A%2F%2Fphotography-on-the.net%2Fgallery%2Fphoto.php%3Fphoto%3D448%26exhi bition%3D1&charset=%28detect+automatically%29&doctype=Inline

and

http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fphotography-on-the.net%2Fgallery%2Fphoto.php%3Fphoto%3D448%26exhi bition%3D1&warnings=yes&input=yes

cdragut

30th of October 2002 (Wed), 11:52

cdragut wrote:

Thanks Pekka...but I have one more problem. I tried with no success to identify in what template is the "Demo" on the paypal page generated.
How du I get rrd of it?!
(I have a paypal seller acount already)
Thanks,

Nevermind. Stupid oversight. I was looking to modify a php file before realizing it's done thru the admin menu.

aviceda

30th of October 2002 (Wed), 13:36

Hi Pekka,

Look forward to trying out the new release soon, just a quick question.
Is there a way to display an indexed list of images for each exhibition? I've had some feedback that it would be a good idea for my site as it contains images of birds.

See http://www.aviceda.org/gallery

Tom

Pekka

30th of October 2002 (Wed), 14:07

aviceda wrote:
Hi Pekka,

Look forward to trying out the new release soon, just a quick question.
Is there a way to display an indexed list of images for each exhibition? I've had some feedback that it would be a good idea for my site as it contains images of birds.

See http://www.aviceda.org/gallery

Tom

Perhaps you could tell in more detail what kind of a list you'd need to produce. As I understand it now all list outputs ( http://www.aviceda.org/gallery/list.php ) are essentially "indexed list of images".

aviceda

30th of October 2002 (Wed), 15:09

Hi Pekka
Just wondering if you can show image files as a text list without thumbnails.
For example: If I were to put up a list of all the birds of SE Qld and hyper-link the available EE images, currently the URL links are huge.....just wondered if you had a facility in EE 1.3 to do this easily.
Also can I use EE as a module in Post-Nuke?
Tom

aviceda

31st of October 2002 (Thu), 02:41

Hi Again Pekka,

Am currently working my way thru your updater and am having problems when I get to EE Utilities
The menu appears but I get this error
Warning: Failed opening '../slashwork.php' for inclusion (include_path='.:/usr/local/lib/php') in /home/aviceda/public_html/galleryx/input/index.php on line 10

(I've backed up the entire EE1.22 on my hard-disk)

Tried to get EE backup to run but get this error
Warning: Unknown MySQL Server Host 'SERVERNAME' (2) in /home/aviceda/public_html/galleryx/input/backup/index.php on line 448

Warning: MySQL Connection Failed: Unknown MySQL Server Host 'SERVERNAME' (2)

in /home/aviceda/public_html/galleryx/input/backup/index.php on line 448

Should I try and run the updater 122_to_130.php or wait until the other issues are fixed?

Tom

Pekka

31st of October 2002 (Thu), 05:02

aviceda wrote:
Hi Again Pekka,

Am currently working my way thru your updater and am having problems when I get to EE Utilities
The menu appears but I get this error
Warning: Failed opening '../slashwork.php' for inclusion (include_path='.:/usr/local/lib/php') in /home/aviceda/public_html/galleryx/input/index.php on line 10

Tom,

Check that you indeed have slashwork.php and root.php on your gallery root folder.

If they are there and you still get the error, there is a deactivated "include path setting" in line 12 of fetchsettings.php:

-------------
// ini_set ("include_path",".:/home/pathtosites/mysite/mywebroot/mygallery/myfolder/");
-------------

remove the commenting from the beginning of that line and edit it to have you system path to the gallery root folder, e.g.

-------------
ini_set ("include_path",".:/home/aviceda/public_html/galleryx/");
-------------

Tried to get EE backup to run but get this error
Warning: Unknown MySQL Server Host 'SERVERNAME' (2) in /home/aviceda/public_html/galleryx/input/backup/index.php on line 448

Warning: MySQL Connection Failed: Unknown MySQL Server Host 'SERVERNAME' (2)

in /home/aviceda/public_html/galleryx/input/backup/index.php on line 448

Open backup/ee_backup_prefs/preferences.php and edit your data into it. See backup/readme.txt for more info. Basically the data you need to edit there is same data you have in you EE's connect.php

Server name is usually "localhost".

Should I try and run the updater 122_to_130.php or wait until the other issues are fixed?

If you can make EE backup work and you can make a successfull backup of your EE 1.22 database, why not.

NOTE: EE backup can use several databases at the same time. If you 1.22 is in database called "gallery" and 1.3 is at "gallery_new" you can insert both databases into EE Backup's preferences and you can make backup from the old gallery by selecting its database as source database. Of you can make a new database "backups" and use that for all backups.

Just keep notes or write comments which backup is for 1.22 and which for 1.3, as you should not restore over different versions.

Paulhuang

2nd of November 2002 (Sat), 05:47

Hi Pekka,

Does this upgrade instructions work for EE 1.1 to 1.3 or do I have to upgrade to 1.22 first?

Thanks,

Paul

Pekka

2nd of November 2002 (Sat), 07:11

paulhuang wrote:
Hi Pekka,

Does this upgrade instructions work for EE 1.1 to 1.3 or do I have to upgrade to 1.22 first?

Thanks,

Paul

The update is only from 1.22 to 1.3, sorry.

Paulhuang

3rd of November 2002 (Sun), 00:20

Hi Pekka,

Thanks for the info. That means I have to either start from scratch or upgrade to 1.22 and then to 1.3.

Keep up the good work.

Cheers,
Paul

aviceda

6th of November 2002 (Wed), 00:26

Hi Pekka,

Had a break for a few days, managed to get some spare time and ran install again from scratch, using your guidelines. Everything seems OK and galleries look fine but when I tried to run EE Backup, got this one:

Warning: Unknown MySQL Server Host 'SERVERNAME' (2) in /home/aviceda/public_html/gallery/somethingodd/backup/index.php on line 448

Warning: MySQL Connection Failed: Unknown MySQL Server Host 'SERVERNAME' (2) in /home/aviceda/public_html/gallery/somethingodd/backup/index.php on line 448

I'm using the same details in preferences.php as I used in connect.php so I'm not too sure what's wrong with the database, I've "chmod" the ee_backup_files folder to 777 so I'm unsure what to do next, please take a look at http:/www.aviceda.org/gallery/
and see if you can see any obvious errors.

Tom

Pekka

6th of November 2002 (Wed), 03:46

aviceda wrote:
Hi Pekka,

Had a break for a few days, managed to get some spare time and ran install again from scratch, using your guidelines. Everything seems OK and galleries look fine but when I tried to run EE Backup, got this one:

Warning: Unknown MySQL Server Host 'SERVERNAME' (2) in /home/aviceda/public_html/gallery/somethingodd/backup/index.php on line 448

Warning: MySQL Connection Failed: Unknown MySQL Server Host 'SERVERNAME' (2) in /home/aviceda/public_html/gallery/somethingodd/backup/index.php on line 448

I'm using the same details in preferences.php as I used in connect.php so I'm not too sure what's wrong with the database, I've "chmod" the ee_backup_files folder to 777 so I'm unsure what to do next, please take a look at http:/www.aviceda.org/gallery/
and see if you can see any obvious errors.

Tom

"Unknown MySQL Server Host 'SERVERNAME' " means there is still server "SERVERNAME" in preferences.php.
Perhaps you added your server to the list, and did not just edit the default server. Check that preferences.php has only one "connect_menu" line (or one line for each MySQL database you use).

aviceda

6th of November 2002 (Wed), 04:36

Hi Pekka,
Thanks, for some reason my preferences.php was saving the old data rather than with mine after I'd changed it. (not sure why though)
Also most of the 'big' images in Samsonvale exhibition had been deleted from the folder on the server (again not sure how!)
Unfortunately we are not quite there yet, I can run the backup/restore utility but cannot edit individual photos.
Whenever I click on one it takes me to an html "page not found"
Any ideas?
Tom

Pekka

6th of November 2002 (Wed), 05:33

aviceda wrote:
Hi Pekka,
Thanks, for some reason my preferences.php was saving the old data rather than with mine after I'd changed it. (not sure why though)
Also most of the 'big' images in Samsonvale exhibition had been deleted from the folder on the server (again not sure how!)

EE can not delete any photos from server. There is simply no code for it in it.

Unfortunately we are not quite there yet, I can run the backup/restore utility but cannot edit individual photos.
Whenever I click on one it takes me to an html "page not found"
Any ideas?
Tom

Mail me how I can access your editors and I'll have a look. You could try uploading all editor files there again (except backup folder).

aviceda

7th of November 2002 (Thu), 04:01

Hi Pekka,
Thanks for the advice, the problems turned out to be of my own making!
Ftp'ing the wrong files to the "output" folder is something to watch out for! Maybe the "output" folder in the "Input" directory could be renamed to avoid confusion?
Anyway all is functioning well and available for viewing at http://www.aviceda.org/gallery
Thanx again,
Tom

vandermerwede

24th of November 2002 (Sun), 01:31

Pekka,

I upgraded to 1.3 RC and am having a problem. I can access the main page, utils.php appears to be working normally, but when I try to access multieditor, exhibition editor, or any from the menu at the top of the util page I get this error:

Fatal error: Call to undefined function: ee_stripslashes() in /home/editoria/public_html/gallery/fetchsettings.php on line 48

even if I try to run these programs directly the same error appears. flashwork.php and toroot.php are both in the root directory.

Any help will be appreciated.

George

vandermerwede

24th of November 2002 (Sun), 03:54

Never mind, I got it. the input folder didn't copy right.

Thanks
George

henkbos

25th of November 2002 (Mon), 03:55

Guess I'm a lucky one. Version 1.22 is still not up and running. Can I install 1.3 without hassles (meaning everything without the upgrade notes)?

miro

25th of November 2002 (Mon), 14:59

I have trouble updating. This is what I get:

UPDATER 1.22 -> 1.3

Dumping 1.3 SQL data

MySQL version:3.23.39

DATABASES AVAILABLE:
....
mzdb (EE USES THIS DATABASE)
....

Old settings saved

Access denied for user: 'miromici@masis.digitronicweb.com' to database 'mzdb'
ERROR IN QUERY:
DROP TABLE IF EXISTS ee_accessory

kingPhoto

8th of March 2003 (Sat), 21:30

I have tried 8 times to get the update to work. I get this error when running index.php from the gallery directory.

Fatal error: Call to undefined function: ee_stripslashes() in /usr18/home/rjking/public_html/gallery/indexstyles/1.php on line 24

What is up?

Thanks for your help.

-Royce

Solved--- FTP did not copy over some files. I deleted the files in indexstyles and reloaded and all is fine.

chriz

13th of March 2003 (Thu), 11:34

I installed version1.22
then upgraded to 1.3
Everythings seems normal but
when i open patheditor (or other editors) it is impossible to update the fields.
Whenever I click update, the previous values are restored.

going into php-myadmin I got this message
Database db_photoplus_es running on mysql1.opsion.fr
PMA Database ... not OK[ Documentation ]
General relation features Disabled

could it have something to do with this ???

Chriz, Belgium

Pekka

13th of March 2003 (Thu), 16:13

chriz wrote:
I installed version1.22
then upgraded to 1.3
Everythings seems normal but
when i open patheditor (or other editors) it is impossible to update the fields.
Whenever I click update, the previous values are restored.

going into php-myadmin I got this message
Database db_photoplus_es running on mysql1.opsion.fr
PMA Database ... not OK[ Documentation ]
General relation features Disabled

could it have something to do with this ???

Chriz, Belgium

That error message by MyAdmin is not relevant (it is of no concern).

It may be that you do not have all privileges to the database. You'll need

Select Insert Update Delete Create Drop Alter

to use EE. If EE does not give any error messages or mysql error messages then the problem is somewhere else. You are the first to report a problem like this.

Let me know if you can't fix it (or your server admin/support can't).

chriz

14th of March 2003 (Fri), 01:37

When I run PHPMyAdmin I'm able to change the fields.
I could update the URL's in ee_thumb_path, ee_photo_size and ee_microthumb_path with no problem.
However, once those values are changed, I cannot alter them using patheditor.
PathEditor does not generate a message: After clicking UPDATE ALL SIZE PATHS, it simply reloads.
the other pages do the same thing.

Even when I was installing the upgrade, after clicking "I AGREE", the page was simply reloading and nothing happened. (I solved that by hard-coding the variable $do to the value "agree", so it bypassed the condition)

As I have only three days of experience using PHP,mySQL I do not see how to solve this problem yet.

Maybe you can assist me further.
Chriz

PS: does this message help you further ? I get this while updating af field in ee_settings.

Request-URI Too Large
The requested URL's length exceeds the capacity limit for this server.

request failed: URI too long

Apache/1.3.24 Server at php1.opsion.fr Port 80

Pekka

14th of March 2003 (Fri), 05:59

chriz wrote:
When I run PHPMyAdmin I'm able to change the fields.
I could update the URL's in ee_thumb_path, ee_photo_size and ee_microthumb_path with no problem.
However, once those values are changed, I cannot alter them using patheditor.
PathEditor does not generate a message: After clicking UPDATE ALL SIZE PATHS, it simply reloads.
the other pages do the same thing.

Even when I was installing the upgrade, after clicking "I AGREE", the page was simply reloading and nothing happened. (I solved that by hard-coding the variable $do to the value "agree", so it bypassed the condition)

This is surely related to problem. Perhaps the update was not successfull (1.3RC is update on 1.22 only).

PS: does this message help you further ? I get this while updating af field in ee_settings.

Request-URI Too Large
The requested URL's length exceeds the capacity limit for this server.

request failed: URI too long

Apache/1.3.24 Server at php1.opsion.fr Port 80

Yes it tells a reason why your EE does not save data.

This message means that your server is configured to accept less POST data (than by default 8190 bytes which is sufficient for most applications) and thus rejects EE's form sending - this will explain why it does not save anything. It seems that your server admin has for some reason edited directive LimitRequestLine (see http://www.apache.org/docs/mod/core.html#limitrequestline ) and that should be brought back to default (at least) to make things work.

See also http://perlmonks.thepen.com/30474.html

There is also a similar directive in PHP.ini "post_max_size" (usually set to 8M) but I think your issue is purely Apache's problem.

chriz

14th of March 2003 (Fri), 07:13

I believe the update was succesfull as I got the message zero errors (or something like that)
also the tables seem to be installed/modified correctly.

As far as this limitrequestline is concerned, my admin will set it to 16380

Still wondering why these pages continue reloading with original settings:
EXAMPLE:
In path editor you can select:
all path editors on one page
size path editor
thumb path editor, etc...

When I select for example size path editor, the page reloads with all path editors on one page.

there must be something else going on.

BTW, I use zonealarm and switched it off to see if that had to do with it, but no.

chriz

14th of March 2003 (Fri), 11:41

Hello Pekka,

Just wanted to add that the connection to the database is working, so that is not the problem.

I deleted the D-30 exhibition and a backup was automatically generated (UNIQUE PHOTO BACKUP).
The field FREE TEXTUAL INFO displays Backup of unique ...

So the problem still remains.

Pekka, did you receive the link I send you to my input folder and would you find the time to go there and see for yourself?
Would be much obliged.

Anyways, enjoy your friday evening, I will too

chriz, Belgium

chriz

17th of March 2003 (Mon), 03:34

Hello,

I have not yet figured out why I cannot update the paths in patheditor:
When pressing UPDATE ALL SIZE PATHS, the page refreshes with the original values.
Modifying the database directly using phpMyAdmin does work, but I guess that can't be the intention.

I would be very happy if I could get EE to work, it looks like a pretty neat way to put my photo on the internet, but I'm struggling with it.

Anybody had this problem?

Help,
Chriz, Belgium

Pekka

17th of March 2003 (Mon), 09:20

chriz wrote:
Hello,

I have not yet figured out why I cannot update the paths in patheditor:
When pressing UPDATE ALL SIZE PATHS, the page refreshes with the original values.
Modifying the database directly using phpMyAdmin does work, but I guess that can't be the intention.

I would be very happy if I could get EE to work, it looks like a pretty neat way to put my photo on the internet, but I'm struggling with it.

Anybody had this problem?

Help,
Chriz, Belgium

Chriz,

I checked you EE and it seems that your server totally ignores all POST data the browser is sending. It accepts GET data which means e.g. adding new exhibition works (as the command is send using GET) but virtually all other commands in EE fail because the server fails to obey them, or it loses POST data completely.

Possibly your Apache is configured to reject POST messages.

So, to solve this you should tell about this behaviour to your system admin - to patch your server accept POST is the only way to make things work there. You can easily test it with e.g. style editor - click "ADD NEW STYLE" button. If a new style info line is not created, not other editor will work either.

chriz

17th of March 2003 (Mon), 09:46

thanks Pekka, I just contacted the server-people and they will check it out.

I'll let you know what happens.

Chriz, Belgium

NetButch

27th of March 2003 (Thu), 21:23

UPdate seems successful, with one exception.

I am getting tons of style info as headers.. actually above the header... any idea what file I edit to get rid of the code that is showing?

here is the link so you can see whats happening.

http://cmwphotography.us/gallery/index.php

thanks for your great program. I will be paying you soon!

Butch

Pekka

28th of March 2003 (Fri), 03:52

netbutch wrote:
UPdate seems successful, with one exception.

I am getting tons of style info as headers.. actually above the header... any idea what file I edit to get rid of the code that is showing?

here is the link so you can see whats happening.

http://cmwphotography.us/gallery/index.php

Hi Butch,

The code you see is PHP code printed out (no

NetButch

28th of March 2003 (Fri), 06:06

I was afraid you might say that... I modified the index code in hopes of getting rid of the style stuff that was showing. I figured its Php code, and there is a missing tag.. but I cant find where its missing... I have re-installed the files, getting rid of my modifications, and its still showing up. this code is also showing on my Exhibition Editor pages (which have never been modified), the list.php page, photo.php page, etc.. which leads me to believe its part of a style. but when I seach the style code in notepad, I cant even find text that matches the junk showing on the web pages.. still hoping you can help.

thanks,
Butch

NetButch

28th of March 2003 (Fri), 06:18

Okay,
I think I solved the problem. I will detail my thoughts to perhaps help others in the future, and for your notes too Pekka.

I orginally used MS Frontpage for engine 1.22. when I uploaded the new 1.3 RC I used FTP.

Well.. MS Frontpage creates a folder in every foler you have (named _vti_cnf) which also holds a copy of just about every file you make.

So, I never went back and updated those _vit_cnf files, I just installed all the new 1.3RC files. When viewing the new files in web browser, IE was pulling some information from the old _vti_cnf folders...

the fix: simple.. DELETE the _vti_cnf folders before you update your 1.3RC.

thanks again Pekka for a great program.

Butch

chwong

15th of April 2003 (Tue), 06:50

Hi Pekka,

I tried to edit the layout of index.php with the MISC. SETTINGS. However, no matter how I tried, I cant seem to enlarge the font size of the header, and the borders just dont seem to appear. The number of microthumbs also do not seem to corresponds to what I have listed in MISC. SETTINGS.

My gallery is at http://www.muakmuak.com/egallery

Regards

Pekka

15th of April 2003 (Tue), 07:40

chwong wrote:
Hi Pekka,

I tried to edit the layout of index.php with the MISC. SETTINGS. However, no matter how I tried, I cant seem to enlarge the font size of the header, and the borders just dont seem to appear. The number of microthumbs also do not seem to corresponds to what I have listed in MISC. SETTINGS.

My gallery is at http://www.muakmuak.com/egallery

Regards

Hi,

Seem like you have 1.22 index page code there. Make sure you have uploaded ALL 1.3RC files, including full contents of indexstyles folder.

Pekka

chwong

15th of April 2003 (Tue), 08:19

Pekka wrote:
Hi,

Seem like you have 1.22 index page code there. Make sure you have uploaded ALL 1.3RC files, including full contents of indexstyles folder.

Pekka

Pekka, thanks for your reply. It is my mistake. The correct URL is http://www.muakmuak.com/ephoto/

When I select 3 microthumbs to appear in the index page, there are still 7 shown under D30 in the index page.

Also despite selecting ouput format no. 1 with borders, I didnt see any borders.

Pekka

15th of April 2003 (Tue), 11:54

I still don't see 1.3 index page. Make sure you have uploaded _ALL_ 1.3RC files, including full contents of indexstyles folder. Now your ephoto/indexstyles/ folder contains 1.22 php code, which means 1.3RC can not adjust index page.

So, open 1.3RC install package and upload indexstyles folder with all its contents to server. This will fix your problem.

chwong

16th of April 2003 (Wed), 01:10

Pekka wrote:
I still don't see 1.3 index page. Make sure you have uploaded _ALL_ 1.3RC files, including full contents of indexstyles folder. Now your ephoto/indexstyles/ folder contains 1.22 php code, which means 1.3RC can not adjust index page.

So, open 1.3RC install package and upload indexstyles folder with all its contents to server. This will fix your problem.

Hi Pekka, I have uploaded the whole of indexstyles folder with all its contents to the server, but the problem still persist.

Also, the index.php shows that it is running on a EE1.3.

Or do you suggest that I uninstall everything and start from scratch again?

Sorry for the trouble.

Pekka

16th of April 2003 (Wed), 14:39

chwong wrote:
Pekka wrote:
I still don't see 1.3 index page. Make sure you have uploaded _ALL_ 1.3RC files, including full contents of indexstyles folder. Now your ephoto/indexstyles/ folder contains 1.22 php code, which means 1.3RC can not adjust index page.

So, open 1.3RC install package and upload indexstyles folder with all its contents to server. This will fix your problem.

Hi Pekka, I have uploaded the whole of indexstyles folder with all its contents to the server, but the problem still persist.

Also, the index.php shows that it is running on a EE1.3.

Or do you suggest that I uninstall everything and start from scratch again?

Sorry for the trouble.

Version number is retrieved from database - it is not fixed to files.

I'm sorry to repeat, I am pretty sure the place you upload files is not the same as the www outputs on browser. I've seen this on Cobalt servers - they have confusingly two www roots and only one is online.

If you still have problems, mail me ftp address, username and pass to pekka@photography-on-the.net and I'll see that your installation is correct and upload what is needed.

Evanrich

11th of May 2003 (Sun), 04:43

Whenever i try to get into my editor after updating to 1.3, i get the following message...

Fatal error: Call to undefined function: ee_stripslashes() in /home/modelxpo/public_html/gallery/fetchsettings.php on line 48

anyone know what causes this? please help, as i cannot edit anything anymore, i can just view the index and thats it...

Sincerely,

Evan Richardson

you can email me directly at evan@modelxposure.com

Thanks

Evanrich

11th of May 2003 (Sun), 04:43

perry_mr

22nd of July 2003 (Tue), 19:32

Hi Pekka,

Your Exhibit Engine is fantastic!!

I have version 1.22 installed on my Windows XP system running Apache and MySQL.

I'm tryiing to upgrade to the new 1.3 version, but everytime I run the 122_to_130.php script I get the message "No action taken. You have version 1.0. This updater works only on EE 1.22"

Can you please tell me what I'm doing wrong.

Thank you.

Mark

Pekka

23rd of July 2003 (Wed), 18:13

perry_mr wrote:
Hi Pekka,

Your Exhibit Engine is fantastic!!

I have version 1.22 installed on my Windows XP system running Apache and MySQL.

I'm tryiing to upgrade to the new 1.3 version, but everytime I run the 122_to_130.php script I get the message "No action taken. You have version 1.0. This updater works only on EE 1.22"

Can you please tell me what I'm doing wrong.

Thank you.

Mark

Hi Mark,

Installer checks for table 'ee_settings' for correct version number. It must be 1.22 or the installer won't continue.

Have you modified the database with e.g. PhPMyAdmin tool?

One possible hack:

Try changing line (556)

if ($ver=="1.22") {

to

print "Current EE version is " . $ver;
if ($ver=="1.22") {

And when you run it again you should see your version before error message. To hack the installer to work with your version is possible by changing line

if ($ver=="1.22") {

to

if ($ver=="1.22beta") {

or whatever you have there, but running update installer hacked like this may likely ruin the database.

Let me know what version you had, and we'll see what can be done.

perry_mr

23rd of July 2003 (Wed), 21:05

Pekka,

Thank you for your response. I tried you suggestion and discovered that the $ver variable was returning an empty string. To make a long story short, I finally discovered that the connect.php script was missing from the "add" directory. I copied the one from the 1.22 directory and ran the update again, and everything was OK.

Now I can explore the new version. Thanks very much for your help.

Regards,

Mark

msbc

30th of July 2003 (Wed), 07:17

Pekka,

I'm going through the upgrade from 1.22 to 1.3. I'm at step 9 - Backup and Restore. When I invoke EE Backup from the Utilities page I get the message:

You need at least MySQL version 3.23.20 to use this software. You are currently using version 4.0.13.

msbc

30th of July 2003 (Wed), 08:19

msbc wrote:
Pekka,

I'm going through the upgrade from 1.22 to 1.3. I'm at step 9 - Backup and Restore. When I invoke EE Backup from the Utilities page I get the message:

You need at least MySQL version 3.23.20 to use this software. You are currently using version 4.0.13.

I found the 1.6 update in another message and I can now get to the Backup page. When I try and backup to a file I see a heap of 'Access denied for user:" messages at the top of the screen - each preceeded by a table name. I did update the preferenes.php file to be the same values as my connect.php. I also get an output file approx 68k in size (I have not added to the clean 1.22 install before doing the upgrade) - so I'm not sure if the backup worked or not???

Pekka

30th of July 2003 (Wed), 08:34

msbc wrote:
msbc wrote:
Pekka,

I'm going through the upgrade from 1.22 to 1.3. I'm at step 9 - Backup and Restore. When I invoke EE Backup from the Utilities page I get the message:

You need at least MySQL version 3.23.20 to use this software. You are currently using version 4.0.13.

I found the 1.6 update in another message and I can now get to the Backup page. When I try and backup to a file I see a heap of 'Access denied for user:" messages at the top of the screen - each preceeded by a table name. I did update the preferenes.php file to be the same values as my connect.php. I also get an output file approx 68k in size (I have not added to the clean 1.22 install before doing the upgrade) - so I'm not sure if the backup worked or not???

This must be a directory permission thing. Go with any ftp program to you EE backup dir and give chmod 0777 command to "ee_backup_files" directory using either manual input or dialogs for issuing the chmod.

msbc

30th of July 2003 (Wed), 17:33

Pekka,

It's not a file issue - I had 0777 on the directory - the messages relate to DB access i.e.
"lock ee_accessory: Access denied for user: 'usernamehere@localhost' to database 'dbnamehere'

I've replaced the real db and user name values in the above message, but they are correct. The preferences.php file has the same values as in my connect.php file.

If I do a backup to DB (target DB = source DB) I also see "lock ee_backup WRITE: Access denied for user" messages to the database.

Since this 1.3 upgrade was to a new install of 1.22 I didn't do the backup in step 6, but the 122_to_130.php ran fine with the OK ZERO ERRORS message so my db access should be fine?

Any suggestions? Maybe I should wipe the whole install and start again? Whats the latest full install version of EE so I don't need to go through an upgrade?

ADDITIONAL INFO:

I tried a new 1.5B1 install and I'm seeing the same messages. The DB install ran fine but when I go to setup FTP servers I see "get_message_lock: Access denied for user: 'myuserid@localhost' to database 'mydb'" in the FTP Message area.

On the 'Auto Optimze' output I see each db table listed as follows:
'ee_accessory' LOCK FAILED.
'ee_accessory' ...............OPTIMIZE TABLE successfull.

Could this be related to my hosting servers systems? System info that may be useful:
O/S: RedHat
PHP: 4.3.2
MySQL: 4.0.13
Perl: 5.008

Thanks,
Mark

This problem has been solved by having my hosting provider add lock priviliges to my DB user.