Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

No Thumbnails

BenBen
edited August 2005 in Vanilla 1.0 Help
In my installation of FileBrowser that came with Vanilla, I seem unable to get the generated thumbnail images. I just get "preview unavaliable".

Any idea why?

Comments

  • are you sure the thumbnails have been created?
  • BenBen
    edited July 2005
    um..no? how do i do that?

    edit: ah found the thumbnailer file, i feel stupid...
  • lol RTFM!
  • MarkMark Vanilla Staff
    hehehe - Did you not read the readme.html file at all? I'm asking because I might make it more prominent about the thumbnailer if it's not obvious to people.
  • BenBen
    edited July 2005
    nope i didn't read it, i only read enough to check the install instructions
    ..actually, i can't seem to find a readme for Filebrowser...
  • MarkMark Vanilla Staff
    It came with the last release: readme.html
  • lechlech Chicagoland
    I think the thumbnailer will also float or sink depending upon weather you have gdlib functional on your php installation as well. The indexer works, I just can't thumbnail based on the fact that there's no gdlib on the server.
  • when you use the filebrowser that comes with Vanilla, in the vanilla/images/ folder, there doesn't seem to be a Readme for Filebrowser; only the Vanilla readme.
  • MarkMark Vanilla Staff
    Oooo. Ben. good point. Want to add that to the bug list?
  • Just curious, why even include the filebrowser in Vanilla's package? It's not like any other user except anybody with FTP access can use it functionally...
  • Its just so if people browse /images/ its friendly, no? Its not like it takes up a whole load of space. Mark - consider it done.
  • I'm aware that it's nice and friendly yep. Woo hoo on that score.

    But on the whole it bares no functionality to Vanilla itself, so I'm curious as to why it's packaged with it, as they're two separate products. If they were intertwined and users were able to upload then fair play, but as it stands it just seems like it's been thrown in just for the extra exposure (no offense mark).
  • I think in this case its more of an index than a filebrowser. Would you rather the /images/ directory was just blocked off completely or left to apache indexing treatment?
  • It's simple enough to shove a blank index file in there, so there's no need for one to speculate on apache would treat each individual case.
  • lechlech Chicagoland

    Vanilla Full Bodied™ - WIth the FileBrowser

    Vanilla Lite™ - Without the FileBrowser

  • I know filebrowser can be got seperately, but why complain that you get a filebrowser free when you install vanilla? Now you have it there in images/ are you really bothered enough to remove it?
    It's some nice exposure for what is a very simple and nifty app.
  • MarkMark Vanilla Staff
    Just be glad I'm not bundling Vanilla with the Filebrowser :P
  • lechlech Chicagoland
    hehe, in the prereleases you did!
  • lech, what he means is that when you get the filebrowser you dont also get vanilla, wheras this isnt true in the reverse. I'm pretty sure he's never bundled vanilla with filebrowser downloads in prereleases of either.
This discussion has been closed.