Piwigo.org

flop25 · 2012-06-27 16:17:37

I didn't code that part but normally the script check if the file exists, and if not generate : so you should be able to generate locally in _data/i/...-suffix.ext and upload it. You might have not used the correct suffix, or path

deserteagle · 2012-06-27 16:36:49

I'm sure the file name and path are correctly, I tried 3 times.

I copy my thumbnail in the cache folder and keep watch it, then, I click the related album, I saw the size of thumbnail files in the cache folder changed one by one, them all thumbnail of that album show up.

Yes, it generated thumbnail again even there were.

flop25 · 2012-06-27 16:45:13

ok
I'm looking at the code and i see only one thing :
if ($mtime===false or $mtime < $params->last_mod_time)
{
$is_cached = false;
I notify the developer of that part

deserteagle · 2012-06-28 12:56:20

so, Is there a way to pre generate multisize cache photos when upload by ftp?

I use ftp because I'd like to keep the structure of album.

deserteagle · 2012-07-02 05:17:47

I figured out it.

if you pre generate the thumbnail or othersize (for example websize) in advance and upload to _data\i\galleries, you should make sure those files have a newer date than the original image it self, otherwise piwigo will regenerate it again.

oliverfr · 2013-08-09 23:48:24

Hello,

I'm sorry to bring back this old thread, but I needed a confirmation, I wouldn't want to screw up badly.

So, to make room, it is safe to
- delete /_data/
- keep /upload/

This is it ?

Code:

du -h --block-size=MiB --max-depth=1 | sort -n
1MiB    ./doc
1MiB    ./galleries
1MiB    ./install
1MiB    ./local
1MiB    ./template-extension
1MiB    ./tools
2MiB    ./include
3MiB    ./admin
5MiB    ./themes
10MiB   ./language
14MiB   ./plugins
10279MiB        ./_data
11015MiB        ./upload

--> With 10 and 11 GB per folder, I'd better not screw up, I don't even want to have to re-upload everything ^^

That would mean that /_data/ contains stuff like resized images that will be, if needed, re-generated on the fly when a visitor wants them ?
While /upload/ keeps the originals for when they're needed again ?

Thank you VERY MUCH if you can help me with that simple confirmation, that it's/ _data/ that can be deleted while /upload/ must be preserved :)

mistic100 · 2013-08-09 23:54:57

why would you want to delete it ? it will be re-generated very quicly causing useless CPU usage

(but yes you can delete _data)

oliverfr · 2013-08-10 00:00:11

The reason is that, with my server, my web host provides an additional backup server, on which my disk quota doesn't exceed 100 GB. So, that's becoming a considerable difference, all in all. If my backup can be 10 GB smaller, that's a literal relief. And I've got enough CPU to handle that :)

(and thank you very much, I mean it, for the /_data/ confirmation ! :) )

Piwigo.org

Announcement

#16 2012-06-27 16:17:37

Re: "local" directory versus "_data" directory

#17 2012-06-27 16:36:49

Re: "local" directory versus "_data" directory

#18 2012-06-27 16:45:13

Re: "local" directory versus "_data" directory

#19 2012-06-28 12:56:20

Re: "local" directory versus "_data" directory

#20 2012-07-02 05:17:47

Re: "local" directory versus "_data" directory

#21 2013-08-09 23:48:24

Re: "local" directory versus "_data" directory

Code:

#22 2013-08-09 23:54:57

Re: "local" directory versus "_data" directory

#23 2013-08-10 00:00:11

Re: "local" directory versus "_data" directory

Board footer