WebExport 1.0 General

Post general comments on WebExport 1.0 (all versions) including feature requests, etc.

38 Responses to “WebExport 1.0 General”

  1. KC Says:

    "Bill of materials for this package not found"! — the thing wouldn't unpack/unstuff correctly, but there was a folder of stuff all the same for me to open. Clicking on the package gave me the sad error message about bill of materials.

  2. ira Says:

    same thing happened to me. i am running osX and after downloading the program and unzipping it, i try to run the webexport.pkg and it gives me an error, claiming the "Open Failed".

  3. Daniel Staudigel Says:

    Not sure what to say, this doesn't happen to me. Make sure that the download wasn't corrupted, and that you're on a modern machine. Re-download and try again, or post some more specifics about your computer so I can more easily debug the situation.

  4. Susan Says:

    I downloaded Webexport1.0r134 for My iMac, OSX Version 10.4.8. I was able to install the package file and see webexport in the export section of iphoto. However, the only template that seemed to install correctly was the multiple galleries. The other templates appear blank, and no information shows for the templates in the export window. When I attempt to use any of the templates, all I get is a bunch of image files on my desktop. I have attempted to download and install a number of time, but there's no difference. Any ideas what is wrong?

    Thank you,

    Susan

  5. Daniel Staudigel Says:

    A few things that would be helpful for debugging:

    What files/folders are in the (~)/Library/Application Support/WebExport/ folder? What templates show up in the drop down? What templates actually work when you try to export them? What templates have info in the info panel (this is not required to make a template work, though, it is just curtesy information provided by the maker of the plugin, but has nothing to do with the actual export).

    How are you installing the templates? By double-clicking them or by dragging them to the aforementioned folder?

  6. Scott Says:

    Daniel, I'm really glad I ran across WebExport as it's exactly what I have been looking for, nice job. I'm currently working on a template for BananAlbum and ran into one issue perhaps you can help with. I'm using the width() and height() calls to get that metadata, however BananAlbum appears to need an integer rather than the float that is returned. Is there a way to cast what is returned rather than modifying the return value in exporter.py? I'd be happy to share the template once I'm done (assuming the BananAlbum creator doesn't mind).

    Thanks, Scott

  7. Daniel Staudigel Says:

    Absolutely! Python, the scripting language on which WebExport is based, has an easy tool to do this. All you have to do is type int(width()), and it is turned into an integer. You may have to stick both in a str(int(width())) if you get an error, but that is only in advanced use cases.

    I'd love to see how your template turns out!

  8. Scott Says:

    Daniel, that didn't quite get it…
    EVAL: An error "exceptions.ValueError" ("invalid literal for int(): 450.0001125") has occurred in "int(height(int(attribute('h')),int(attribute('w'))))" for image (0 of 2) gallery (0 of 1)

    It works Ok if I do the cast on the return value from height()/width() in exporter.py, but not in a template file on the unicode value that's returned. I'd prefer not to have to modify exporter.py (much better to use your stuff out of the box if possible!). The objective here is to get the dimensions of the generated image to fill a path type of element. BTW, is it possible to output other photo attributes like shutter speed, fstop, etc.?

    Thanks, Scott

  9. Daniel Staudigel Says:

    Weird… could you email me your template? I wouldn't cast the input attribute('h') and w, just cast the output: int(height(attribute('h'),attribute('w'))), not with so many casts. You shouldn't have to modify exporter.py to get this simple functionality.

    There is no support for EXIF stuff (fstop, shutter, etc.) now, though I've been looking into ways of adding it. If there's interest, I'm developing a version of WebExport for Aperture, which will have these capabilities.

  10. Daniel Staudigel Says:

    Damn, maybe Python isn't as nice as I thought. To convert a string of a floating point number into an integer, you first have to turn it into an float and then into an integer. Don't ask em why, but:

    int("400.0034") generates an error

    but

    int(float("400.0034")) does not.

    SO. The line in question should look like:

    int(float(width(int(attribute('imgsize')) ,int(attribute('imgsize' )))))

    And that's that… I should figure out a way to make this excessive casing less so, and also replace attribute with attr().

    Thanks for the heads up! Ah, programming.

  11. sd Says:

    Hi,

    If I am using a "image(W,H)" tag, I thought that H and W would be MAX dimensions of the result image. But if the original iPhoto image is smaller, WebExport enlarge it… Is it a bug or a feature?
    So how can I export a photo at original unaltered size?

  12. Daniel Staudigel Says:

    Interesting… I never really thought of using this for exporting low-res photos and images, so it's not really possible to do. I'll see what I can do about incorporating this into the next iteration. There might be a way to do it with some clever python hacking, so if you know Py, you might have some luck checking through the attributes file.

  13. ElGanzoLoco Says:

    I'm currently using JAlbum to do my galleries, but it is somewhat cumbersome as it's not integrated in any way with iPhoto. I'd much rather use WebExport, but I really need EXIF data output (the whole shebang: camera make, ISO, shutter speed and aperture, flash fired, etc).

    Very good work anyways!! Congrats also to the developers of some templates (Postcardviewer is amazing!)

  14. Daniel Staudigel Says:

    Well, depending on how down-and-dirty you are willing to get, you can get EXIF to work with WebExport. With WebExport you have access to the original file, and Python. So, if you have a shell script/utility that can extract EXIF data, you could write a little bit of glue code that allows you to import that. The reason I haven't built this into WE yet is that not many users need it and EXIF data can be non-standard. I am working this into WebExport Pro, which will work with Aperture.

  15. ElGanzoLoco Says:

    Unfortunately I have absolutely no Python skills whatsoever! Maybe my mad coder friend can work it out, but I doubt he has the time for that :)

    Why not make WebExport Pro compatible with iPhoto as well as Aperture? I'd be willing to pay some money for it, but I won't be buying Aperture (my Mac wouldn't run it anyways…). I think many advanced amateurs or semi-professional photographers are in the same case…

    Thanks for your answers anyway, and keep up the great work!

  16. cayco Says:

    Hi! Nice work!

    I discovered an error. I guess it has something to do with unicode characters in photos filenames. I'll try to hunt it down although I am not very experienced python programmer.

    EVAL: An error "exceptions.UnicodeEncodeError" ("'ascii' codec can't encode character u'\u0307' in position 33: ordinal not in range(128)") has occurred in "image(int(attribute('maxwidth')),int(attribute('maxheight')),'images/')" for image (0 of 12) gallery (0 of 1)
    Traceback (most recent call last):
    File "/Applications/iPhoto.app/Contents/PlugIns/WebExport.iPhotoExporter/Contents/Resources/exporter.py", line 284, in processEval

    s = eval(ev)
    File "", line 0, in ?
    File "/Applications/iPhoto.app/Contents/PlugIns/WebExport.iPhotoExporter/Contents/Resources/exporter.py", line 207, in image
    print "319010816 (null) -1340410392 22 ãu∂Vã;Ñìg ˇtL=ˇ" i,style,maxw,maxh,destination)
    UnicodeEncodeError: 'ascii' codec can't encode character u'\u0307' in position 33: ordinal not in range(128)

  17. cayco Says:

    Fixed ;-)

    The solution was to encode Unicode string to plain ASCII with 'ignore' parameter which gets rid of some wrong Unicode characters. Here's diff:

    143c143
    return metadata('filename',i).replace(' ','_')+"."+property('extension')
    206c206
    destination = location+metadata('filename',i).replace(' ','_')+".jpg";
    391c391
    file = metadata('filename').replace(' ','_');

  18. cayco Says:

    I'm sory, I need to post again - wordpress changed diff format. Here's pastebin link: http://pastebin.ca/553200

  19. Daniel Staudigel Says:

    So, this pastebinned code is a patch for the current exporter script? I'll see if I can get this out once finals are over. Thanks for the heads-up. I wonder why it doesn't like UTF-8/Unicode, I was pretty sure that the MacOSX file system was OK with unicode file names, but whatever. The only concern is when it's all Unicode files, then it's possible to get overwritten names.

  20. Zippyaus Says:

    Hi Daniel

    Thanks for the plugin .. it is awesome … I have a question … I have been using iPhoto export (www.hagus.net) … I am using it with your SimpleView template.

    Is there a way to get the Comments as the photo tag instead of the Photo name?

    Thanks

    ZP

  21. Daniel Staudigel Says:

    Sure! Right-click the template, edit the XML file, and change < ?title?> to < ?comment?>, or something like < ?title?>: < ?comment?> if you wanted a combination (all in the
    section).

  22. Donald Says:

    OK, so new to web site building, but very keen to try Webexport. Trouble is it won't install. I'm using a power book, OSX 10.4.10. I've tried twice now. Downloaded the "current version", unpacked, gone through all the motions and after it tells me it is installed I can't find it anywhere. It is not listed in "application Support", or in iweb. Any ideas what I'm doing wrong. Thanks for your time!

  23. Daniel Staudigel Says:

    It's an iPhoto plugin, so you just go to "Export", the same as for "Web" or "QuickTime" or whatever, and you export photos directly out of iPhoto.

  24. Lucas Says:

    The plugin does not work with iPhoto 7. (iLife '08) Please please please can you make it work on iPhoto 7?
    Thank you for your time, I am a big fan of your product.

  25. Brecht Says:

    I had webexport installed in iPhoto6, but now I upgraded to iPhoto7 and the export function in iPhoto doesn't work anymore, If I choose File - Export, nothing happens…
    Is this a WebExport related bug?

    please help :-)

  26. Zippyaus Says:

    You said to change the template "Sure! Right-click the template, edit the XML file, and change to , or something like : if you wanted a combination (all in the section)."

    I don't understand? .. I went to the package contents and opened the gallery.xml file … but couldn't understand what I needed to change.

    Thanks

    ZP

  27. Dave Says:

    Sadly it looks like iPhoto 7 has issues with third-party plugins. For a couple others that I have installed, if you double click on their tab in the Export dialog, they will activate. However, if WebExport is installed, the Export window will not even appear. Of all the plugins I have this is the one that I love the most and hope it can be fixed soon.

    Thanks!!

  28. Daniel Staudigel Says:

    Yes. It will not work with iPhoto 7 yet. Unfortunately, I am in Germany right now, and I can't get my grubby paws on a copy until I'm back in the states (a few weeks). Once I do have it, I should be able to figure out how to make it work with the new version quickly, unless apple has gone and screwed me over. We'll see. If someone knows of a way to get it faster than going by my (now non-)local Apple store, drop me a line.

    In the meantime… remove it from /Applications/iPhoto.app/Contents/PlugIns/.

    Sorry for the inconvenience, I really can't wait to get my hands on iPhoto 7, I have a lot of cool stuff planned.

  29. Daniel Staudigel Says:

    ZP: Sorry, WordPress ate my post. Change (in brackets) title, to (also in brackets), comment.

    Hope that helps.

  30. Daniel Staudigel Says:

    Yahoo! Got ahold of '08, and the new version is on the main site. Sweet.

  31. Zippyaus Says:

    Hi Daniel

    I got the caption working with the title and the comment. It is excellent and does what I want. I have been playing with this all weekend, but cant seem to create a link to the file. I put all the full versions of the images in a folder called HiRes, this enables people to download the HiRes version of the pics to print. I can't get the URL to work. Below is the code I have come up with.
    () .jpg"/>

    I would greatly appreciate any help with this as it will complete my solution.

    Thanks again

    ZP

  32. Zippyaus Says:

    WordPress ate my post too … the code I had was wrong anyway. I have got this working as I want it now. If anyone is interested you can add a URL with the code below, should have thought of it earlier, but have a 6 week old child and not getting sleep :)

    " () <a href="HiRes/.jpg">Click here for HiRes</b>"

  33. Zippyaus Says:

    OK… you cant paste code in here .. even in quotes, but basically all I did was use the standard html HREF and replaced the greater than and less than symbols with & gt ; (with no spaces) so ampersand gt semi-colon for > and ampersand lt semi-colon for

  34. Zippyaus Says:

    OK .. so one more element .. what about the photo date .. can that be called in the xml? What is the attribute name? I have tried Date and photodate.

    Cheers

    ZP

  35. Zippyaus Says:

    In the outputted xml it says " date="""

    Anyway I will keep trying or add the dates in manually.

    Thanks again

  36. Zippyaus Says:

    it doesn't like date(index) … if I use date I get

    Thanks for any input .. I will keep trying

    ZP

  37. oliver E. Says:

    hi! i just found that nice plugin fir iphoto! i works great! is there any chance i can put that on my homepage with iweb und my dotmac account?
    how can i upload it via iweb?

    Thank you so far!

    Olli

  38. Daniel Staudigel Says:

    I have tried to figure out a way to get WE to work with iWeb… but the best I could do is add a link in iWeb to your exported gallery, and then upload the gallery manually. This is not the greatest solution, because it's neither fast nor intuitive. If apple made a better plugin architecture for iWeb, this would be trivial. Oh well.

Leave a Reply