I have two paths defined:

At the top of the brilliant gallery config page (/admin/settings/brilliant_gallery) where it says
Path to an image cache folder, I put the full path to where I want my thumbs to cache:
/var/www/vhosts/mysite.com/httpdocs/sites/www.mysite.local/files/gallerytemp
(I copied my "site" folder from my local environment, hence the "www.mysite.local" as a folder name)

At the bottom of the same page where it says
Database or file system caching of images:
I picked "Use the temporary directory you have set in /admin/settings/file-system. Faster than database caching!"
This leads to a different folder, my general cache folder sites/www.mysite.local/temp.

My questions are:
1. It doesn't seem to work. There are no cache files (in either folder) after I open a gallery in thumbnail view. Any idea why?
2. Which of the two paths is it? I seem to be setting TWO paths as a cache folder? What's the difference?

(note: caching worked on my local test environment when I just used "E:\xampp\tmp" as my setting in both cases)

Comments

puppetmast0r’s picture

puppetmast0r commented

Not enough info?

Could anyone perhaps answer question 2 for me? What is the difference between the two folders I can select to cache?

sittard’s picture

sittard commented

Most likely it's a permissions problem on the server I would chmod/chown the folder. Double check the correct owner/web server has the correct write permissions.

Personally I'd like to see brilliant gallery storing the cached files as physical image files.

mgearr’s picture

mgearr commented

I agree, it would be fine if BG stored cached files on disk. Why doesn't it store them when the cache path is set - I have no idea

vacilando’s picture

vacilando commented
Version: 6.x-3.4 » 6.x-3.x-dev
Status: Active » Fixed

@Puppetmast0r,
1) Surely a question of permissions. PHP must have permissions to write to the cache directory.
2) I agree it looked confusing in te settings, but indeed only one path was used for file caching. Fixed in the latest dev (submitted today).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

LdyMox’s picture

LdyMox commented

Same problem here