CopperExport – original comments

CopperExport comments

In the original CopperExport web page, I had left comments enabled. The response was incredible! So much that the page was getting too long. To keep it manageable, I disabled comments, and for new feedback, I would encourage you to use the forums, or email me directly. The original comments still can be read below. Thanks to everyone who submitted them!

Advertisements

77 responses to “CopperExport – original comments

  1. Thank you, this is exacly what I been looking for so long now.

    If I can make a suggestion for future upgrades is to have a “rename to exif date” option, example, i renamme alll my files so I can go to the coppermine Admin Cpp and renamme the files based on the fillename date (ex: 2003-01-01-14-47-39.jpg becomes Jan, 1st 2003 – 14:47:39) … it woudl be nice if the script did it on the fly πŸ™‚

    once again, thank you .. I was sending my Images to a XP machine so I coold use xp_publish, this is much better

  2. have to say a big thank you to you for developing this! before i would have to ftp into my server to batch upload the files but couldn’t add comments or titles directly. This way is so much simpler, and using iphoto already, is a dream to use. Well done!!!

  3. NullMind and jads, thank you for the comments! I am very happy that you have found it useful.

    NullMind, just to make sure I fully understand your suggestion: the final name you would like for the file is “Jan, 1st 2003 – 14:43:39.jpg”, is this correct?

    Update: actually, from your gallery, I gather it’s the opposite, yes? You have your files named as YYYY-MM-DD-hh-mm-ss.jpg.

  4. Hitchhiker

    Go to the “Admin Tools” in Coppermine

    you will see this option “Filename β‡’ File title (1)”

    it does this

    “Change 2003_11_23_13_20_20.jpg to 11/23/2003 13:20”

    but it will also change

    “2003-11-23-13-20-20.jpg to 11/23/2003 13:20”

    (not sure iif the “-” or “_” are relevant”

    so … no .JPG at the end,, this doesnt change the filename .. just the “Title”

    Here is an example how it loooks once it’s done

    http://theregos.com/thumbnails.php?album=130

    I posted a link for this excellent hack everywere .. so hopefully more will come and check it, I bellieve good scripts like these need to be announced πŸ™‚

  5. Aha, I get it now. Consider it officially added to the list of enhancement requests πŸ™‚

    Thanks again!

  6. PS – I am using iPhoto 5 .. works great

  7. That’s the first confirmation I get about iPhoto 5 – great news, thanks.

  8. THANK YOU! I was using a perl script to do the same thing not so well. This is an excellent solution. I have one request so far…

    An option to “sync” the album, meaning that pictures not in the iPhoto selection will get deleted from the coppermine album So if I add a picture to an album in iPhoto, select the album, and upload, the new picture gets remotely added. If I delete a picture, select the album and upload, the picture gets remotely deleted.

    I’ll second the iPhoto 5 usability comment: works great.

  9. Tree – thanks for the comment! I am very happy you have found it useful πŸ™‚

    About your suggestion: for the moment, all the operations are at the individual picture level (the export plugin doesn’t know about the selected album in iPhoto, only about selected photos), but I want to look into doing album-level operations at some point. When this happens, your sync idea should be possible.

  10. One more advise .. have a mailinglist so we can be notified of any future updates πŸ™‚ and a donation paypal address πŸ˜‰

  11. NullMind: thanks for the suggestions. I’ve added the PayPal button, and will set up an announcements mailing list soon. I haven’t had much time to work on CopperExport lately, but I have a bunch of ideas floating in my head, so hopefully there will be a new version in the near future.

  12. Okay, I’m new to iPhoto and the Mac, but I can’t figure out how to use this. I’ve followed the instructions and it seemed to work, but I don’t see any changes in iPhoto5. I do have the flickr plugin installed too if that matters.

  13. Bill: the use of this plugin is very similar to the Flickr plugin. When you select “Export…” you should see an additional tab that says “Coppermine” (and you should have one that says “Flickr” from the other plugin). Is this not the case?

  14. I was able to install it just fine following the instructions, but I get an error each time I try to upload a file. I get a message saying that the largest file size that can be uploaded is 1024kb, but the file isn’t even that big. Can’t figure out how to fix this. any ideas?

    Looks to be great other than that.

  15. keno: there are two places where you have to increase the upload limit: In the php.ini file in your web server, you have to modify the upload\_max\_filesize parameter. For example:

    upload_max_filesize = 8M

    Also, in the Coppermine Config screen, in the “Files and thumbnails settings”, you have to raise the value of the “Max size for uploaded files” parameter. This parameter is given in KB, so to match the 8M, you would have to set it to 8096.

    You say that the file isn’t even 1024KB – what size is it? Also, it could be that the limit in Coppermine is 1024KB (hence the one the error is reporting) but the limit in php is set to a lower value.

    I hope this helps.

  16. K, it’s working now. I think I picked the top folder instead of the one inside. However it fails to upload with Coopermine 1.1.1. I will upgrade my server stuff and try again.

  17. Upgraded to 1.3.2 (the latest I think) and it works just fine. Thanks for the help.

  18. hitchhiker: where would the php.ini file be? I can’t find it anywhere. Maybe it’s not accessible to me? It’s no in the coppermine folder so I’m figuring it might be somewhere i don’t have access to. I did change the file size to be larger in the controls for Coppermine. the file I’m trying to upload is only 332kb and it will upload fine if I use the “upload files” feature in coppermine rather than the plugin

  19. Hey… Something strange is happening on my G4 iBook. The plugin worked just GREAT the first time I used it. I left the house for a little while to eat dinner with my girlfriend, and then I came back to upload some more pictures and when I click File->Export… it waits for a second with File highlighted, and then does nothing… I’ve rebooted, removed and added the plugin again… no luck. Any suggestions?

  20. Bryan: Could you please look at your console log (in a Terminal window, type “tail -f /Library/Logs/Console/yourusername/console.log”), and see if any messages appear when you select “Export” – they may help in diagnosing the problem.

  21. Thanks for your quick reply… here’s what I got! Let me know if i can help with anything!

    Katie-Lairds-Computer:~ katielaird$ tail -f /Library/Logs/Console/katielaird/console.log
    Try ‘sips –help’ for help using this tool
    2005-02-26 14:21:57.432 iPhoto[527] Cannot parse a NULL or zero-length data
    Warning: /Users/katielaird/Pictures/iPhoto Library/2004/12/17/Chinesemcdonalds.jpg not a valid file – skipping
    Error 4: no file was specified
    Try ‘sips –help’ for help using this tool
    2005-02-26 14:22:19.185 iPhoto[527] Cannot parse a NULL or zero-length data
    Warning: /Users/katielaird/Pictures/iPhoto Library/2004/12/17/Chinesemcdonalds.jpg not a valid file – skipping
    Error 4: no file was specified
    Try ‘sips –help’ for help using this tool
    2005-02-26 14:22:43.924 iPhoto[527] Cannot parse a NULL or zero-length data
    Warning: /Users/katielaird/Pictures/iPhoto Library/2004/12/17/Chinesemcdonalds.jpg not a valid file – skipping
    Error 4: no file was specified
    Try ‘sips –help’ for help using this tool
    2005-02-26 15:44:21.431 iPhoto[814] Cannot parse a NULL or zero-length data
    Warning: /Users/katielaird/Pictures/iPhoto Library/2004/12/17/Chinesemcdonalds.jpg not a valid file – skipping
    Error 4: no file was specified
    Try ‘sips –help’ for help using this tool
    2005-02-26 15:44:47.791 iPhoto[814] Cannot parse a NULL or zero-length data

  22. My problem is fixed, it uploads now. One of my albums had the first charcter as the ‘@’ symbol and it was hanging up the export tool. I go rid of the ‘@’ symbol and the export tool started to work just fine. It didn’t matter that the album with the ‘@’ was way down in my album list, just that it was there at all.

    This tool is great! I already love it!

  23. Hmm… strange. It seems some of the pictures in iPhoto were giving the exporter some trouble. I deleted them and then readded them to the database… things are working just fine now. Great tool!!!

  24. Bryan, keno: I’m happy the problems are solved now! Thank you for the nice comments, I’m very happy that you find the tool useful πŸ™‚

    Bryan: from the log, it seems that some of your pictures contained some invalid information, which was causing the sips tool to fail. If you don’t mind, would you send me one of these pictures, so I can try to debug the problem?

    keno: thanks for identifying the problem with the @ sign. I will try to fix it soon.

  25. hello.

    i’ve installed the plugin following the instructions included, but it is not showing up as one of the options.

    i am using iphoto 4.03

    thinking it could be because the flickr plugin was already installed, i disabled the flikr plugin, but the coppermin export is still not showing up.

    help?

    thanks

  26. Hi Adrian – two things to check:

    * Does the Copperexport plug-in show up correctly in the iPhoto info dialog (in the plugins section)?
    * Have you quit and restarted iPhoto after installing the plugin? (I assume so, from your message, but just to state the obvious).

    If this doesn’t help, could you please run Console (in Applications > Utilities), and see if any error messages appear when you run iPhoto and select File > Export. Please send them to me by email, and we’ll see if them help in diagnosing the problem.

  27. Working with iPhoto 5, this is great! I just tested with CPG 1.41 beta, and works great as well. Question: (Back to 1.32 of CPG) …I tried to bridge with my mambo site login to consolidate user auth, etc. When I’m bridged, I can’t authenticate. Is this an XP_PUBLISH.php issue? Thanks much for a great tool!

  28. Kevin, thanks for the nice comments! It’s nice to hear that it works with CPG 1.4 – I’ve been meaning to try it but haven’t had the time.

    About your question: I know nothing about mambo and how it bridges other programs, but if I can help from the plugin side, I’d be happy to try. CopperExport uses the standard login facility in xp\_publish.php, which sets two cookies (cpg130\_uid and cpg130\_pass, where the prefix can change as per your configuration) to indicate that you are logged in. After logging in, CopperExport uses the publish routine in xp\_publish.php, and responds with the appropriate cookies. So if your bridging process can set and later request cookies to indicate proper authentication, then the plugin should work fine (the names of the cookies don’t really matter, the plugin simply sends whatever cookies have been set by the site).

    Please let me know if this helps. Feel free to email me instead of using the comments here.

  29. I have protected my family’s Coppermine-gallery with htaccess. Is it possible to use this script in with it? Now it doesn’t seem to work. I’d really like to switch totally to Mac πŸ™‚

  30. Burana – are you using the .htaccess to ask for an additional password, apart from the Coppermine one? The plugin does not support HTTP authentication. I might look into adding support for it, but since Coppermine already does authentication, do you really need it?

    One possible workaround for now would be in your .htaccess to exclude xp_publish.php from needing authentication.

  31. I use .htaccess to prevent anonymous Googlers from entering the family gallery at all and this seems to be the most convenient way so far. Messing around with Coppermine’s own authentications werent so simple. But I will try excluding xp_publish.php and tell if it works or not. Thanks for suggestion.

  32. Err, it seems that i am not advanced enough to cast a .htaccess spell that would require basic authentication from all other files in coppermine directory and beyond except the xp_publish.php. Any help would be greatly appreciated πŸ™‚

  33. I can load the xp_publish.php in my web browser okay (modified version from CopperExport). I can upload images using the standard CPG upload okay. I try and use CopperExport and I get a 403 forbidden error. Am I missing something here? TIA!

  34. comccoy: do you have some other authentication mechanism in place, apart from the standard Coppermine login?

    Could you please try the following: run the Console utility (in Applications -> Utilities), filter for “iPhoto”, and then trigger the error. Please send me what appears in the console, as it should contain a more detailed error message. Also, please send me the full text in the error dialog you get.

  35. I’ll do one better and send you the sniffed packets as well. I’ll send them to copperexport@zzamboni.org. Thanks!

  36. Thank you ever so much for this ,I can’t tell you how long I’ve been looking for a plugin like this, ever since I switched from PC to Mac, and beeing on a php_safemode_on server, I’ve been looking !

    Thank you for your great plugin πŸ˜€

  37. Andreas – thanks for the nice comments! I am very happy you have found the plugin useful πŸ™‚

  38. So, my camera saves files as TIFF images, which are what all my iPhoto images are (of course). Yet, uploading them to coppermine via CopperExport, I get an error about no file uploaded. I’m assuming this is because they are tiffs and not jpg’s. It would be perfect if CopperExport had an option to convert non-jpg images to jpg.

  39. Shan – I will investigate uploading tiff files. Thanks for the comment!

    I went to add your request to the “Features request” page on berliOS and saw that you did that already. Thanks πŸ™‚

  40. Thanks for CopperExport! Very handy. But… I have a problem wih CopperExport 0.2.1 with iPhoto 5.0.2 : each time i try to export via CopperExport, iPhoto just hangs, indefinitely, waiting for the export window to appear. I trashed CopperExport prefs file to no avail (in fact, something changed: the window now appears but with nothing drawn in it, just the frame..). And I looked in the logs and nothing is written… CopperExport was working in iPhoto 5.0 and 5.0.1.

  41. Im trying to use CopperExport 0.2.1 with iPhoto 5.0.2 and like Gilles iPhoto hangs, but my eventualy crashes and generates a crash log.

  42. Wow, this is exactly what I was looking for. I just wanted to say like the last 2 post, I also can’t get copperExport 0.2.1 to work with iPhoto 5.0.2. it just locks up iPhoto. If you need any more info please let me know. Thanks for the great app!

  43. iPhoto 5.0.2 ins’t working with CopperExport for me either…. is it fixable?

  44. Gilles, Ryan, Craig, Tree – sorry it took me some time to reply, I’ve had visitors and haven’t been checking the messages as frequently.

    About the issue with iPhoto 5.0.2 – sadly I can’t reproduce it. Would you please try removing the plugin completely (from the Finder info dialog for iPhoto), run iPhoto to verify that it’s gone, and then reinstall CopperExport. Does the problem persist? Do you have any additional third-party plugins installed? At which point precisely does the plugin hang (does the export dialog appear when you click “Export”, or is it before that?)

    Thanks for the nice comments! I hope we can get this problem fixed for you.

  45. amazing dude. after my .mac trial expired, i needed an easy way to export my albums to the web (.mac accounts are mad expensive). thanks for such a great tool.

  46. eh…im having that Error 403 crap. how do i fix this? please email me at nerogtr@gmail.com

  47. cmd=login&lang=english
    2005-04-28 00:16:28.943 iPhoto[975] HTTP status code: 403, response string: forbidden
    2005-04-28 00:16:28.943 iPhoto[975] Error detected: HTTP Error 403: forbidden (code 403)
    2005-04-28 00:16:35.493 iPhoto[975] Posting to URL: http://www.neroband.com/nerogtr/xp_publish.php?

    thats the error from the console.

  48. I downloaded CopperExport to use while I was on a trip recently and I think it’s a great program. However, there was one thing where I think it could use some improvement.

    It took me forever to figure out that, to set the image size for all photos, you have to select one of the photos first. It would be nice it there was text somewhere in the window instructing you to select a photo first. Now it’s obvious, but having the button say “Apply To All” made me think that I didn’t need to select a photo before clicking the button. [Is there a ReadMe file that explains this? I couldn’t find one.]

    I see that there is grayed out text in the Title field that says “No Selection”, but in the size boxes, all that shows up is “No Se”, which, of course, doesn’t tell you much.

    All in all, it’s a nice addition to iPhoto 5.

    Thank you.

    BTW, it works fine for me with iPhoto 5.0.2

  49. Well i reinstalled my machine with Tiger and now it works, must have been something else messing CopperExport up.
    Thanks for the great app.

  50. Frank – thanks for the feedback. I have to confess I’m puzzled myself by that behavior sometimes πŸ™‚ I will try to fix it as soon as possible.

    Ryan – I’m happy it’s working with Tiger now.

    Thanks for the nice comments! I’m happy you have found the plugin useful.

  51. Any luck on the “covert to jpg” feature? My poor website hasn’t been updated with baby pictures because of this :D. My family is bugging me about it!

    Shan

  52. First, let me give you a big THANK YOU of preferrably mucha gracias, DankeschΓΆn or merci vielmals πŸ˜‰
    This plug-in certainly is great to use, easy to install and good looking.

    But I can confirm a missbehaviour reported above (Post No. 14, 18, 22 from keno – maybe also 21). In my case, I did get an error for wrong width although I reduced the size appropriately:
    Error detected: The size of file you have uploaded is too large (maximum allowed is 1024 x 1024).

    I followed up on the error and found the cause:
    If the filename of the pic in iPhoto includes a non-standard Ascii-Char (above it was the @-sign, in my case a single quote), it is not read properly due to system differences in char-tables (i suppose).
    This is my console error:
    _____
    2005-05-30 13:30:19.043 iPhoto[5055] Uploading image /Users/michaelraich/Pictures/iPhoto Library/2003/10/08/UmΒ΄s Haus 012.jpg

    Error: Error modifying file
    _____
    The file actually is stored as __Um??s Haus 012.jpg__ thus cannot be found by __UmΒ΄s Haus 012.jpg__

    So call it an iPhoto inconsistency or just plain bad char encoding but the result is that the image cannot be resized. It seems that iPhoto uses an OS X alias for the filename and according to the Cocoa documentation, these are not automatically handled.

    A possible workaround (supposedly in CpgImageRecord.h) might be this one found at the ADC reference library:
    http://developer.apple.com/documentation/Cocoa/Conceptual/LowLevelFileMgmt/Tasks/ResolvingAliases.html

    I haven’t had a thorough look into the code, But this jumped right into my face as I had to deal with a similar problem before. But I might be wrong after all.

  53. Shan – sorry, I haven’t had any time lately to work on CopperExport lately, but the tiff-to-jpeg conversion is number one in my list of tasks. I will get it done soon!

    Michael – thanks for the feedback, and for the diagnosis! I will look at this in more detail as soon as I can.

    Thanks for the nice words, too! πŸ™‚

  54. Great program, but I do have one problem with it. I type in a title and description and everything, but none of that transfers when I upload it; all I get is a picture in my album with no title or description. I’m using iPhoto 5 and CPG 1.3.3.

    Am I doing something wrong? Thanks.

  55. Schlep – it sounds as if you have not installed the server-side patch that comes with CopperExport. Without this patch, Coppermine does not recognize titles, descriptions or tags. The instructions are in the ReadMe file. Please make sure you use the patch from version 0.2.1, as previous versions had a potential security problem.

  56. I put them at http://www.criticaldigital.com/copper.zip

    That zip is exactly what my camera produces. You can bring them into iPhoto like that was a camera’s card πŸ˜€

    Shan

  57. I get an timeout error and the code (-1001). Then it asks me to check the login password.
    After that the site is actually out of reach for about ten minutes. Seems like the server crashes or something.
    This is from the console:
    2005-06-05 14:01:36.868 iPhoto[968] ###### Error: code=-1001, domain=NSURLErrorDomain, localizedDesc=tidsavbrudd
    2005-06-05 14:01:36.868 iPhoto[968] Error detected: tidsavbrudd (code -1001)
    “Tidsavbrudd” is norwegian and means timeout.
    Coppermine version 1.3.2, iPhoto version 4.03.

  58. Edit:
    Actually, first I get an error ,HTTP error 500, and a message saying it could not log in. Then if i try again the other error comes (se message above, no 57).
    So this probably is a server problem. Any suggestions?

  59. Jon – it does indeed sound like a server problem. Do you have access to your web server’s error_log file? That might give a better clue about what the problem is.

  60. Thanx Hitchhiker
    Here’s the errorlog:

    [Sun Jun 5 15:55:40 2005] [error] [client 84.118.33.199] mod\_security: Access denied with code 500. Error parsing multipart parameters: Error normalizing parameter value: (null) [hostname “www.galleri.selsaas.no”] [uri “/galleri/xp\_publish.php?cmd=login〈=english”] [unique_id QqMEXD5GDs0AAFCzHN8]

    Does this tell you something?

  61. Yes. There’s been other reports of CopperExport not working with servers with mod_security installed. Sadly, I haven’t had a chance to look at it and fix it… I promise to do it ASAP.

  62. Thank you.
    Thats good news. Looking forward to the update.

  63. I love this plug-in!

    The only problem I’ve run into is that under iPhoto 5.0.2 and OS X Tiger, uploads hang after 3 or 4 photos at 800×600. When they hang, there is no network traffic and I am able to cancel out of the upload and return to using iPhoto.

    I have this problem on two different computers. I had the same problem on both computers running OS X 10.3.9. I’ve had the problem even after trashing and reinstalling the plug-in. I see that this is similar to other problems folks have been having and I’m wondering if there’s any new word on what could be causing the problem and how to fix it.

    Thanks!!!
    ~Darrel

  64. yeah, i’ve been seeing the same problems as Darrel. It constantly hangs…

    -s

  65. I’m seeing some hanging, but my larger problem (since that is infrequent) is that the export plugin consistently errors out mid-upload. I will be a couple files into an upload and get an error:

    No file was uploaded! If you have already selected a file to upload, check that the server allows file uploads…xp_publish.php / Line 782.

    It appears that the plugin is not properly issuing the post request. The pertinent line in xp_publish is:

    // Test if the filename of the temporary uploaded picture is empty
    if ($HTTP_POST_FILES[‘userpicture’][‘tmp_name’] == ”) simple_die(ERROR, $lang_db_input_php[‘no_pic_uploaded’], __FILE__, __LINE__);

    Any suggestions you have on how to fix this would be great. Thanks.

  66. By the way, otherwise this is a great plugin, exactly what I needed.

  67. Darrel, Steve, parker – thanks for the feedback. I am currently swamped with work, but I am keeping an eye on the comments, and will look into it as soon as time allows. Thanks for your patience!

  68. Very cool plug-in. But I’m getting an error. It says that “exec() disabled for security reasons.” Does that mean, i won’t be able to use this plug-in with my current webhost?

  69. Diego, have you had a chance to see the xp_publish.php from version 1.4 (beta) of CopperExport? Do you know if its safe to replace the xp_publish from copperexport so I can upload descriptions, etc. from iPhoto?? Thanks! Kevin

  70. Kevin – I haven’t tried cpg1.4 myself, but from looking at xp_publish.php, it seems a very similar change to the previous version should work. I wouldn’t replace the whole file, but could you try the patch below, and let me know if it works? Thanks!

    *** xp_publish.php.141 Sat Jul 16 18:39:00 2005
    — xp_publish.php Sat Jul 16 18:39:10 2005
    ***************
    *** 702,710 ****
    if (!USER_ID || !USER_CAN_UPLOAD_PICTURES) simple_die(ERROR, $lang_errors[‘perm_denied’], __FILE__, __LINE__);

    $album = (int)$_GET[‘album’];
    ! $title = ”;
    ! $caption = ”;
    ! $keywords = ”;
    $user1 = ”;
    $user2 = ”;
    $user3 = ”;
    — 702,710 —-
    if (!USER_ID || !USER_CAN_UPLOAD_PICTURES) simple_die(ERROR, $lang_errors[‘perm_denied’], __FILE__, __LINE__);

    $album = (int)$_GET[‘album’];
    ! $title = addslashes($HTTP_POST_VARS[‘title’]);
    ! $caption = addslashes($HTTP_POST_VARS[‘caption’]);
    ! $keywords = addslashes($HTTP_POST_VARS[‘keywords’]);
    $user1 = ”;
    $user2 = ”;
    $user3 = ”;

  71. Thanks much! Actually, in spite of me not being a PHP programmer, I actually diff’d the two php files, and played with the title field only, and it didn’t work for me. I put your suggestions in for the other fields as well and did some more testing. From what I can tell, I’m not getting the information passed through on any platform, so my guess there is a problem elsewhere in the script…when I test the http_post_vars I get nulls for anything I try to retrieve off the $HTTP_POST_VARS array.

    Thanks for your help!

    Kevin

  72. had problems with 403 error with iPhoto 5.03.
    Problem is, as I understand with Mod_Security that I have running on my VPS.

    Found this tip:
    Make a .htaccess file in the directory where Coppermine is installed, and put in this line (without qoutes):

    “SecFilterScanPOST Off”

    Then upload to my coppermine workes for me with iPhoto 5.03 on OS X 10.3.8
    Coppermine 1.33.

    But I do not know what this “off” qoute will do regarding the security on your site, or the server you are on.

  73. Henrik Tilly

    Hi!

    First off, great plugin!! This is exactly what I have been looking for !!

    Im running OSX 10.4.2
    iPhoto 5.0.3
    Coppermine 1.3

    The problem Im having is that when I try to enter the user / password in the export process iPhoto just crashes 😦

    I can fill out the username and the URL, but as soon as I put the marker in the passwordfield it just crashes 😦

    Any ide how to solve this? I would really love to get it working !

    ps. how about a forum this great plugin. ds.

    BR
    Henrik T

  74. Hey..

    I’m running into a problem trying to get things up and running for the first time. When I hit the export button, I get an error telling me that there are no albums where I can upload pictures, and I don’t have permission to create new albums.
    I’ve checked every setting I could find, but everything seems to be in order.

    I should also mention that I’m running a beta version of CPG (1.4.1)… My thinking is that the problem has something to do with this.
    But comparing the two xp_publish files (the one that came with 1.4.1 and yours), I can’t seem to find any major differences.
    Mind you, I know very little about this sort of thing, so something small could have easily slipped by me.

    Anyway, if anyone can offer any insight, I’d very much appreciate it.

    thanks

    -d

  75. I’m using iPhoto 5.0.3, Tiger 10.4.1, and Coppermine 1.4.1. xp_publish.php has had some signifigant upgrade. I’ve been messing with the file without mcuh success yet. I’d love to be able to upload descriptions… anyone having any luck with this?

  76. Hi – I finally had some time to play with Coppermine 1.4.1beta. This is the patch that has to be applied to xp_publish.php in this version to get it to work. I’ll post the file properly a little later, but here it is: (the lines starting with “-” indicate the old line, the “+” indicates the new line).


    --- xp\_publish.php.141 Sun Jul 24 22:27:42 2005
    +++ xp\_publish.php Sun Jul 24 22:32:52 2005
    @@ -676,7 +676,7 @@
    $category = FIRST\_USER\_CAT + USER\_ID;
    }

    - $query = "INSERT INTO {$CONFIG['TABLE\_ALBUMS']} (category, title, uploads, pos) VALUES ('$category', '" . addslashes($\_POST['new\_alb\_name']) . "', 'NO', '0')";
    + $query = "INSERT INTO {$CONFIG['TABLE\_ALBUMS']} (category, title, uploads, pos, description) VALUES ('$category', '" . addslashes($\_POST['new\_alb\_name']) . "', 'NO', '0', '" . addslashes($\_POST['new\_alb\_description']) . "')";
    cpg\_db\_query($query);

    $params = array('{NEW\_ALB\_CREATED}' => sprintf($lang\_xp\_publish\_php['new\_alb\_created'], $\_POST['new\_alb\_name']),
    @@ -702,9 +702,9 @@
    if (!USER\_ID || !USER\_CAN\_UPLOAD\_PICTURES) simple\_die(ERROR, $lang\_errors['perm\_denied'], \_\_FILE\_\_, \_\_LINE\_\_);

    $album = (int)$\_GET['album'];
    - $title = '';
    - $caption = '';
    - $keywords = '';
    + $title = addslashes($\_POST['title']);
    + $caption = addslashes($\_POST['caption']);
    + $keywords = addslashes($\_POST['keywords']);
    $user1 = '';
    $user2 = '';
    $user3 = '';

  77. Please note: This page was getting a little too long, so I will turn off comments. For feedback, please use the forums.