Exhibit Engine 2 upgrade instructions

[Pekka]

Download from http://photography-on-the.net/forum/showthread.php?t=223287
For first two weeks the download link is available for forum users only.

Upgrading to version 2.0

System requirement change is that EE 2.0 requires PHP version 4.1.0 or later. MySQL 4 or later is recommended. Upgrade works only on untampered EE databases. ALSO NOTE THAT EE 2 REQUIRES MYSQL LOCK PRIVILEGES. Consult your server admin if you have these requirements set or not.

Upgrade should done by following basic scheme, aiming for maximum data safety and easy recover of old installation in case of problems. If you do not understand the instructions, ask more information. Do not perform the upgrade unless you know how to do all these steps.
Make file backup of your EE database and download the file.
Unzip EE upgrade packet locally.
Edit PRIMARY SETTINGS section of "basecode/SETUP_settings.php" locally: insert current add/connect php database connection info, edit $ee_ident and $s_admin_path.
Rename current EE folder on your server to something else.
Create new folder EE2 on server.
Upload all EE 2.0 files and folders to server folder EE2. MAKE SURE YOU USE ASCII TRANSFER FOR ALL PHP FILES!
Rename admin folder to what you set $s_admin_path to.
Set permissions inside admin folder to 777 (world writeable) for these folders only:
admin/temp
admin/UPLOAD
admin/UPLOAD/ee_temp_upload
admin/UPLOAD/test
If you had photo or thumb folders inside EE program folder, copy those photo and thumb folder to EE2 folder.
Browse to updater script http://www.yourserver.com/eegallery/upgrade/upgrade.php and perform upgrade.
If all went fine, browse to your server folder EE2 and see that you see EE index page (without exhibitions - this is normal).
rename EE2 folder to your original EE folder name.If you got errors during upgrade (anything in red color), copy them and post in http://photography-on-the.net/forum/forumdisplay.php?f=94 . Before you retry upgrade, you must clean all tables and restore old EE database.

After upgrade you should also upload your custom watermark photos back to watermark folder. Not also that EE Backup .php files has also been upgraded, but the preferences file is identical format so there is no need to upgrade that.

For the hasty ones, a simple quick method, if you have backups of all, is to delete all EE related files and folders in your gallery folder EXCEPT PHOTOS AND THUMBS, and upload all EE 2 files there. Then edit "basecode/SETUP_settings.php", set permissions and start the upgrade.

It is important that you delete all old EE's .php files and folders. Leaving them on server might be a security risk.

Delete upgrade folder after succesful upgrade.



Loggin in to admin area (editor)

Address to your EE's admin area is http://www.yourdomain.com/youEEgalleryfoldername/yourEEadminfoldername/

Admin folder name should be set in "basecode/SETUP_settings.php".
Default login is

username: admin
pass: pass

After upgrade use your old logins. If EE sees that you have either of the default login strings, it will urge you to change them ASAP and it is wise to do so: well chosen name of your EE admin folder, well chosen admin username and well chosen admin pass build together a firewall which will block out unwanted visitors who try to hack into your EE.



First things to do in editor after upgrade

After upgrade EE 2 will not show any exhibitions or groups in public area, this is not an error. Your group id 1 has been moved to end of group list and group id 1 is now called INDEX.

What you need to do now is to create a site structure and give users permissions to exhibitions. User public is "all those who are not logged in". You do not have to assign any exhibitions to public view if you want to keep your galleries fully private.

The editor must be used with a modern web browser that has Javascript on. I recommend latest Firefox.

Adding user permission to view exhibitions:

1. Click on the top left: "daily" or "all" to show editor menus we need.
2. On the left menu click item: "User editor"
3. See that username"public" is selected (i.e. in inverse color), then select all exhibitions you want to show for those who are not logged in. Keep CTRL key down when selecting, this way you can add to or remove from selection.
4. Click "save user".

Creating EE site structure:

1. On the left menu click item: "Structure".
2. In structure editor
- click in GROUP column: "INDEX"
- CTRL-select in "CONTAINS EXHIBITIONS" column those exhibitions you want to show on index page
- click "SAVE THIS GROUP"

You can see below a Structure Viewer a tree view how public users will see their EE.

Now you see public exhibitions on EE index page and all data they have. Some counters show zero, they will update to correct amount in few of minutes time.

Updating photo size database:

1. Click on the top left: "setup" or "all" to show editor menus we need.
2. On the left menu click item: "Retrieve Photo Sizes".
3. Select display filter: "only photos with some unset/zero size",
4. Select photos (better to do this few dozen at a time).
5. Hit "start". On next screen you have a option to continue to next photo ro continue nonstop.

Do this procedure until all photo sizes are stored. Now you can change in "basecode/SETUP_settings.php" variable
$s_use_notavailable = "1";
This enables all features in EE which use photo size data (defaul photo size, missing photo image, thumbsize limiters, multiarea navigation...). On upload EE stores photo sizes automatically.



All EE 1.5 settings are preserved on upgrade. Nevertheless it is adviced to check out main settings:

1. Click on the top left: "setup" or "all" to show editor menus we need.
2. On the left menu click item: "FTP servers".
- do ftp test and verify that all works. Choose EE internal FTP ENGINE for maximum features.
3. On the left menu click item: "Server tools".
- do each test and verify that the needed apps work. The paths and settings should be same as before upgrade.
4. On the left menu click item: "Paths".
- check that each path has correct ftp server chosen (if you did changes to ftp servers above).
5. On the left menu click item: "Resize methods".
- check that they work and settings are what works for you. If you had IMAGICK resizemethods, they are now changed to IMAGEMAGICK.
6. On the left menu click item: "Global settings".
- make sure that "HTTP address (URL) to gallery" is correct.
7. On the left menu click item: "Install check".
- wait for the check to complete and look at the results.

[segal3]

'Exhibition Order' isn't saving, nor displaying the correct order even based on the current numbering - may have gotten it to work by resorting with 'Reset to selected' and then reordering, but it rounds everything to the tens (no matter if i put in order as #17 or #23, it'll change it to whatever fits between, so if there was a #20 and a #30, then the #30->#40, and then #23->#30. Weird.

[Ewan]

Upgrade works only on untampered EE databases.

I've added a handful of text fields to the ee_photo table to display extra information on the photo pages. Is this likely to cause problems with the upgrade?

Thanks.

[GvdM]

For some unknown reason my 1.5 rc4 database doesn't have the ee_backup and ee_backup_info tables. So obviously they do not exist in my 2.0 upgrade.

Can someone post the schema for these two tables so I can create them myself?

Thanks in advance.

[Pekka]

For some unknown reason my 1.5 rc4 database doesn't have the ee_backup and ee_backup_info tables. So obviously they do not exist in my 2.0 upgrade.

Can someone post the schema for these two tables so I can create them myself?

Thanks in advance.

If you open EE Backup it will create those tables for the target database that is selected.

[Pekka]

I've added a handful of text fields to the ee_photo table to display extra information on the photo pages. Is this likely to cause problems with the upgrade?

Thanks.

No, I don't think so.

[Ewan]

Thanks for the prompt reply Pekka. I bit the bullet and did the upgrade. All data seems intact :D

Phew!

[afterburn]

Thanks Pekka for all the work, upgrade went smoothly and quickly, without any problems.

[Pekka]

I have moved problem reports not related to actual upgrade process into http://photography-on-the.net/forum/forumdisplay.php?f=99

[GvdM]

If you open EE Backup it will create those tables for the target database that is selected.

I get this:

Unable to connect to the selected database server at this time
PLEASE PRESS REFRESH ON YOUR BROWSER TO TRY AGAIN.
Why do you get this error? Maybe because:

The database server has not been activated for you domain
your username/password is wrong.
The database server in offline for some reason.
The server name is incorrect.
Server firewall rejects the connect.If you get this error, contact your server administrator and check if MySQL is indeed running on your server. This error message can also mean that the MySQL server is overloaded - can easily happen in shared hosting where 250 sites fight for one CPU and same system resources.
(Info by EE Backup)

Server: localhost
Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

Everything else is working fine....

[::John::]

Pekka,

1. Make file backup of your EE database and download the file.

Being the sort of person I am, I opened and read the downloaded file.

Towards the bottom there were a LOT of lines like:

INSERT INTO `ee_uncookied` VALUES ('529', '}‘Qn… EWão£bk_Ût
d”QHyoà³võ¥†¦?:9÷Ì*b—¦óŸª±þ÷üS¶íg2»/+ö+4Ah2R„ŸR
Ê)º%*
ëJ»T:P:hÊã:zú`ùÀ}##RolM*@ÃmN�Åyrö˜?
Má¼¼¿&ï^Ð,0c¥«³(qïz\"sµÅ¢ê2¹E0£ä†¶bÐ:ó³Ã¯qtœV·¬.ÉOAur½¶X‰U_X„8Áª³3â3[2î<O{<*òE’£‡£àJü‘È÷;§iú/â®p;ç<9«þí', '1')|EE|BACKUP|

I decided that it wasn't prudent to procede any further until I could see a clean backup so I went into the admin section of my gallery and ran the Purge Uncookied Data in Server Info.

I performed another backup to file and downloaded it. It was clean.

I am wondering, if people are going to be rushing to upgrade their galleries, how many other people may have a backup with similar issues, whether those issues would produce problems when restoring (if necessary) and whether they aren't taking some unwitting risk with their desire to upgrade?

I suspect I may be completely wrong but would appreciate some clarification.

Thanks,
John

[Pekka]

I get this:

Unable to connect to the selected database server at this time
PLEASE PRESS REFRESH ON YOUR BROWSER TO TRY AGAIN.
Why do you get this error? Maybe because:

The database server has not been activated for you domain
your username/password is wrong.
The database server in offline for some reason.
The server name is incorrect.
Server firewall rejects the connect.If you get this error, contact your server administrator and check if MySQL is indeed running on your server. This error message can also mean that the MySQL server is overloaded - can easily happen in shared hosting where 250 sites fight for one CPU and same system resources.
(Info by EE Backup)

Server: localhost
Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

Everything else is working fine....

Edit admin/backup/ee_backup_prefs/preferences.php

[GvdM]

Edit admin/backup/ee_backup_prefs/preferences.php

Perfect.....

Did I miss those edit instructions somewhere?????

Thanks Pekka

[Pekka]

Perfect.....

Did I miss those edit instructions somewhere?????

Thanks Pekka

I missed them so you missed them :)

[gillyworld]

I missed them so you missed them :)

I think You also need to set the permissions on the ee_backup_files folder as well in order to do a backup.

Alan

[Faustini]

Hi!

This is the only error I got after upgrade:

"alter ee_backup_info ...... Table 'name-of-database.ee_backup_info' doesn't exist"

I guess that's why I have never used EE's backup command before (my server doesn't allow me, only in CGI mode). Should I worry about it? I mean, will it cause any further problems in the structure or functioning of my gallery?

Thanks!

[Pekka]

Hi!

This is the only error I got after upgrade:

"alter ee_backup_info ...... Table 'name-of-database.ee_backup_info' doesn't exist"

I guess that's why I have never used EE's backup command before (my server doesn't allow me, only in CGI mode). Should I worry about it? I mean, will it cause any further problems in the structure or functioning of my gallery?

Thanks!

No that should not be a problem. EE Backup creates its tables if they do not exist.

[GvdM]

No that should not be a problem. EE Backup creates its tables if they do not exist.

That is directly relatd to my problem that we fixed. Edit admin/backup/ee_backup_prefs/preferences.php

[Faustini]

May we apply to EE version 2.0 the same language files we used in version 1.5 RC 4? I did it, but I noted that some buttons and drop-down menus have no text... As more contents were added in version 2, I guess we'll need updated language files, won't we?

Thanks for now, as always.

[Pekka]

May we apply to EE version 2.0 the same language files we used in version 1.5 RC 4? I did it, but I noted that some buttons and drop-down menus have no text... As more contents were added in version 2, I guess we'll need updated language files, won't we?

Thanks for now, as always.

Sorry for forgetting to mention this. All language data has been moved to global.php in each language folder. There is also custom.php loaded where you can add your own customisations.

You can see in Install Checker if the language keys are found and if files are there.

If you have e.g. Italy language from 1.5, basically you can copy all old language strings to languages/ita/global.php, then run in install check to see what more you need. Or the most correct way is to open languages/eng/global.php and build a new language to a new file line by line from old data.

I'll add all contributed language files for download here.

[Pekka]

Added "ALSO NOTE THAT EE 2 REQUIRES MYSQL LOCK PRIVILEGES" to instructions.

[Faustini]

Or the most correct way is to open languages/eng/global.php and build a new language to a new file line by line from old data.

I'll add all contributed language files for download here.

Hi again! As a contribution, I'll work on the translation of the english language files into brazilian portuguese, OK? In time:

1 - May I include the " (quote) character in comment lines (//)?

2 - How to insert quotes in the text of translated sentences (so PHP doesn't interpret the first one as the one that is ending the "tag")? For example:

$translated["custom_footer"] = "Thanks for being here in my "digital nestle"!";

3 - Sugestion: what about starting a "Language translations" thread? ;)

Peace,

Faustini

[Pekka]

Hi again! As a contribution, I'll work on the translation of the english language files into brazilian portuguese, OK? In time:

[QUOTE]1 - May I include the " (quote) character in comment lines (//)?

Yes.

2 - How to insert quotes in the text of translated sentences (so PHP doesn't interpret the first one as the one that is ending the "tag")? For example:

$translated["custom_footer"] = "Thanks for being here in my "digital nestle"!";

Add a slash before the quote:

"Thanks for being here in my \"digital nestle\"!"

3 - Sugestion: what about starting a "Language translations" thread? ;)

Will do soon. Thanks!

[Faustini]

Still:

1 - What's the "$s_charset" (ISO #) to brazilian portuguese?

2 - How do I set the item "setlocale (LC_TIME , "english");"?

3 - May I use [ ]s and ( )s in the text of the sentences? For example:

make_flash ("\"fill\" (preenchimento)");

Sincerely,

Faustini

[Pekka]

Still:

1 - What's the "$s_charset" (ISO #) to brazilian portuguese?

ISO 8859-1 should work ok.

2 - How do I set the item "setlocale (LC_TIME , "english");"?

use

"setlocale (LC_TIME , "portuguese");"

or

"setlocale (LC_TIME , "pt_BR");"

or

"setlocale (LC_TIME , "pt_BR.iso-8859-1");"

This setting affects only the date and time setting in EE 2 "Global Settings", when you select "Preferred date representation of current language" choices.

3 - May I use [ ]s and ( )s in the text of the sentences? For example:

make_flash ("\"fill\" (preenchimento)");

yes.

[hbeumer]

During the upgrade procedure I encountered the following errors. The error can be reproduced (after restore of database backup).

Upgrading from 1.5RC4 to 2.0
PHP version 5.1.4
MySQL version 5.0.22
MySQL lock privileges are set

Upgrade log follows:
-----------------------------------------------------------------------
DROP TABLE IF EXISTS `ee_uncookied` ...... OK
CREATE TABLE `ee_uncookied` ...... OK
DROP TABLE IF EXISTS `ee_uncookied_settings` ...... OK
DROP TABLE IF EXISTS `ee_message` ...... OK
DROP TABLE IF EXISTS `ee_message` ...... OK
CREATE TABLE `ee_message` ...... OK
DROP TABLE IF EXISTS `ee_link_to_group` ...... OK
CREATE TABLE `ee_link_to_group` ...... OK
DROP TABLE IF EXISTS `ee_error` ...... OK
CREATE TABLE `ee_error` ...... OK
DROP TABLE IF EXISTS `ee_login` ...... OK
CREATE TABLE `ee_login` ...... OK
DROP TABLE IF EXISTS `ee_order_to_group` ...... OK
CREATE TABLE `ee_order_to_group` ...... OK
DROP TABLE IF EXISTS `ee_order_to_link` ...... OK
CREATE TABLE `ee_order_to_link` ...... OK
DROP TABLE IF EXISTS `ee_resultcache` ...... OK
CREATE TABLE `ee_resultcache` ...... OK
DROP TABLE IF EXISTS `ee_session` ...... OK
CREATE TABLE `ee_session` ...... OK
DROP TABLE IF EXISTS `ee_shorthand` ...... OK
CREATE TABLE `ee_shorthand` ...... OK
DROP TABLE IF EXISTS `ee_structure_cache` ...... OK
CREATE TABLE `ee_structure_cache` ...... OK
DROP TABLE IF EXISTS `ee_structure_lang_cache` ...... OK
CREATE TABLE `ee_structure_lang_cache` ...... OK
DROP TABLE IF EXISTS `ee_thumb_size` ...... OK
CREATE TABLE `ee_thumb_size` ...... OK
DROP TABLE IF EXISTS `ee_upload_folder` ...... OK
CREATE TABLE `ee_upload_folder` ...... OK
DROP TABLE IF EXISTS `ee_uploader_cache` ...... OK
CREATE TABLE `ee_uploader_cache` ...... OK
DROP TABLE IF EXISTS `ee_user` ...... OK
CREATE TABLE `ee_user` ...... OK
DROP TABLE IF EXISTS `ee_viewerstyle` ...... OK
CREATE TABLE `ee_viewerstyle` ...... OK
DROP TABLE IF EXISTS `ee_frame` ...... OK
CREATE TABLE `ee_frame` ...... OK
DROP TABLE IF EXISTS `ee_debug_timer` ...... OK
CREATE TABLE `ee_debug_timer` ...... OK
DROP TABLE IF EXISTS `ee_debug_report` ...... OK
CREATE TABLE `ee_debug_report` ...... OK
DROP TABLE IF EXISTS `ee_prevnext_cache` ...... OK
CREATE TABLE `ee_prevnext_cache` ...... OK
DROP TABLE IF EXISTS `ee_style_template` ...... OK
CREATE TABLE `ee_style_template` ...... OK
DROP TABLE IF EXISTS `ee_group` ...... OK
CREATE TABLE `ee_group` ...... OK
DROP TABLE IF EXISTS `ee_group_eng` ...... OK
CREATE TABLE `ee_group_eng` ...... OK
DROP TABLE IF EXISTS `ee_link` ...... OK
CREATE TABLE `ee_link` ...... OK
DROP TABLE IF EXISTS `ee_group_to_group` ...... OK
CREATE TABLE `ee_group_to_group` ...... OK
DROP TABLE IF EXISTS `ee_batch_cache` ...... OK
CREATE TABLE `ee_batch_cache` ...... OK
DROP TABLE IF EXISTS `ee_style` ...... OK
CREATE TABLE `ee_style` ...... OK
DROP TABLE IF EXISTS `ee_admin_log` ...... OK
DROP TABLE IF EXISTS `ee_settings` ...... OK
DROP TABLE IF EXISTS `ee_settings` ...... OK
CREATE TABLE `ee_settings` ...... OK
INSERT INTO ee_uncookied_settings () VALUES () ...... OK
INSERT INTO `ee_order_to_group` (index group order) ...... OK
ALTER TABLE `ee_size` (add ee_size_protected) ...... OK
ALTER TABLE `ee_photo_size` (add index ee_photo_id) ...... OK
ALTER TABLE `ee_photo_size` (add ee_viewerstyle_id) ...... OK
ALTER TABLE `ee_photo_size` (add ee_viewerstyle_use_vars) ...... OK
ALTER TABLE `ee_photo_size` (add ee_viewerstyle_vars) ...... OK
ALTER TABLE `ee_photo_size` (add ee_size_x) ...... OK
ALTER TABLE `ee_photo_size` (add ee_size_y) ...... OK
ALTER TABLE `ee_photo_size` (add ee_size_bytes) ...... OK
ALTER TABLE `ee_photo_size` (add ee_size_filename) ...... OK
ALTER TABLE `ee_photo_size` (add index ee_size_id) ...... OK
ALTER TABLE `ee_photo_size` (add index ee_viewerstyle_id) ...... OK
ALTER TABLE `ee_news` (add ee_news_photo_id) ...... OK
ALTER TABLE `ee_news` (add ee_news_exhibition_id) ...... OK
INSERT INTO `ee_viewerstyle` (insert VIEWERSTYLE_default.php) ...... OK
INSERT INTO `ee_viewerstyle` (insert VIEWERSTYLE_flash.php) ...... OK
INSERT INTO `ee_viewerstyle` (insert VIEWERSTYLE_pt_panorama.php) ...... OK
INSERT INTO `ee_viewerstyle` (insert VIEWERSTYLE_pt_crypt.php) ...... OK
INSERT INTO `ee_viewerstyle` (insert VIEWERSTYLE_win_media.php) ...... OK
ALTER TABLE `ee_resizemethod` (change ee_resizemethod_usm_amount) ...... OK
INSERT DEFAULT TEMPLATE DATA ...... OK
ALTER TABLE `ee_exhibition` (add ee_exhibition_is_virtual) ...... OK
ALTER TABLE `ee_exhibition` (add ee_exhibition_virtual_parameters) ...... OK
ALTER TABLE `ee_exhibition` (add ee_exhibition_indexlink) ...... OK
ALTER TABLE `ee_exhibition` (add ee_exhibition_indexlink_active) ...... OK
INSERT INTO `ee_group` (INDEX group) ...... OK
INSERT INTO `ee_group_eng` (INDEX group) ...... OK
INSERT INTO `ee_group` (move old index group) ...... OK
INSERT INTO `ee_order_to_group` (move old index group) ...... OK
INSERT INTO `ee_group_eng` (move old index group) ...... OK
INSERT INTO `ee_link` (default links) ...... OK
INSERT INTO `ee_link` (default links) ...... OK
INSERT INTO `ee_link` (default links) ...... OK
INSERT INTO `ee_link` (default links) ...... OK
INSERT INTO `ee_link` (default links) ...... OK
INSERT INTO `ee_link` ...... OK
INSERT INTO `ee_link` (default links) ...... OK
DROP TABLE IF EXISTS `ee_link_eng` ...... OK
CREATE TABLE `ee_link_eng` ...... OK
INSERT INTO `ee_link_eng` (default links) ...... OK
INSERT INTO `ee_link_eng` (default links) ...... OK
INSERT INTO `ee_link_eng` (default links) ...... OK
INSERT INTO `ee_link_eng` (default links) ...... OK
INSERT INTO `ee_link_eng` (default links) ...... OK
INSERT INTO `ee_link_eng` (default links) ...... OK
INSERT INTO `ee_link_eng` (default links) ...... OK
INSERT INTO `ee_order_to_link` (default links) ...... OK
INSERT INTO `ee_order_to_link` (default links) ...... OK
INSERT INTO `ee_order_to_link` (default links) ...... OK
INSERT INTO `ee_order_to_link` (default links) ...... OK
INSERT INTO `ee_order_to_link` (default links) ...... OK
INSERT INTO `ee_order_to_link` (default links) ...... OK
INSERT INTO `ee_order_to_link` (default links) ...... OK
INSERT INTO `ee_link_to_group` (default links) ...... OK
INSERT INTO `ee_link_to_group` (default links) ...... OK
INSERT INTO `ee_link_to_group` (default links) ...... OK
INSERT INTO `ee_link_to_group` (default links) ...... OK
INSERT INTO `ee_link_to_group` (default links) ...... OK
INSERT INTO `ee_link_to_group` (default links) ...... OK
INSERT INTO `ee_link_to_group` (default links) ...... OK
ALTER TABLE `ee_exhibition_to_group` DROP INDEX ...... OK
ALTER TABLE `ee_exhibition_to_group` DROP INDEX ...... OK
ALTER TABLE `ee_exhibition_to_group` CHANGE ...... OK
UPDATE `ee_exhibition_to_group` ...... OK
ALTER TABLE `ee_exhibition_to_group` ADD INDEX ...... OK
ALTER TABLE `ee_exhibition_to_group` ADD INDEX ...... OK
INSERT INTO `ee_frame` (example frame passepartout_4) ...... OK
INSERT INTO `ee_frame` (example frame passepartout_3) ...... OK
INSERT INTO `ee_frame` (example frame passepartout_2) ...... OK
INSERT INTO `ee_frame` (example frame passepartout_1) ...... OK
INSERT INTO `ee_frame` (example frame passepartout_5) ...... OK
INSERT INTO `ee_frame` (example frame passepartout_6) ...... OK
INSERT INTO `ee_frame` (example frame plain_1) ...... OK
INSERT INTO `ee_frame` (example frame dark_1) ...... OK
INSERT INTO `ee_frame` (example frame rosy_1) ...... OK
INSERT INTO `ee_batch_cache` ...... OK
INSERT INTO `ee_batch_cache` ...... OK
ALTER TABLE `ee_photo_size` ...... OK
DROP TABLE IF EXISTS `ee_size_custom_menutext_eng` ...... OK
CREATE TABLE `ee_size_custom_menutext_eng` ...... OK
ALTER TABLE `ee_ftp` (drop ee_ftp_servertype) ...... OK
ALTER TABLE `ee_ftp` (drop ee_ftp_idletime) ...... OK
ALTER TABLE `ee_ftp` (add ee_ftp_nobuffer) ...... OK
ALTER TABLE `ee_counter` (drop ee_counter_group) ...... OK
ALTER TABLE `ee_debug_report` (change ee_debug_pagewasrun) ...... OK
ALTER TABLE `ee_exhibition` (drop ee_exhibition_pass) ...... OK
ALTER TABLE `ee_exhibition_feedback` (change ee_exhibition_feedback_timestamp) ...... OK
ALTER TABLE `ee_exhibition_feedback` (add ee_exhibition_feedback_user_agent) ...... OK
ALTER TABLE `ee_exhibition_feedback` (add ee_exhibition_feedback_ip) ...... OK
ALTER TABLE `ee_exhibition_feedback` (add ee_exhibition_feedback_checksum) ...... OK
ALTER TABLE `ee_exhibition_feedback` (change ee_exhibition_feedback_name) ...... OK
ALTER TABLE `ee_news` (change ee_news_photo_id) ...... OK
ALTER TABLE `ee_order_to_exhibition` (drop index ee_photo_id) ...... OK
ALTER TABLE `ee_order_to_exhibition` (drop index ee_exhibition_id) ...... OK
ALTER TABLE `ee_order_to_exhibition` (add multi index) ...... OK
ALTER TABLE `ee_order_to_exhibition` (add multi index) ...... OK
ALTER TABLE `ee_owner` (drop index ee_country_id) ...... OK
ALTER TABLE `ee_owner` (drop index ee_location_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_photo_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_light_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_counter_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_country_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_location_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_workflow_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_lens_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_owner_id) ...... OK
ALTER TABLE `ee_photo` (drop index ee_camera_id) ...... OK
ALTER TABLE `ee_photo` (drop ee_photo_foo) ...... OK
ALTER TABLE `ee_photo_comment` ...... OK
ALTER TABLE `ee_photo_comment` ...... OK
ALTER TABLE `ee_photo_eng` (drop index ee_photo_id) ...... OK
ALTER TABLE `ee_photo_to_accessory` (add index ee_photo_id) ...... OK
ALTER TABLE `ee_photo_to_accessory` (add index ee_accessory_id) ...... OK
ALTER TABLE `ee_photo_to_exhibition` (drop index ee_photo_id) ...... OK
ALTER TABLE `ee_photo_to_exhibition` (drop index ee_exhibition_id) ...... OK
ALTER TABLE `ee_photo_to_exhibition` (add index ee_photo_id) ...... OK
ALTER TABLE `ee_resizemethod` (drop ee_resizemethod_safetynet) ...... OK
ALTER TABLE `ee_session` (change ee_login_session_id) ...... OK
ALTER TABLE `ee_session` (add index ee_login_session_id) ...... OK
INSERT INTO `ee_upload_folder` (base row) ...... OK
ALTER TABLE `ee_uploader_cache` ...... OK
ALTER TABLE `ee_uploader_cache` (change ee_uploader_data) ...... OK
INSERT INTO `ee_uploader_cache` (user public) ...... OK
ALTER TABLE `ee_user` (add ee_user_totalcount_cache) ...... OK
ALTER TABLE `ee_user` (add ee_user_totalcount_cache_update) ...... OK
ALTER TABLE `ee_user` (add ee_user_totalcount_cache_timestamp) ...... OK
INSERT INTO `ee_style` default styles ...... OK
DROP TABLE IF EXISTS `ee_exhibition_group_eng` ...... OK
ALTER TABLE `ee_photo_to_exhibition` (add index ee_exhibition_id) ...... OK
UPDATE `ee_exhibition` (all styles to 1) ...... OK
INSERT INTO ee_settings () VALUES () ...... OK
TRUNCATE TABLE ee_performance (remove stale data) ...... OK
INSERT INTO `ee_resizemethod` (netpbm thumb slot) ...... OK
INSERT INTO `ee_resizemethod` (netpbm microthumb slot) ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
UPDATE table comment ...... OK
ALTER TABLE `ee_settings_eng` ...... Lost connection to MySQL server during query
ALTER TABLE `ee_settings_eng` ...... MySQL server has gone away
UPDATE table comment ...... MySQL server has gone away
UPDATE table comment ...... MySQL server has gone away
UPDATE table comment ...... MySQL server has gone away
UPDATE table comment ...... MySQL server has gone away
UPDATE table comment ...... MySQL server has gone away
UPDATE table comment ...... MySQL server has gone away
CHANGE ee_exhibition ...... MySQL server has gone away
DROP `ee_simplenavigation_search` ...... MySQL server has gone away
DROP `ee_simplenavigation_sort` ...... MySQL server has gone away
DROP `ee_simplenavigation_perpage` ...... MySQL server has gone away
ALTER TABLE `ee_exhibition` CHANGE `ee_detaillist_1` ...... MySQL server has gone away
ALTER TABLE `ee_exhibition` CHANGE `ee_detaillist_2` ...... MySQL server has gone away
DROP `ee_activate_links_list` ...... MySQL server has gone away
restore some of the old settings ...... MySQL server has gone away
UPDATE `ee_group` ...... MySQL server has gone away
UPDATE `ee_group` ...... MySQL server has gone away
UPDATE `ee_group` ...... MySQL server has gone away
ALTER TABLE `ee_admin` ...... MySQL server has gone away
INSERT INTO `ee_batch_cache` ...... MySQL server has gone away
INSERT INTO `ee_batch_cache` ...... MySQL server has gone away
fixing category tables... .....FINISHED.
update ee_list_perpage ...... MySQL server has gone away
alter ee_photo_exif_shutter ...... MySQL server has gone away
update ee_photo_for_www yes ...... MySQL server has gone away
update ee_photo_for_www no ...... MySQL server has gone away
alter ee_photo_for_www ...... MySQL server has gone away
update ee_settings ee_installed_gd ...... MySQL server has gone away
update ee_settings ee_installed_imagick ...... MySQL server has gone away
alter ee_backup_info ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter ee_detaillist_1 defaults ...... MySQL server has gone away
alter ee_detaillist_2 defaults ...... MySQL server has gone away
alter ee_photodetailrow ...... MySQL server has gone away
alter ee_photo ...... MySQL server has gone away
update ee_version number to 2.0 ...... MySQL server has gone away

[Pekka]

This probably means your mysql has quite short connect timeout value.

One solution (untested) is changing ee_install function in upgrade.php line 345 to


function ee_install ($query,$name,$report="1") {
global $servername;
global $username;
global $password;
global $databasename;
global $ee_mysql_connection;
// test connection
$test = mysql_query("SELECT 1+1");
if (!$test) {
include ($toroot . "basecode/SCRIPT_connect.php");
}
$update = mysql_query($query);
if ($report == "1") {
ee_error ($update,$query,$name);
}
if ($update) {
print "<br><b>" . $name . "</b> ...... <span style=\"color: #00BB00;\">OK</span>";
}
if (!$update) {
print "<br><b>" . $name . "</b> ...... <span style=\"color: #FF0000;\">" . mysql_error() . "</span>";
}
flush();
return;
}


Other option is to add reconnect code


@mysql_close();
include ($toroot . "basecode/SCRIPT_connect.php");


to line 3508

Please let me know if either one helped.

[tommykjensen]

Ok ran the upgrade and everything went fin until the point of updating the photosize database.

When I select a few photos and click on start the page refresh partially and stops.

Then if I click on all in the top to get the menu again and click on retrieve photo sizes again. Then I can click on continue last batch and some photos are processed. Then there is the option to click on next photo or continue nonstop. If I click on next photo the same happens with the partial page refresh. But if I click on continue nonstop one photo is processed.

I am using IE6.

114907

[tommykjensen]

Ok forget above. I just updated with the files for 2.01 which I thought was in the original zipfile. Now the page refreshed correctly and continue automatically when clicking on continue nonstop.

[tommykjensen]

How do I get the batch photo size checker to continue for more than 30 seconds a time?

My php timeout is set to 6000 seconds


From server info
PHP maximum script execution time: 6000 seconds

[Pekka]

PHP timeout affects only on batch page at a time. Do you have problems running a batch?

[tommykjensen]

Not any more. I think the 2.01 update fixed it. The strange thing was that when I choose ftp the script in batch stopped after 30 seconds but when choosing http it continued. So I just finished updating all photos.

[Pekka]

In some servers the ftp login takes ages (usually misconfiguration of ftp server) - other option is that your EE home ftp was not set up correctly.

In any case I think I'll make http the default method.

[hbeumer]

No, Pekka, neither of these solutions helped. I treid adding reconnects at some other place, but with no result.

The error always starts at the same place: upgrade.php lines 3844-3845:

$query = "ALTER TABLE {$q}ee_settings_{$language}{$q}ee_indexlink{$q} {$q}ee_indexlink{$q} VARCHAR( 255 ) DEFAULT 'INDEX'";

[hbeumer]

This probably means your mysql has quite short connect timeout value.

One solution (untested) is changing ee_install function in upgrade.php line 345 to ......

Other option is to add reconnect code ....

Please let me know if either one helped.

No, Pekka, neither of these solutions helped. I tried adding reconnects at some other place, but with no result.

Connection timeout of MySQL is set to 60 seconds which should me more than enough.

The error always starts at the same place: upgrade.php lines 3844-3845:

$query = "ALTER TABLE {$q}ee_settings_{$language}{$q}ee_indexlink{$q} {$q}ee_indexlink{$q} VARCHAR( 255 ) DEFAULT 'INDEX'";

[Pekka]

No, Pekka, neither of these solutions helped. I treid adding reconnects at some other place, but with no result.

The error always starts at the same place: upgrade.php lines 3844-3845:

$query = "ALTER TABLE {$q}ee_settings_{$language}{$q}ee_indexlink{$q} {$q}ee_indexlink{$q} VARCHAR( 255 ) DEFAULT 'INDEX'";

Can you see in e.g. phpmyadmin what value MySQL wait_timeout has? It should be more than 7200 usually.

Also value max_allowed_packet is interesting.

I'll try to make you a split upgrader.

[hbeumer]

Can you see in e.g. phpmyadmin what value MySQL wait_timeout has? It should be more than 7200 usually.

Also value max_allowed_packet is interesting.

I'll try to make you a split upgrader.

wait timeout = 28800
max allowed packet = 16776192

I'm not sure timeout is the problem since the error always occurs with the exact same query. Becasue of some error during the query, the connection seems to be reset, causing all following queries to fail(??)

When I remove these two queries in lines 3844-3847 (in fact the whole while looop part), the upgrade goes on, to crash somewhere further on:

ALTER TABLE `ee_exhibition` CHANGE `ee_detaillist_1` ...... OK
ALTER TABLE `ee_exhibition` CHANGE `ee_detaillist_2` ...... OK
DROP `ee_activate_links_list` ...... OK
restore some of the old settings ...... OK
UPDATE `ee_group` ...... OK
UPDATE `ee_group` ...... OK
UPDATE `ee_group` ...... OK
ALTER TABLE `ee_admin` ...... OK
INSERT INTO `ee_batch_cache` ...... OK
INSERT INTO `ee_batch_cache` ...... OK
fixing category tables... .....FINISHED.
update ee_list_perpage ...... MySQL server has gone away
alter ee_photo_exif_shutter ...... MySQL server has gone away
update ee_photo_for_www yes ...... MySQL server has gone away
update ee_photo_for_www no ...... MySQL server has gone away
alter ee_photo_for_www ...... MySQL server has gone away
update ee_settings ee_installed_gd ...... MySQL server has gone away
update ee_settings ee_installed_imagick ...... MySQL server has gone away
alter ee_backup_info ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter admin table defaults ...... MySQL server has gone away
alter ee_detaillist_1 defaults ...... MySQL server has gone away
alter ee_detaillist_2 defaults ...... MySQL server has gone away
alter ee_photodetailrow ...... MySQL server has gone away
alter ee_photo ...... MySQL server has gone away
update ee_version number to 2.0 ...... MySQL server has gone away

[hbeumer]

I just checked the MySQL log file and it reports severe errors during the mentioned query. MySQL crashes at that point.... I checked the database files for corruption (myisamchk) but everything seems to be OK.

[Pekka]

Is this on Windows or UNIX? On my developement Windows XP Pro PC I have seen a MYSQL crash a table couple of times when doing large backup restores - when I deleted the table and recreated it crashes stopped. MySQL tables are simply files on a disk - if there are disk write errors, filesystem errors or sector corruption it would explain crashes.

I'm sure the queries and code is valid. MySQL and PHP report errors immediately before executing the actual command(s).

In any case I'll make some pasta now and after that I make you an alternative installer, step by step one. Just to try it out that it is not some RAM usage problem in PHP.

[hbeumer]

Is this on Windows or UNIX? On my developement Windows XP Pro PC I have seen a MYSQL crash a table couple of times when doing large backup restores - when I deleted the table and recreated it crashes stopped.

After deleting the database and recreating it from an SQL dump, the upgrade ran flawlessly. So it must have been some inconsistency in my database. Thanks for your support.

[pplfilho]

Pekka,

You've done a great job indeed.

One thing I noticed after upgrading to EE2.0 is that in my Indexpage settings something is not quite right. I used to have a search box in my group index page to one of the sites where I have images for sale and now that search box (was set up in 'Headers') does not show up anymore nor the Footer. Here is a snapshot of my ADMIN indexpage. (Attached file).:rolleyes::?:

[Pekka]

Pekka,

You've done a great job indeed.

One thing I noticed after upgrading to EE2.0 is that in my Indexpage settings something is not quite right. I used to have a search box in my group index page to one of the sites where I have images for sale and now that search box (was set up in 'Headers') does not show up anymore nor the Footer. Here is a snapshot of my ADMIN indexpage. (Attached file).:rolleyes::?:

I removed your image for security reasons.
The odd stuff in your index page settings editor is because there is some commented code which includes your header code (which is not in this editor any more) and messes the output.... it'll be fixed in next release.

The header and footer are in global settings editor.

header precedence:
1. header html (global settings editor)
2. gallery/languages/xxx/header.php
3. gallery/header.php

[pplfilho]

I removed your image for security reasons.
The odd stuff in your index page settings editor is because there is some commented code which includes your header code (which is not in this editor any more) and messes the output.... it'll be fixed in next release.

The header and footer are in global settings editor.

header precedence:
1. header html (global settings editor)
2. gallery/languages/xxx/header.php
3. gallery/header.php



Thanks Pekka,

I will be waiting to the fix. Meanwhile I will try to fit the search box somewhere else. Mind you the footer is not showing up either.

[]s
Pedro Luz Cunha
;)

[Pekka]

Well, I meant fixed only a bug in index settings editor. Global Settings editor has header and footer boxes which should work just fine. So if header and footer do not show, the problem is not in EE, but in what is in header and footer.

[pplfilho]

Well, I meant fixed only a bug in index settings editor. Global Settings editor has header and footer boxes which should work just fine. So if header and footer do not show, the problem is not in EE, but in what is in header and footer.

Pekka,

Well what I have there (Global Settings) is the same I had with EE1.5 RC4 and it worked fine in EE1.5RC4. It doesn't work now. What I thought was strange is that the code I had to setup my search box in the first page is now somehow incorporated to INDEXPAGE Settings, and you can see that in the image I sent you earlier.

Now it rings me a bell that the search box was in an welcome message I had. Is there another place to put a 'welcome message' in EE2?

Does it make sense?

[]s
:rolleyes:

[yosemite]

pedro,

another member showed me that you can put a welcome message, etc in the 1st group. go to group editor and use the id 1, 1st group. and put the text in the Group description and leave the name blank.

[pplfilho]

Well, I meant fixed only a bug in index settings editor. Global Settings editor has header and footer boxes which should work just fine. So if header and footer do not show, the problem is not in EE, but in what is in header and footer.

Pekka,

One other thing: My welcome message is in ee_settings_eng, column ee_indexpage_text and it is fairly long.

[]s

[pplfilho]

pedro,

another member showed me that you can put a welcome message, etc in the 1st group. go to group editor and use the id 1, 1st group. and put the text in the Group description and leave the name blank.

Thanks for the tip. But I need quite a few lines to setup a search box. Would it be possible to do in the way you suggest?

Thanks,

:rolleyes:

[yosemite]

i am not sure as i have not tried it. i had this in my header for 1.5 and it worked. give it a try.

<FORM ACTION="list.php"
METHOD="POST" name="FORM_search" id="FORM_search">
<input type="hidden" name="exhibition" value="all">
<input type="text" name="keyword" value="" size="10"
maxlength="50">
<input name="SUBMIT_search" type="submit" class="but"
value="search">
</FORM>

[segal3]

The default layout has a search box in the right column of the index page...

<?php print $form_simple_search_html; ?>

[pplfilho]

Thank you all that responded to my post. I now have the search box online, thanks Yosemite for the tip.

[]s
:D

[pplfilho]

Well, I meant fixed only a bug in index settings editor. Global Settings editor has header and footer boxes which should work just fine. So if header and footer do not show, the problem is not in EE, but in what is in header and footer.


I wil PM you with the code I have in my Footer box in Global settings.


[]s
:rolleyes:;)

[Cyclist]

@Pekka: How does the upgrade work if I have an pre-release EE2 version installed on my server? (by the way: have you recieved my message?)

[david chegal]

Can I install this EE2 without EE1.5?
Because I'm not EE1.5 user.

[yosemite]

there is no ee2 installer, you have to do a upgrade, just install ee1.5 and then the 2 upgrade. do a search as it has been discussed here before.

[kledi]

where can I download the database structure. On the site there is a download for the upgrade, but it appears to be missing the database structure.

[yosemite]

are you upgrading or fresh install?

[geantbrun]

Hi everyone,
Sorry if the question is too obvious, I'm a newbie with EE. Is it possible to install EE2 without having installed before earlier versions? I've only found *upgrade* instructions.
Best regards,
Patrick

[geantbrun]

I found my answer in the preceding posts.
Sorry for that.
Patrick

[Paulhuang]

Hi,

I am trying to do a upgrade of EE to version 2.0. Trying to a backup of my database first. I used the backup facility in EE and encountered this error message. Any help would be greatly appreciated.

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 679 bytes) in /home/virtual/site18/fst/var/www/html/gallery/adminfolder/backup/index.php on line 1611

Thanks,
Paul
www.naturestops.com

[Alan Van Vliet]

Hello,

I am getting ready to upgrade from 1.5 RC and I got this error message recently while trying to assign exhibition groups.


Exhibit Engine MySQL error!
ERROR FROM QUERY lock_groups in page 'exhibition_group_editor':

------------------------------
Access denied for user 'avvphoto'@'localhost' to database 'avvphoto_forsale'
------------------------------

If you encounter this error with unmodified EE source code please mail this error to EE developers with version number, detailed circumstances when it happened and preferably with a database backup dump. All reports helps improving EE to your satisfaction. Thank You.

Any thoughts on upgrading with this existing problem?

I assumed it was a bad idea...



I purged the uncookied data but it didn't make any difference. I can send a database backup if needed.

Thanks, AL

[Pekka]

Hello,

I am getting ready to upgrade from 1.5 RC and I got this error message recently while trying to assign exhibition groups.


Exhibit Engine MySQL error!
ERROR FROM QUERY lock_groups in page 'exhibition_group_editor':

------------------------------
Access denied for user 'avvphoto'@'localhost' to database 'avvphoto_forsale'
------------------------------

If you encounter this error with unmodified EE source code please mail this error to EE developers with version number, detailed circumstances when it happened and preferably with a database backup dump. All reports helps improving EE to your satisfaction. Thank You.

Any thoughts on upgrading with this existing problem?

I assumed it was a bad idea...



I purged the uncookied data but it didn't make any difference. I can send a database backup if needed.

Thanks, AL


You will need lock privileges for mysql user (user that you have for EE2). Easiest way to add them is to use phpmyadmin if you have proper rights to do it. Then you do reload privileges in phpmyadmin and that's done. Else you'll need to ask your server support to do it for you.

The other thing is that error message from above is from EE 1.5, not 2.x! Have you really uploaded all php files. Also, EE 2 database is not EE 1.5 compatible.

[wkitty42]

Set permissions inside admin folder to 777 (world writeable) for these folders only:
admin/temp
admin/UPLOAD
admin/UPLOAD/ee_temp_upload
admin/UPLOAD/test
i just moved the code and photos to another server and did set the above as directed... but who should the owner be? the ftp server, the web server or the username?

woke up this morning and the first thought was about this and that it would be the same as the ftp user who does the uploads. hehe, i'm so used to working with high privileges that i hadn't had to worry about this.

on the same lines, what should be the rights and owner of the exhibits folder? my layout has the exhibits in a tree within the main script folder... my main script folder is also /...

also twigged on this, too... everything's 644 except those few admin directories that need 777 as per the instructions

the reason i've moved this stuff was for speed and increased options... my front-end server is doing a reverse-proxy to the new box so that nothing on the front has to change...

as far as i can tell, everything is working like it was but now i've also got the added benefits of imagemagick and other commonly available tools in *nix platforms... however, i still cannot rethumbnail and i don't see anything indicating what the error is... i am NOT using imagemagick at this time... my resize methods still use GD2...

also, what should the permissions on /temp be? that's temp in the webroot...

should this be a link to the main system /tmp or shold it not even exist?

yes, i've got the ftp root for my ee_user set to the webroot, too...

[wkitty42]

well, i wasn't right in my above edit... 644 isn't what is needed and i'm unable to determine what the proper perms and group are supposed to be :( 644 seems to work ok for viewing and stuff but not when i go to do uploads...

1. i'm my own host.
2. "username" is the ftp account
3. "username" belongs to "username" group
4. www-data is the web account
5. www-data is the web account group
6. proftp starts off with a mode of 666 for files
7. proftp starts off with a mode of 777 for directories
8. proftp is currently set to a UMASK of 022 for the files
9. proftp is currently set to a UMASK of 022 for the directories
10. the UMASK is subtracted from the mode. so a user mode of 666 and UMASK of 022 should return a final of 644 for files uploaded by the user via ftp
11. by the same token, a directory mode of 777 and UMASK of 022 should return a final of 755 for directories created by the user via ftp
12. could someone please tell me what the UMASK should be for uploaded files and created directories?
13. should the user also belong to the www-data group? if so, how to add the user to another group without loosing the existing group(s)?
14. could someone please list me a simple directory tree of a working eE installation with the proper user, group, and permissions so i can fix up a quick script to correct what is already in place?

hopefully the above is clear and complete??

[yosemite]

here is what the files look like from a fresh install of 1.5 rc4, then upgraded to 2.0 then to 2.2, no errors works perfect. installed this last week

jpeg screen capture

[wkitty42]

here is what the files look like from a fresh install of 1.5 rc4, then upgraded to 2.0 then to 2.2, no errors works perfect. installed this last week

jpeg screen capture

thanks for that, yosemite! ummm... can you email a larger version of that, please? the text is pretty small...

i will say that i'm pretty close as i do finally have rethumbnailing and uploading of new photos working... i haven't tried to edit any existing php files via the admin editor, though...

i think my biggest problem was getting the owner of into the proper groups... one group for the web server and another group for the ftp stuff to work... now i just need to ensure that i don't have too many permissions assigned...

i'm actually working (as soon as i can get my keyboard working again) to look at the permissions applied to the newly uploaded stuff and applying them to everything... well, at least as far as actual exhibit photos go... i just also want to ensure that i've got the proper stuff for the php scripts and the directories that contain them... i sure don't want any hackers getting in due to something being too open ;)

[Tragerman]

Perhaps I have missed it, but I don't see any link to download the base level EE to get started. If you know where this is, please point me along..... Thanks!
-Mickey

[Tragerman]

Perhaps I have missed it, but I don't see any link to download the base level EE to get started. If you know where this is, please point me along..... Thanks!
-Mickey

Nevermind. I found it.

[freewilly]

After upgrade to 2.0, I test the ftp servers with EE internal FTP engine chosen. It seems taking very long then time out. It works when I chose PHP ftp module.

Anyone can help? Thanks.

[PrimaPhoto]

I am trying to install EE 1.5, I downloaded EE_RC4.zip and did the MySQL info in the files as stated but I have a 500 server error?

Did I download the correct file?

Thanks

[PrimaPhoto]

Exhibit Engine MySQL error!
ERROR FROM QUERY lock_groups in page 'exhibition_group_editor':

------------------------------
Access denied for user 'avvphoto'@'localhost' to database 'avvphoto_forsale'
------------------------------

If you encounter this error with unmodified EE source code please mail this error to EE developers with version number, detailed circumstances when it happened and preferably with a database backup dump. All reports helps improving EE to your satisfaction. Thank You.

Any thoughts on upgrading with this existing problem?

My server people told me I was trying to run 1.5 on PHP 5.

[chrisclw]

Can someone tell me what I did do wrong? Installed 1.5 without any problem. I got this line when I am trying to upgrade to 2.0:


Parse error: syntax error, unexpected T_LNUMBER in /share/HDA_DATA/Qweb/EE2/basecode/SETUP_settings.php on line 340

[Pekka]

Can someone tell me what I did do wrong? Installed 1.5 without any problem. I got this line when I am trying to upgrade to 2.0:


Parse error: syntax error, unexpected T_LNUMBER in /share/HDA_DATA/Qweb/EE2/basecode/SETUP_settings.php on line 340

There must be some extra characters in that file. Make sure that you edit the original basecode/SETUP_settings.php and save it as plain text (use NOTEPAD in Windows) and upload it as ASCII.

[chrisclw]

There must be some extra characters in that file. Make sure that you edit the original basecode/SETUP_settings.php and save it as plain text (use NOTEPAD in Windows) and upload it as ASCII.

Pekka, I did that, but it still gave me the same error. Since I am installing EE on my NAS, is it the same if I just copy and paste from Windows explorer as oppose to upload it as ASCII? Thanks.

[eyesociety]

Hi all

I am using SMF a forum based site and i would like to install and use this Exhibit Engine 2 for my photo's
so that all my friends and family a can share images with each.

How do i start off. I am running a Gentoo Linux system

[UweB]

First you go here:
http://photography-on-the.net/forum/showpost.php?p=192221&postcount=4
read and install everything carefully and make it work.
If it does you can go here:
http://photography-on-the.net/forum/showthread.php?t=223149
there is no auto upgrade from 1.5 to 2.02

[noopara]

It's been awhile since anyone has posted here.

I just upgraded from 1.22 to 2.0 after my web host provider changed servers and broke my installation after 6 years of flawless operation. Darn...

So, I thought it would be a good idea to upgrade to 2.0. I followed the process and I can see the index page and can see some of the images on the index page but only a small number in some of the albums. When I try and run the Retrieve Photo Sizes, it seems to hang up.

I have a copy of my old install and made a copy of the original database using phpMyAdmin before attempting the upgrade.

The install log gave me these errors:
add ee_list_view ...... Duplicate column name 'ee_list_view'
add ee_list_perpage ...... Duplicate column name 'ee_list_perpage'
add ee_list_order ...... Duplicate column name 'ee_list_order'
add ee_simplenavigation_search ...... Duplicate column name 'ee_simplenavigation_search'
add ee_detaillist_1 ...... Duplicate column name 'ee_detaillist_1'
add ee_detaillist_2 ...... Duplicate column name 'ee_detaillist_2'
add ee_sort_row ...... Duplicate column name 'ee_sort_row'
add ee_simplenavigation_sort ...... Duplicate column name 'ee_simplenavigation_sort'
add ee_simplenavigation_perpage ...... Duplicate column name 'ee_simplenavigation_perpage'
add ee_activate_links_list ...... Duplicate column name 'ee_activate_links_list'
add ee_activate_br_list ...... Duplicate column name 'ee_activate_br_list'
add ee_tooltip_showdetail ...... Duplicate column name 'ee_tooltip_showdetail'
add ee_counter_scale ...... Duplicate column name 'ee_counter_scale'
add ee_use_custom_list_settings ...... Duplicate column name 'ee_use_custom_list_settings'
add ee_performance_samples ...... Duplicate column name 'ee_performance_samples'
add ee_add_path_trailing_slash ...... Duplicate column name 'ee_add_path_trailing_slash'
add ee_editor_font_size ...... Duplicate column name 'ee_editor_font_size'
add ee_use_pt_pano ...... Duplicate column name 'ee_use_pt_pano'
add ee_use_pt_flat ...... Duplicate column name 'ee_use_pt_flat'
add ee_make_pt_files_local ...... Duplicate column name 'ee_make_pt_files_local'
add ee_try_pt_crypt ...... Duplicate column name 'ee_try_pt_crypt'
add ee_ftp_view ...... Duplicate column name 'ee_ftp_view'
add ee_ftp_cleanup ...... Duplicate column name 'ee_ftp_cleanup'
add ee_debug ...... Duplicate column name 'ee_debug'
add ee_editor_font_family ...... Duplicate column name 'ee_editor_font_family'
add ee_indexpage_thumbcaption ...... Duplicate column name 'ee_indexpage_thumbcaption'
drop ee_admin ...... OK
create ee_admin ...... OK
add into ee_admin ...... OK
add ee_indexpage_thumbsize ...... Duplicate column name 'ee_indexpage_thumbsize'
ALTER TABLE `ee_photo` (drop ee_photo_foo) ...... Can't DROP 'ee_photo_foo'; check that column/key exists
alter ee_backup_info ...... Table 'caiman323_gallery.ee_backup_info' doesn't exist


After running the install the install page had the drop down menu set to 1.5 Release Candidate 4 instead of 1.22 which is what it was when I started? Why is that?

I am unable to do the db backup from within EE2. It starts and then a blank page appears after 15 seconds.

The install check is clean except for:
35. PHP maxtime: 30 seconds
WARNING: 30 seconds is pretty low value, this means you have exactly 30 seconds to perform each editor command before PHP system halts the execution (resulting usually on blank page). You can increase this value in .htaccess or php.ini. What is a correct value depends on your server speed and tasks you do. Do not set it too high either as it will cause problems when scripts hang out for other reasons. Try 600 first (10 minutes).

Is the backup and photo size routines not working because of the 30 sec max time limit?
Should I do the install again?
Or, should I do the 2.02 upgrade?
Do the install errors provide an answer to the problem?
Why is it necessary to run the retrieve photo size process? What is actually going on with this process?

Many thanks for the help. I hope you are still watching this thread!

-- greg

[Pekka]

Those "duplicate column name" errors seem to suggest that you have run upgrade twice.

Yes, 30 second php max script exceution time limit will prevent backup process and other functions which take more than 30 seconds. 15 seconds blank page sounds like RAM problem. So please also check that you let PHP use RAM if needed. in php.ini do

max_execution_time = 1800
max_input_time = 1800
memory_limit = 32M

To check integrity of database, please do this: go to admin -> reports and select "database form check", do you have other than some TIMESTAMP's in red color there?

[Pekka]

Why is it necessary to run the retrieve photo size process? What is actually going on with this process?

It gets photo dimensions and stores them to database. Makes pages render smoother and without "jumping". See comments in SETUP_settings.php:

// should photos without stored size info show as "not available image" or as they are (as broken image)?
// yes = "1" no = "0"
// NOTE: set this setting to "0" after upgrade from 1.5, before you have run all images
// through "Retrieve Photo Sizes" editor. Else keep it at "1".
$s_use_notavailable = "0";

[noopara]

That makes sense. It probably did run twice as the upgrade page was still loading each time I started my browser. Hopefully it caused no harm.

Database form check shows no messages in red other than TIMESTAMPS

I have not had a need in the past to mess with my php installation. I will set up a custom php.ini file and make the changes.

Thx

[noopara]

I made the changes to php.ini

There is no change.

I think the problem might have to do with a problem logging into my ftp server. I am getting errors like that when trying to run Retrieve Photo Sizes.
msg 10005 | internal ftp: PASS: 530 Login incorrect.
msg 10004 | internal ftp: PASS
msg 10003 | internal ftp: USER: 331 Password required for username
msg 10002 | internal ftp: USER username
msg 10001 | internal ftp: CONNECT: 220 DreamHost FTP Server
msg 10000 | SIZE ANALYZER: 0x0 - 0 bytes

This is probably becuause I don't understand the requirmenet to enter the server info. The FTP Server Setup shows two entry forms. One for FTP Servers and the other for EE Home FTP Server.

When I run a test on what I have for FTP Servers it passes all the tests. When I run a test on the EE Home FTP Server I get an error checking EE Home Directory - it says unknown. My entry for the Home Directory is the same as what I put in for the FTP Server except for the path info. Maybe this is what is causing the problem.

When I run backup I get
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


When I run a batch for photo size I get
1580.
Normal http://www..../normal/bg_r0003.jpg 0x0 FAILED 0 bytes
Large http://www..../large/bg_r0003.jpg 0x0 FAILED 0 bytes

[noopara]

I forgot to mention that my RAM in my php.ini file was set to 90M so it wasn't necessary to change it.

[Pekka]

The EE home dir needs to be correct and pass ftp tests in order uploads and resizes to work. EE Home ftp path is the directory you see when you log in normally with any ftp client -> browse to your EE index.php and then give ftp command PWD ( which means "print work directory"). Many ftp clöients let you see the current path in GUI, too. Usually it's the path from ftp login root, sometimes path from server root, there is no way to know this without checking. You might also try to let EE find it, but that might take a long time (must finish within max_ececution_time).

Check also that you have admin temp dirs chmod 777:

admin/temp
admin/UPLOAD
admin/UPLOAD/ee_temp_upload
admin/UPLOAD/test
admin/backup/ee_backup_files

The EE Backup error might be file permission, if its http error 500 then try to upload all files in backup folder again with ASCII upload.

[noopara]

OK, we are getting somewhere now.

I moved the eegallery directory up near the top (alphabetically) in the directory reducing the time for discovery and using the find function was able to decipher the path. The Home EE FTP server now works fine.

I ran the backup and it looks like it worked. Lots of files in the backup folder.

Batch photo checker still doesn't work.

I get these messages
sg 54792 | SIZE ANALYZER: 0x0 - 0 bytes
msg 54791 | internal ftp: QUIT
msg 54790 | internal ftp: PASS: 530 Login incorrect.
msg 54789 | internal ftp: PASS
msg 54788 | internal ftp: USER: 331 Password required for username
msg 54787 | internal ftp: USER username

and
Normal http://www.../....jpg 0x0FAILED0 bytesLarge http://www.../...jpg 0x0FAILED0 bytesTHUMB:
http://www.flamincaiman.org/gallery/2008_reunion/tn/gb_r0283.jpghttp://www.flamincaiman.org/gallery/apmf323admin/graphs/x.gif
0x0 - 0 bytes MICROTHUMB:
http://www.flamincaiman.org/gallery/2008_reunion/mtn/gb_r0283.jpghttp://www.flamincaiman.org/gallery/apmf323admin/graphs/x.gif
0x0 - 0 bytes
this one: 5.3s
total 00:00:11








FILE CHECKED SUCCESFULLY!



















I still don't have very many images showing
www.flamincaiman.org/gallery

[Pekka]

If file size checker fail when in ftp mode, it means you have wrong ftp paths to your photo folders in your path editor.

If file size checker fail when in ftp mode, it means temp folder(s) has wrong permissions.

EE Backup file backup creates only one file. You must have some old backups there.

You might want to upgrade to 2.04 now.

[noopara]

That was it. I assumed it would have handled that in the upgrade process. I inputted the info and now the photo check routine works fine.

Regarding resizing, what is the best way to proceed. My data up to now consists of 4 directories: Normal, Large, Thumb and Microthumb. I would like to start using auto resizing for new photos. How can I use both the old data without doing auto resizing and use auto resizing with the new data. If I specify a resize method in the path table won't it be applied to all the photos in the directory?

[noopara]

Regarding the back files, there are about 19 of them. 12 on 6/20, 1 on 6/21 and 4 on 6/22 and 2 on 6/24. The file names look like this: database_name_2010-06-20@00_22_28

what is the 00_22_28?

Perhaps all the attempts at running the database prior to getting the path correct were waiting in the wings and ran once I corrected the path??

[Pekka]

Regarding the back files, there are about 19 of them. 12 on 6/20, 1 on 6/21 and 4 on 6/22 and 2 on 6/24. The file names look like this: database_name_2010-06-20@00_22_28

what is the 00_22_28?

Perhaps all the attempts at running the database prior to getting the path correct were waiting in the wings and ran once I corrected the path??

00_22_28 is HH_MM_SS timestamp.

Yes, those must be attempts that failed. You can delete them all.
Please remember to download the latest backup file after you make it. If server breaks, it not of much use there.

[Pekka]

That was it. I assumed it would have handled that in the upgrade process. I inputted the info and now the photo check routine works fine.[QUOTE]

Great!

[QUOTE=noopara;10419623]Regarding resizing, what is the best way to proceed. My data up to now consists of 4 directories: Normal, Large, Thumb and Microthumb. I would like to start using auto resizing for new photos. How can I use both the old data without doing auto resizing and use auto resizing with the new data. If I specify a resize method in the path table won't it be applied to all the photos in the directory?

Resize is done while UPLOAD TO DATABASE is running. Current resize method settings are used, which you assinged to the paths selected for upload.

I would use same size and thumb paths for all exhibitions, unless you have a specific reason to divide them around or have set of private photos in some obscurely named folders.

When you change size paths, just make sure you do not change the ones that are in use.

Also, one tip: upload the largest photo size (e.g. 1024 wide) you want to display into the server and put it to size path "original", and set that size path resize method to "NONE". The set other paths and resizes as needed. NONE means: just move the photo to the folder using ftp, do not resize it.

[noopara]

OK, I think I understand.

In the past I had for each album 4 directories on the server, large, normal, thumb and microthumb. I manually, using batch editing software, used to resize from the large size the normal, thumb and microthumb and then ftp's all four to the server. A lot of work.

What I think you are saying that with the new version I can create a new upload folder for each album and ftp the large (original) size to that folder and use auto resizing for the other images. To do this, for example for the thumb size, the path for the thumb would be the upload folder. I don't have to do anything for the photos already in the database. Is this about right?

[Pekka]

OK, I think I understand.

In the past I had for each album 4 directories on the server, large, normal, thumb and microthumb. I manually, using batch editing software, used to resize from the large size the normal, thumb and microthumb and then ftp's all four to the server. A lot of work.

What I think you are saying that with the new version I can create a new upload folder for each album and ftp the large (original) size to that folder and use auto resizing for the other images. To do this, for example for the thumb size, the path for the thumb would be the upload folder. I don't have to do anything for the photos already in the database. Is this about right?

Eh, no. :)

All size paths and thumb paths should point to folders in your www site, and not to admin/UPLOAD folder. It is technically possible to use UPLOAD folder so, but it is a very bad idea indeed.

UPLOAD folder is for source material only. UPLOAD folder is in your admin folder (which you have renamed to something only you know, right?) and not for serving photos. After upload to database is successful and you verify all is ok, you can delete photos in upload folder.

When EE resizes photos to whatever sizes you want to display (each size = size path) and resizes to thumbnails: it first reads selected photo from UPLOAD folder, does the resize process and the moves the resized photo using ftp to correct ftp path in server.

Ftp path and URL must point to same physical folder on your server, and that folder must be accessible by www. Ftp path is there so that EE can move resized photos within server(s), URL is there so that EE can show the photo on a web page.


This system is almost too free, so in order to have some structure you can understand keep it simple.

Let's say you have server's www root in /home/www/gallery/index.php. Then you have admin in /home/www/gallery/myEEadminXXX/

Set up size paths

Path: default
URL: http://www.yoursite.com/gallery/photos/1/default/
FTP server: localhost
FTP Folder: /home/www/gallery/photos/1/default
Resize Method: NONE

Path: medium
URL: http://www.yoursite.com/gallery/photos/1/medium/
FTP server: localhost
FTP Folder: /home/www/gallery/photos/1/medium
Resize Method: Medium (IMAGEMAGICK 800)

Path: small
URL: http://www.yoursite.com/gallery/photos/1/small/
FTP server: localhost
FTP Folder: /home/www/gallery/photos/1/small
Resize Method: Small (IMAGEMAGICK 600)



and thumb path

URL: http://www.yoursite.com/gallery/photos/thumb/
FTP server: localhost
FTP Folder: /home/www/gallery/photos/thumb
Resize Method: thumb (IMAGEMAGICK 110)

and microthumb path

URL: http://www.yoursite.com/gallery/photos/microthumb/
FTP server: localhost
FTP Folder: /home/www/gallery/photos/microthumb
Resize Method: microthumb (IMAGEMAGICK 43)


Now you create an exhibition, and choose thumb path http://www.yoursite.com/gallery/photos/thumb/ and microthumb path http://www.yoursite.com/gallery/photos/microthumb/ for it.

Then you got to "UPLOAD TO DATABASE" and follow the 7 form steps. You do not have to select all size paths there, just one is needed.

Size paths you select on upload form are not fixed to any exhibition which means if size path works (ftp and http) it can be used by any photo on any exhibition. You can make several size paths point to same folder on server with different resize methods - on that upload form you decide which are used for that particular photo or batch of photos.

You can later move folders on your server, or to another server. Just update the paths and photos will display fine.

[noopara]

A few more questions...

I don't see thumbnails showing for all the albums in the index??

I am seeing for each album thumbnails, black thumbnails with a white X, and no thumbnail - just the name of the file. This might be because with the old version I sometimes would upload photos but not put them into the data base. I'm not sure what the white X thumbs are about.

Thanks for all your help.

[Pekka]

Go to your exhibition editor, and see what thumb paths you have there.

Change in basecode/SETUP_settings.php

$s_use_notavailable = "0";

Now you can see the broken image paths in either by right clicking broken image icon browser shows you, or viewing the html source.

[noopara]

The paths to my images is correct. I am working on only one of my albums to keep it simple.

My setup_settings.php already had this entry
$s_use_notavailable = "0";

The black rectangles with a white X have a path of /graphs/na_thumb.gif

The entries with no image show the title and the path to these is correct except the Type is listed as text/y404 and the entry in the Page Info in firefox shows in grey colored italicized text. Where there is an image there is no title showing and the entry in the Page Info is black and non-italicized. If I change the Listing Type to Thumbnails with Titles, the entries with only titles show the title twice.

I am wondering if my database is corrupted. Perhaps this happened with the upgrade. Does the upgrade from 1.22 or 1.5 to 2.0 change anything in the db? When I did the upgrade I selected 1.22 to upgrade from, but when it finished the report page showed that I upgraded from 1.5. Maybe I accidentally changed the drop down list entry with my scroll wheel without realizing it right before the upgrade ran??

Thank you for the detailed explanation regarding the upload process. I didn't understand that the upload process copied the files from the upload directory into the photo folders. (In your explanation you said that it moves the files and then you said that after the upload process that you can delete the files from the upload folder. I think you meant to say that they are copied from the upload folder.)

[noopara]

From searching all the files, I'm guessing that the reason for the na_thumb.gif might be because the script did not find the thumb image or it does not meet the size criteria??

[noopara]

I discovered a problem with the directories on the server. A lot of the photos were missing because my local directories were not complete.

Ignore my last two posts.

I still have the broken images/links to some photos that show black with a white x. That's the next hurdle.

[noopara]

I solved the problem with the broken links to thumbs. I re ran the photo size checker on those photos and it cleared it up.

You mentioned that I should upgrade to 2.04. What improvements are in 2.04?

Where can I find the file and procedures for the upgrade?

How can I change the font styles and sizes showing on the various pages?

[noopara]

I believe I found the solution to changing font styles and sizes.

I also found the posting regarding a procedure to upgrade to 2.04. I will give it a whirl.

Many thanks for all the help.

-- greg

[wkitty42]

You might want to upgrade to 2.04 now.
where are the instructions for upgrading from eE 2.02 to 2.04, please? i have found the EE204 file and downloaded it but cannot afford to frag my install and so want to do this right...

i'm hoping it will take care of the error i'm currently seeing after a recent server OS upgrade

msg 200600 | ftp: wedding1_001.png: MICROTHUMB DELETE ERROR. Reason: unknown
msg 200599 | internal ftp: LOCAL: WORKING DIRECTORY CHANGE to '/Exhibits/2nd-life/blak&tcheb-wedding/microthumbs' FAILED. Reason: Function split() is deprecated. CAN NOT GO ON...
msg 200598 | internal ftp: CWD: 550 /Exhibits/2nd-life/blak&tcheb-wedding/microthumbs: No such file or directory
msg 200597 | internal ftp: CWD /Exhibits/2nd-life/blak&tcheb-wedding/microthumbs
msg 200596 | internal ftp: LOCAL: Logged in as 'myuser'

[pjbellue]

Hello Pekka, looks like I need to redo an install from scratch. I can't find the files I had, and looks like Picmans account has been suspended, where can I get this download from?

[FA_Productions]

I am also looking for this program. Is the upgrade also a full install?