PLEASE REPORT ALL (EVEN MINOR) BUGS IN RC3

[Pekka]

To make the release version 1.5 as stable as possible please report even slightest error or problem (withing current feature set) in version 1.5 RC 3. No new features will be added to this version, but all that are there now should work 100%.

Please try to use Internal FTP - need as much testing on that as possible. Only reason not to use internal FTP now would be that your ftp server refuses passive mode connections.

Thanks a lot for making EE the most stable gallery system, too :)

New features will be introduced in 1.5x versions. Bigger features will include lightbox system tied to EE Commerce, mail related features like notifications and E-Cards and make a new more timeout-tolerable upload scheme.

If you have done cool styles do not hesitate to share them with others. You can announce them in this forum or mail them to me if you want/let them to be included in EE release version.

[TomKa]

Testing the IPTC feed into EE, the IPTC-Field ID5, Object Name, is converted into the header of the page and the picture title.
This should be the IPTC-Field ID105, Headline, that should be used as the header.

See also the IPTC-table from Markus: http://www.sinus.ch/iptctable.html
And the forum thread http://photography-on-the.net/forum/showthread.php?t=24441&highlight=subcategory

105 Headline: Not repeatable, maximum of 256 octets, consisting of graphic characters plus spaces.
A publishable entry providing a synopsis of the contents of the
objectdata.
Example: "Lindbergh Lands In Paris"

05 Object Name: Not repeatable, maximum 64 octets, consisting of graphic characters plus spaces.
Used as a shorthand reference for the object. Changes to existing
data, such as updated stories or new crops on photos, should be identified in Edit Status.
Examples:
"Wall St."
"Ferry Sinks"
Markus, for example, is putting his original filename "sin01450" in this field.

However, also for me it's not 100% clear what to put in. Somebody can give me more input? :?

[msoo]

Hi Pekka,

This bug hasn't been fixed.

In "misc settings", uncheck "Display photo detail:" but leave "show/hide photo detail switch:" checked.

In the photo page, the details are gone but hide/show won't bring it back.

- MS

[pplfilho]

Hi Pekka and All,

After upgrading from RC2 to RC3 I am getting this code on the bottom over my photos:

= "2") { print ""; } if ($debug == "1") { print $infomap; } // EOF ?>

check http://www.pedroluz.com/photo.php?photo=57

[]s

[Pekka]

Hi Pekka and All,

After upgrading from RC2 to RC3 I am getting this code on the bottom over my photos:

= "2") { print ""; } if ($debug == "1") { print $infomap; } // EOF ?>

check http://www.pedroluz.com/photo.php?photo=57

[]s

Must be corrupt file. Try uploading viewerstyles/VIEWERSTYLE_default.php again to server. Let me know if that fixes it or not.

[pplfilho]

Must be corrupt file. Try uploading viewerstyles/VIEWERSTYLE_default.php again to server. Let me know if that fixes it or not.

I've uploaded all the 'viewerstules' directory and now it works fine. Thanks Pekka.

[]s :D

[smeyer]

Hi Pekka and All,

After upgrading from RC2 to RC3 I am getting this code on the bottom over my photos:

= "2") { print ""; } if ($debug == "1") { print $infomap; } // EOF ?>

check http://www.pedroluz.com/photo.php?photo=57

[]sI get a similar thing. Over the photo I get:

Notice: Undefined index: ee_ftp_passivemode in /home/web/web15618/viewerstyles/VIEWERSTYLE_ftp_retrieve.php on line 52

Notice: Undefined variable: last_id in /home/web/web15618/FTP_ee_library.php on line 807

Notice: Undefined variable: last_id in /home/web/web15618/FTP_ee_library.php on line 807

Notice: Undefined variable: last_id in /home/web/web15618/FTP_ee_library.php on line 807


Check: http://www.mit-fotoalbum.dk/photo.php?photo=234

Ive tried uploading the viewerstyles-files again, but that didn't make any difference. What could be wrong?

/Steffen

[pplfilho]

Pekka and All,

I am still unable to rethumbnail images. After doing a rethumbnail I get black images instead of new micro/thumbnails. My FTP log shows image size (original) 0 x 0 and I am usig GD2:

(15s.) --- messagesize 32 KB

msg 13335 | internal ftp: UPLOAD FINISHED SUCCESFULLY.
msg 13334 | internal ftp: LOCAL: DISCONNECTED
msg 13333 | internal ftp: QUIT:
...

221-Goodbye. You uploaded 1 and downloaded 0 kbytes.
221 Logout - CPU time spent: 0.000 seconds.


msg 13332 | internal ftp: QUIT
msg 13331 | internal ftp: LOCAL:
'ANIM000044.jpg' UPLOADED SUCCESFULLY
SIZE: 0x0 => 43x43 microthumb (GD 43)
msg 13330 | internal ftp: UPLOAD(END):

[]s :?:

[pplfilho]

Hello Pekka and All,

One more piece of information. I was using EE Internal FTP. I switched to PHP FTP and now I also get the following messages:

Warning: imagecreatefromjpeg(): gd-jpeg: JPEG library reports
unrecoverable error:
in /home/pplfilho/public_html/input/RESIZE_gd.php on line 44

Warning: imagecreatefromjpeg(): 'temp/ANIM000044.jpg' is not a valid JPEG file in /home/pplfilho/public_html/input/RESIZE_gd.php on line 44

Warning: imagecopyresampled(): supplied argument is not a valid Image resource in /home/pplfilho/public_html/input/RESIZE_gd.php on line 46


[]s

[pplfilho]

Hello Pekka and All,

I don't know if this is a bug or not. I am getting the following message in tha backup page:

Warning: disk_free_space(): open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/pplfilho:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/pplfilho/public_html/xarope/backup/index.php on line 2704

Path ee_backup_files/ has B free space left. :-|


[]s

[Pekka]

Hi Pekka and All,

After upgrading from RC2 to RC3 I am getting this code on the bottom over my photos:

= "2") { print ""; } if ($debug == "1") { print $infomap; } // EOF ?>

check http://www.pedroluz.com/photo.php?photo=57

[]sI get a similar thing. Over the photo I get:

Notice: Undefined index: ee_ftp_passivemode in /home/web/web15618/viewerstyles/VIEWERSTYLE_ftp_retrieve.php on line 52

Notice: Undefined variable: last_id in /home/web/web15618/FTP_ee_library.php on line 807

Notice: Undefined variable: last_id in /home/web/web15618/FTP_ee_library.php on line 807

Notice: Undefined variable: last_id in /home/web/web15618/FTP_ee_library.php on line 807


Check: http://www.mit-fotoalbum.dk/photo.php?photo=234

Ive tried uploading the viewerstyles-files again, but that didn't make any difference. What could be wrong?

/Steffen

Download http://photography-on-the.net/ee/beta/ftp_view_fix.zip and replace files.

[Pekka]

Hello Pekka and All,

I don't know if this is a bug or not. I am getting the following message in tha backup page:

Warning: disk_free_space(): open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/pplfilho:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/pplfilho/public_html/xarope/backup/index.php on line 2704

Path ee_backup_files/ has B free space left. :-|


[]s

This is not a bug, but it is a bug that this message is displayed :)

In backup/index.php replace (line 2703 onwards)

<?php
if (function_exists('disk_free_space')) {
$df = disk_free_space("/"); print "<br><b>Path <span style=\"color: #990000;\">" . $dir . "</span> has " . humanfilesize($df) . " free space left.</b>";
}
?>


with


<?php
if (function_exists("disk_free_space")) {
$df = " [unknown] ";
$df = @disk_free_space("/"); print "<br><b>Path <span style=\"color: #990000;\">" . $dir . "</span> has " . humanfilesize($df) . " free space left.</b>";
}
?>

[smeyer]

Download http://photography-on-the.net/ee/beta/ftp_view_fix.zip and replace files.

Yup - that did the trick. Thanks again Pekka! :D

[pplfilho]

<?php
if (function_exists("disk_free_space")) {
$df = " [unknown] ";
$df = @disk_free_space("/"); print "<br><b>Path <span style=\"color: #990000;\">" . $dir . "</span> has " . humanfilesize($df) . " free space left.</b>";
}
?>

Hello Pekka,

Done. Now the warning message is gone, but

'Path ee_backup_files/ has B free space left.'

is still there, not showing the amount of free space left. Is that meant to be like this? :)


[]s

[chriz]

-------- ----- Expositie browser

After applying above fixes (from RC3 fixes) I notice that:
from index.php
click on thumbnail
displays picture without navigation bar (see above no next, previous or thumbnails)

On the contrary
from list.php
click on big thumbnail
normal result

Please try it: www.photoevents.nu
use the horse-pictures (the other ones work )

Chriz

PS: I uploaded all files, ran RC2 to RC3 script, tested it all day before applying fixes and found no errors. maybe I shouldn't apply fixes if everything works :P

[Pekka]

-------- ----- Expositie browser

After applying above fixes (from RC3 fixes) I notice that:
from index.php
click on thumbnail
displays picture without navigation bar (see above no next, previous or thumbnails)

On the contrary
from list.php
click on big thumbnail
normal result

Please try it: www.photoevents.nu
use the horse-pictures (the other ones work )

Chriz

PS: I uploaded all files, ran RC2 to RC3 script, tested it all day before applying fixes and found no errors. maybe I shouldn't apply fixes if everything works :P

OK, I see a problem. Upload list.php and photo.php from original RC3 installer pack back to server and see what happens.

I would very much like to have your database for testing that problem gallery - if you can mail it to me pekka AT photography-on-the.net I would be happy to check and debug that one out.

Oh, and I have to mention: it is not really a "database problem" - it is purely problem with that fix "speeded" code.

[chriz]

I uploaded photo.php and list.php from original RC3 and it seems OK again.

also emailed you my database

need anything else?


Chriz

[chriz]

Hope the database got through. It's close to 8 Mb and outlook seems to have a problem with it.

An alternative is to setup a ftp-server and give me temp login, then I'll upload it using smartftp.

Chriz

[Pekka]

Chriz,

No mail yet. I have PM'd you ftp details.

[chriz]

upload OK
going offline untill tomorrow morning

Chriz

[daddy0]

New features will be introduced in 1.5x versions.

I thought you were implementing media property (film, memory make etc.) for this version. Is it possible to include it in this phase?

BR,
Mikko

[chriz]

Pekka,

Please check your PM

Chriz

[Alexis427]

hide photo data still showing lots of |||

eg here :
http://underwaterpics.org/photo.php?photo=1297

Still having problems with internal FTP
trying to upload 34 pictures (also happens with 5 pics...), i got this error :


Fatal error: Maximum execution time of 30 seconds exceeded in /home/uwpics/www/FTP_ee_library.php on line 686

doesn't happen with php ftp

i am using imagemagick, just to strip exif . if i remove this function internal ftp works

[okapi]

just recently i upgraded EE 1.5 beta 5 to RC3 as a test installation of my gallery (340 photos) with a serparate database on the same server, and i installed all fixes available so far, also the rc3_speeder.
apart from the snippets, called from outside the gallery root, - http://photography-on-the.net/forum/showthread.php?t=28760 - everything works fine, but very, very slow. it's even slower than my running beta 5 version gallery.

what could be the reason for that?

[Pekka]

just recently i upgraded EE 1.5 beta 5 to RC3 as a test installation of my gallery (340 photos) with a serparate database on the same server, and i installed all fixes available so far, also the rc3_speeder.
apart from the snippets, called from outside the gallery root, - http://photography-on-the.net/forum/showthread.php?t=28760 - everything works fine, but very, very slow. it's even slower than my running beta 5 version gallery.

what could be the reason for that?

Editor: defragment + optimize database (under "optimize" link).

[okapi]

yes, i have done this already.

what i have learned right now is:

i had the uncookied foo end text |... removed. now i recreated it, and the photopages run a bit smooter and faster.

do you see a connection? should it not be removed?

[martabfp]

Mine was very slow untill I uninstall the rc3_speeder.
I do not know the reason, I was just trying to undone things one by one.

[Pekka]

yes, i have done this already.

what i have learned right now is:

i had the uncookied foo end text |... removed. now i recreated it, and the photopages run a bit smooter and faster.

do you see a connection? should it not be removed?

No that does not affect anything - only browser cache if even that. Try this:

1. Open photo order editor and select each exhibition in turn.
2. Go to server info page and purge uncookied data.
3. Do EE Backup (to database)
4. Restore that EE Backup

[Pekka]

New features will be introduced in 1.5x versions.

I thought you were implementing media property (film, memory make etc.) for this version. Is it possible to include it in this phase?

BR,
Mikko

Yes I remember the promise and will add it. Sorry for missing it now.

[Pekka]

Note about speed: MySQL uses "index system" to accelerate speed and EE uses that system extensively. After new clean install MySQL index system may not be active, so you will need to do one backup and restore in EE Backup make index system active again.

Also, make sure that you have checked these items to gain full speed:

- you have at least 7 photos in EE
- you have more than 5 photographers in database
- you have more than 5 cameras in database
- you have more than 5 lenses in database
- you have more than 5 lights in database
- you have more than 5 categories in database
- you have more than 5 workflows in database
- you have more than 5 paths (size, thumb, microthumb) in database

Those extra items can just be "dummy"ones, no one will see them if they are not used in photos. You may set extra paths' ftp server as OFF to hide them from upload lists.

Reason for these strange instructions is in that "index system" of MySQL. It needs data to be active, if it does not have items in database it will slow down a lot. The more data it has the merrier it is.

And this is not an April fool!

[Pekka]

More about speed:

Clear messages if they grow very large.

Use compression in Uncookied system (it reports if compression is possible as "SERVER HAS COMPRESSION CAPABILITY: YES"). Purge Uncookied data if it grows very large, in time.

[okapi]

thank you very much for this information, pekka!

[Pekka]

----------------
One daily blog entry from EE developers life (rather technical talk):
----------------

As uncookied system makes it possible to write in a mail, forum or web page a link which points to EXACT moment of EE browsing (with sorting, keywords, pagination... all settings) deleting uncookied data (which is nothing more than cookie replacement system without cookies) will make those links you posted earlier "inactive", they return you default page, or "not found" page. This in mind I will later add a filter system into uncookied purge command so that you may define Uncookied ID numbers which must be "preserved".

Today I fixed a important problem which arises with this scheme:

- Uncookied data id 987 is stored to contain exhibition id 2
- That page is indexed by search engine as http://www.example.com/gallery/photo.php?photo=123&u=987-9
- Now you purge uncookied data. Uncookied id count starts again.
- You browse the galleries and soon (freed) uncookied data id 987 is assigned to contain exhibition id 17
- someone finds the page using search engine and opens the link. EE's rather polite photo not found page opens instead because exhibition 17 does not contain photo 123.

As you may see the problem was that the search engine link holds a valid Uncookied id, but that id contains replaced data which has wrong exhibition id - this is why you'll get "photo not found" message page instead.

I have now fixed this with code that detects the problem and fixes it so that photo is always displayed. Also, all possibilities having wrong Uncookied id, wrong offset, different separator character and no uncookied id at all are secured so that photo is shown normally and all links contain valid data thereafter.

Example: a Google search http://www.google.com/search?q=sakari+oramo+photo&sourceid=mozilla-search&start=0&start=0&ie=utf-8&oe=utf-8 - click the top link (Sakari Oramo, Conductor, by Pekka Saarinen (in photo gallery Seven ...) which gets you to correct page. But if you place mouse on the microthumb of the same image, you can see from browser info bar tthat the actual link has "u=69-28" instead of "u=163-9" as in Google link. This is how transparent "show the photo even if parameters are wrong" system works.

The biggest work in programming is to ensure that every possible error is taken into account, not to write something to happen.

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

[Pekka]

Mine was very slow untill I uninstall the rc3_speeder.
I do not know the reason, I was just trying to undone things one by one.

I found the reason for this problem and will post a fix pack tomorrow. Speeder code is just ok, but duplicate category id 1's have appeared all over the place which mess and slow things up. Tomorrow you'll get Analyze/Repair code which fixes those id's so that speeder code will work normally. I have also added guardian code to seek and kill that id problem on image upload and other editors because I can not reproduce it here. So it will not happen again but nevertheless I'll keep working on finding the real cause (perhaps PHP function bug).

All above fixes plus few others will be posted tomorrow (Saturday) evening.

[okapi]

pekka wrote:

Also, make sure that you have checked these items to gain full speed:

- you have at least 7 photos in EE
- you have more than 5 photographers in database
- you have more than 5 cameras in database
- you have more than 5 lenses in database
- you have more than 5 lights in database
- you have more than 5 categories in database
- you have more than 5 workflows in database
- you have more than 5 paths (size, thumb, microthumb) in database

Those extra items can just be "dummy"ones, no one will see them if they are not used in photos. You may set extra paths' ftp server as OFF to hide them from upload lists.

Reason for these strange instructions is in that "index system" of MySQL. It needs data to be active, if it does not have items in database it will slow down a lot. The more data it has the merrier it is.

it's amazing! after i have set 10 dummy photographers, cameras, lights, categories, and workflows, EE has speeded up enormously! i have never seen such speed before in my old installation! i'm looking forward to the fix pack tomorrow, but i think the information you gave above is most important and should be published in the manual and the help files coming!

thanks again, pekka!

[okapi]

there was still a problem with my index page created with snippets. sorry for posting this again, but this might be a bug. you said, with snippets we can call the snippets code from everywhere. my index page (not the EE index page) is a php-file like the snippetdemo.php and it calls the code with absolute path from outside my gallery folder (from one level higher).

the problem is, i can see the thumbs, but also some error messages:

Notice: Undefined variable: orlist in /home/.sites/69/site292/web/photolog/snippets.php on line 222
Notice: Undefined variable: orlist in /home/.sites/69/site292/web/photolog/snippets.php on line 310
Notice: Undefined variable: exlorlist in /home/.sites/69/site292/web/photolog/snippets.php on line 312

what about these errors?

EDITED:

that solved the problem:
http://photography-on-the.net/forum/showthread.php?t=28760

[manutremo]

I am getting this error in the details area of the photo showing:

Notice: Undefined index: currently_browsing in D:\Mis documentos\htdocs\gallery\photodetails.php on line 505

You can have a look at it in

http://viajeros.no-ip.info/gallery/photo.php?photo=3559

[Pekka]

I am getting this error in the details area of the photo showing:

Notice: Undefined index: currently_browsing in D:\Mis documentos\htdocs\gallery\photodetails.php on line 505

You can have a look at it in

http://viajeros.no-ip.info/gallery/photo.php?photo=3559

There is one translation missing from some language files: in photo.php language translation file

$translated["currently_browsing"] = "currently browsing";

is missing,

[manutremo]

Thanks Pekka, already corrected.

[okapi]

Mine was very slow untill I uninstall the rc3_speeder.
I do not know the reason, I was just trying to undone things one by one.

I found the reason for this problem and will post a fix pack tomorrow. Speeder code is just ok, but duplicate category id 1's have appeared all over the place which mess and slow things up. Tomorrow you'll get Analyze/Repair code which fixes those id's so that speeder code will work normally. I have also added guardian code to seek and kill that id problem on image upload and other editors because I can not reproduce it here. So it will not happen again but nevertheless I'll keep working on finding the real cause (perhaps PHP function bug).

All above fixes plus few others will be posted tomorrow (Saturday) evening.

for me EE RC3 runs very smoothly and fast now, but nevertheless may i ask when you will post these fixes?

[Pekka]

for me EE RC3 runs very smoothly and fast now, but nevertheless may i ask when you will post these fixes?

Sorry about the Saturday deadline missed - I got couple of bug reports which I had to fix. THe RC 4 installer is coming today - I'm just now checking that 1.22 and 1.3 updaters work.

New:

- added filefunction URL wrapper setting to rethumbnailer and export.
- fixed several problems in export.
- added panorama to powertools.
- added new field: media (add in SETTINGS_dropdowns.php).
- changed preferred order of photo header reading from IPTC/XMP (IPTC field 105 "headline" is now most important).
- when "display photo detail" is OFF photo detail switch will be hidden automatically.
- fixed uncookied n/a and wrong data reference problems.
- fixed problems with multiple category id 1's on same photo. Analyze repair has a detect and fix for systems affected by this.
- fixed bug with sizepath menu sorting (sort by menutext)

[tommykjensen]

Just got these errors when trying to set a few fields for photos in one exhibition with powertools.

Warning: reset(): Passed variable is not an array or object in \ee\xyz\EDITOR_powertools.php on line 247

Warning: Invalid argument supplied for foreach() in \ee\xyz\EDITOR_powertools.php on line 252
zyx is not the correct name of my input directory.

The SQL query formed looked like this:

UPDATE
ee_photo,
ee_exhibition,
ee_photo_to_exhibition
SET
ee_photo.ee_country_id = '48', ee_photo.ee_location_id = '113'
WHERE

ee_photo.ee_photo_id = ee_photo_to_exhibition.ee_photo_id AND ee_exhibition.ee_exhibition_id = ee_photo_to_exhibition.ee_exhibition_id AND (ee_exhibition.ee_exhibition_id = '13')

AFFECTED DATABASE ROWS: none, query failed


In step one "select filtering" I selected one exhibition.

In step one "replace data with" I set country, location and categories to the values I wanted.

In step 3 "select photos" I did not select any photos as I assumed selecting an exhibition and no individual photo would affect all photos in the selected exhibition.

[Pekka]

In step 3 "select photos" I did not select any photos as I assumed selecting an exhibition and no individual photo would affect all photos in the selected exhibition.

Currently you must select some photos. Your idea of how if should function is fine, but it does not work that way now (later it will have exhibition target selection). The error message reflects that - I'll hide the message in RR 4.

Thanks for reporting.

[c_by_sinus]

Markus, for example, is putting his original filename "sin01450" in this field.

However, also for me it's not 100% clear what to put in. Somebody can give me more input? :?

Hi Tom,
If you do some searches on the net, then you will found out (at least I found out), that iptc is a realy standard, but some fields, although the standard says, what to fill in, are used different.
Hence I would do at least one: make a choice and then do the same forever, DO NOT MIX fields.
Because if you would later decide, that the values from your field "objectname" should change with the field "Headline" (for example), than this could be done easy with a program like IMatch. Hence you must be consistenly with your work.

There are some fields, like caption, headline, date and so on, what are filled out mostly in the same manner from users. But a lot does for example use ONLY the caption (description) and maybe still copyright, then they leaves the rest blank.
Therefore you are quite free how to fill some fields, what are used not often.
There are also some big agencies like Reuters or Stern (magazin) what gives some advises, but also these are not the same - except as I said, the most used fields.

I guess, my table gives quite a good overview, but of course I be always thankful for news in this area.

Hey, best wishes from Switzerland, raining, raining, regen, regen ....
Markus

[tommykjensen]

In step 3 "select photos" I did not select any photos as I assumed selecting an exhibition and no individual photo would affect all photos in the selected exhibition.

Currently you must select some photos. Your idea of how if should function is fine, but it does not work that way now (later it will have exhibition target selection). The error message reflects that - I'll hide the message in RR 4.


I just tried this one more time in RC4. This time I did select both an exhibition and the relevant photos from that exhibition in order to set the lens correctly.

However it did not work, this was the SQL query done:


UPDATE
ee_photo,
ee_exhibition,
ee_photo_to_exhibition
SET
ee_photo.ee_lens_id = '1', ee_photo.ee_photo_panorama = 'NO'
WHERE
(ee_photo.ee_photo_id = '2078' OR ee_photo.ee_photo_id = '2079' OR ee_photo.ee_photo_id = '2080' OR ee_photo.ee_photo_id = '2081' OR ee_photo.ee_photo_id = '2082' OR ee_photo.ee_photo_id = '2083' OR ee_photo.ee_photo_id = '2084' OR ee_photo.ee_photo_id = '2085' OR ee_photo.ee_photo_id = '2086' OR ee_photo.ee_photo_id = '2087' OR ee_photo.ee_photo_id = '2088' OR ee_photo.ee_photo_id = '2089' OR ee_photo.ee_photo_id = '2090' OR ee_photo.ee_photo_id = '2091' OR ee_photo.ee_photo_id = '2092' OR ee_photo.ee_photo_id = '2093' OR ee_photo.ee_photo_id = '2094' OR ee_photo.ee_photo_id = '2095' OR ee_photo.ee_photo_id = '2096' OR ee_photo.ee_photo_id = '2097' OR ee_photo.ee_photo_id = '2098' OR ee_photo.ee_photo_id = '2099' OR ee_photo.ee_photo_id = '2100' OR ee_photo.ee_photo_id = '2101' OR ee_photo.ee_photo_id = '2102' OR ee_photo.ee_photo_id = '2103' OR ee_photo.ee_photo_id = '2104' OR ee_photo.ee_photo_id = '2105' OR ee_photo.ee_photo_id = '2106' OR ee_photo.ee_photo_id = '2107' OR ee_photo.ee_photo_id = '2108' OR ee_photo.ee_photo_id = '2109' OR ee_photo.ee_photo_id = '2110' OR ee_photo.ee_photo_id = '2111' OR ee_photo.ee_photo_id = '2112' OR ee_photo.ee_photo_id = '2113' OR ee_photo.ee_photo_id = '2114' OR ee_photo.ee_photo_id = '2115' OR ee_photo.ee_photo_id = '2116' OR ee_photo.ee_photo_id = '2117' OR ee_photo.ee_photo_id = '2118' OR ee_photo.ee_photo_id = '2119' OR ee_photo.ee_photo_id = '2120' OR ee_photo.ee_photo_id = '2121' OR ee_photo.ee_photo_id = '2122' OR ee_photo.ee_photo_id = '2123' OR ee_photo.ee_photo_id = '2124' OR ee_photo.ee_photo_id = '2125' OR ee_photo.ee_photo_id = '2126' OR ee_photo.ee_photo_id = '2127' OR ee_photo.ee_photo_id = '2128' OR ee_photo.ee_photo_id = '2129' OR ee_photo.ee_photo_id = '2130' OR ee_photo.ee_photo_id = '2131' OR ee_photo.ee_photo_id = '2132' OR ee_photo.ee_photo_id = '2133' OR ee_photo.ee_photo_id = '2134' OR ee_photo.ee_photo_id = '2135' OR ee_photo.ee_photo_id = '2136' OR ee_photo.ee_photo_id = '2137' OR ee_photo.ee_photo_id = '2138' OR ee_photo.ee_photo_id = '2139' OR ee_photo.ee_photo_id = '2140' OR ee_photo.ee_photo_id = '2141' OR ee_photo.ee_photo_id = '2142' OR ee_photo.ee_photo_id = '2143' OR ee_photo.ee_photo_id = '2144' OR ee_photo.ee_photo_id = '2145' OR ee_photo.ee_photo_id = '2146' OR ee_photo.ee_photo_id = '2147' OR ee_photo.ee_photo_id = '2148' OR ee_photo.ee_photo_id = '2149' OR ee_photo.ee_photo_id = '2150' OR ee_photo.ee_photo_id = '2151' OR ee_photo.ee_photo_id = '2152' OR ee_photo.ee_photo_id = '2153' OR ee_photo.ee_photo_id = '2154' OR ee_photo.ee_photo_id = '2155' OR ee_photo.ee_photo_id = '2156' OR ee_photo.ee_photo_id = '2157' OR ee_photo.ee_photo_id = '2158') AND
ee_photo.ee_photo_id = ee_photo_to_exhibition.ee_photo_id AND ee_exhibition.ee_exhibition_id = ee_photo_to_exhibition.ee_exhibition_id AND (ee_exhibition.ee_exhibition_id = '14')

AFFECTED DATABASE ROWS: none, query failed


If I leave out the exhibition in step one and only select photos in the last box it works. This is the resulting query:

UPDATE
ee_photo
SET
ee_photo.ee_lens_id = '1', ee_photo.ee_photo_panorama = 'NO'
WHERE
(ee_photo.ee_photo_id = '2078' OR ee_photo.ee_photo_id = '2079' OR ee_photo.ee_photo_id = '2080' OR ee_photo.ee_photo_id = '2081' OR ee_photo.ee_photo_id = '2082' OR ee_photo.ee_photo_id = '2083' OR ee_photo.ee_photo_id = '2084' OR ee_photo.ee_photo_id = '2085' OR ee_photo.ee_photo_id = '2086' OR ee_photo.ee_photo_id = '2087' OR ee_photo.ee_photo_id = '2088' OR ee_photo.ee_photo_id = '2089' OR ee_photo.ee_photo_id = '2090' OR ee_photo.ee_photo_id = '2091' OR ee_photo.ee_photo_id = '2092' OR ee_photo.ee_photo_id = '2093' OR ee_photo.ee_photo_id = '2094' OR ee_photo.ee_photo_id = '2095' OR ee_photo.ee_photo_id = '2096' OR ee_photo.ee_photo_id = '2097' OR ee_photo.ee_photo_id = '2098' OR ee_photo.ee_photo_id = '2099' OR ee_photo.ee_photo_id = '2100' OR ee_photo.ee_photo_id = '2101' OR ee_photo.ee_photo_id = '2102' OR ee_photo.ee_photo_id = '2103' OR ee_photo.ee_photo_id = '2104' OR ee_photo.ee_photo_id = '2105' OR ee_photo.ee_photo_id = '2106' OR ee_photo.ee_photo_id = '2107' OR ee_photo.ee_photo_id = '2108' OR ee_photo.ee_photo_id = '2109' OR ee_photo.ee_photo_id = '2110' OR ee_photo.ee_photo_id = '2111' OR ee_photo.ee_photo_id = '2112' OR ee_photo.ee_photo_id = '2113' OR ee_photo.ee_photo_id = '2114' OR ee_photo.ee_photo_id = '2115' OR ee_photo.ee_photo_id = '2116' OR ee_photo.ee_photo_id = '2117' OR ee_photo.ee_photo_id = '2118' OR ee_photo.ee_photo_id = '2119' OR ee_photo.ee_photo_id = '2120' OR ee_photo.ee_photo_id = '2121' OR ee_photo.ee_photo_id = '2122' OR ee_photo.ee_photo_id = '2123' OR ee_photo.ee_photo_id = '2124' OR ee_photo.ee_photo_id = '2125' OR ee_photo.ee_photo_id = '2126' OR ee_photo.ee_photo_id = '2127' OR ee_photo.ee_photo_id = '2128' OR ee_photo.ee_photo_id = '2129' OR ee_photo.ee_photo_id = '2130' OR ee_photo.ee_photo_id = '2131' OR ee_photo.ee_photo_id = '2132' OR ee_photo.ee_photo_id = '2133' OR ee_photo.ee_photo_id = '2134' OR ee_photo.ee_photo_id = '2135' OR ee_photo.ee_photo_id = '2136' OR ee_photo.ee_photo_id = '2137' OR ee_photo.ee_photo_id = '2138' OR ee_photo.ee_photo_id = '2139' OR ee_photo.ee_photo_id = '2140' OR ee_photo.ee_photo_id = '2141' OR ee_photo.ee_photo_id = '2142' OR ee_photo.ee_photo_id = '2143' OR ee_photo.ee_photo_id = '2144' OR ee_photo.ee_photo_id = '2145' OR ee_photo.ee_photo_id = '2146' OR ee_photo.ee_photo_id = '2147' OR ee_photo.ee_photo_id = '2148' OR ee_photo.ee_photo_id = '2149' OR ee_photo.ee_photo_id = '2150' OR ee_photo.ee_photo_id = '2151' OR ee_photo.ee_photo_id = '2152' OR ee_photo.ee_photo_id = '2153' OR ee_photo.ee_photo_id = '2154' OR ee_photo.ee_photo_id = '2155' OR ee_photo.ee_photo_id = '2156' OR ee_photo.ee_photo_id = '2157' OR ee_photo.ee_photo_id = '2158')

AFFECTED DATABASE ROWS: 49