dealing w/ images

[jairoh_]

---

mga boss unsai mas maau na practice in dealing w/ images? i.store sa database ang image or name/path ra sa image?
kai mas pas2x man ug load kung sa path ra dba? pero ang nakabati kai maka.view ang user sa folder sa uploaded images, unlike kung sa database jud gi.store. any idea there? please post the advantages and the disadavantages. tnx. i'm still learning.

[kamahak]

The latter. Assuming na apache server imo gamit, setup lng ug .htaccess sa folder na dli nimo ganahan ipa view.

.htaccess:

order allow deny
deny from all

Of course, daghan pa kaau kag mabuhat pero sa imoha lng na case, ok nani siya.

[arthexcalibur]

for me, mas nice ang path ra. . imong database mura rag papel ang kagaanon. . .

[cutterpillow20]

up ko ani kay kani pud ako gus2 mahibal.an karon sa video ug sa images..

[ondoy]

better kung dli db pra dli bugat...kung dka mg gamit ug framework need nmo ng ky kamahak

[jairoh_]

better kung dli db pra dli bugat...kung dka mg gamit ug framework need nmo ng ky kamahak

i use CI boss hehehe.

[ChaosOrb]

ibutang lang sa path ang images. Sakto ila suggestion, nakasuway sad ko ana nga problem before, but later na realize nako ang advantage. Kung sa database nmo ibutang versus path/folder...just think if you're dealing with millions and millions of records....dili lalim!

ang gi.suggest ni kamahak, okay man pud through apache, straightforward walay daghan additional settings needed, but then dili na viewable ang images directory, tight and secure.

If you want nga viewable ra ang mga images, by providing the correct path/file name....then lahi sad nga approach ang gamiton.

in your images folder, add index.php.

<?php
//Silence is Golden!  ^_^

[jairoh_]

ibutang lang sa path ang images. Sakto ila suggestion, nakasuway sad ko ana nga problem before, but later na realize nako ang advantage. Kung sa database nmo ibutang versus path/folder...just think if you're dealing with millions and millions of records....dili lalim!

ang gi.suggest ni kamahak, okay man pud through apache, straightforward walay daghan additional settings needed, but then dili na viewable ang images directory, tight and secure.

If you want nga viewable ra ang mga images, by providing the correct path/file name....then lahi sad nga approach ang gamiton.

in your images folder, add index.php.

<?php
//Silence is Golden!  ^_^

what about if akong i.delete ang image? how would i able to do it? or example a change the user's avatar, does that mean mag.overwrite rato ang image.name/path sa akong database then ang old image naa ra sa folder? in that case mapuno ang folder ug mga images na wa gamita ana in time. nag.learn pako ani. so please tell me how to do it in a good way


and i think istorya.net is not using path, db ang gamit sa ila avatar.

[ChaosOrb]

then delete the file that is physically associated with the record, you have the path of the image, locate it, then delete physically before adding a new one.

ang technique para gaan imong image directory is to optimize the image into allowable size. you have to redraw/recreate the image somehow para gaan nlng inig load sa avatar. *hint: PHP GD2 Library.

[jairoh_]

The latter. Assuming na apache server imo gamit, setup lng ug .htaccess sa folder na dli nimo ganahan ipa view.


.htaccess:

order allow deny
deny from all

Of course, daghan pa kaau kag mabuhat pero sa imoha lng na case, ok nani siya.

boss if akong butangan ug
order allow deny
deny from all, di naman ma.view ang image gamit iya path, sa src ba

then delete the file that is physically associated with the record, you have the path of the image, locate it, then delete physically before adding a new one.

ang technique para gaan imong image directory is to optimize the image into allowable size. you have to redraw/recreate the image somehow para gaan nlng inig load sa avatar. *hint: PHP GD2 Library.

yes mao na ako gbuhat. i thought nga naai saun na way sa pagdelete, manual pa diay japon.