Oh but it seems to have speeded it up with out that
so if i work out how to do above it will be even faster?:D

Hello Vitaly,

in the AdminCP Options, at "Path to attachments", need to insert the patch of the thumb right?

But it is the same of the attachments? If not, How can I find the correct path? I remember to have setup the attachments stored on disk, but I don't rememeber a specific path where are store my thumb.

All my attachments are in : "forum/attachments"

Thank you

Try /forum/attachments or /attachments

It's easy to check:
- open page source
- check generated thumbnal paths
- if not correct - play with setting to fix difference.

Of cause, you should check, that thumbnails can be downloaded via www (that's mentioned in installetion steps).

Sorry to disappoint, but I have no apache. So, I can say WHAT should be done, but not HOW. Try to ask your admin or google this question :) . Don't forget to share result, if you have some.

Hmm have an odd issue. I have attachments on a subdomain along with all the url rewrites working. The attachment thumbnails show however when you click on the attachment image they do not load in the lightbox. Any advice?

I do run imagemagick of that has any effect.

Do those work:

- if you switch off lightbox
- if you switch off this mod

?

The other way to check is to install firebug addon for firefox, and check what happens in network tab when image fails to load.

Turns out I am getting 404 errors on the lightbox and if I load the attachment directly. If I disable this mod the attachments work fine and the thumbs still work.

So it seems something from this mod is breaking the attachments themselves.

Can you check with firebug, which URL failed for lightbox?

Played with it some more it turns out its the X-Accel-Redirect. Updated my NGINX just to make sure it wasnt a bug.


Failing URL is
http://immortal-guild.net/attachment...1&d=1271597314

This mod doesn't affect fullsize attachments, if you turn off "nginx acceleration" option.

If problem caused by this option, then absolute disk path can be wrong, or some rare nginx limitation for X-Accel-Redirect (see docs).