Log in | Register | Lost password

Bottom
A couple of suggestions:
  • Posted: 02.05.2003, 10:10
     
    Converted
    rank:
    12
    registered:
     March 2009
    Status:
    offline
    last visit:
    Posts:
    0

    1)
    Anyone on the shared server can potentially mess with your world-writable files (or files writeable by webserver). As an additional precaution I'd suggest to calculate MD5 checksums for uploaded media, and having a "FileLock" feature wich will chmod to -w after uploading...

    2)
    When in module admin I change image storage method from DB to File , I'm unable to see pictures stored in the DB. And vice versa. Why not to have a field with info on where the image located (db/file/remote)?

    3)
    A different table for image descriptions will allow multilanguage descriprions.

    Just my 10 minutes :)


  • Posted: 03.05.2003, 19:36
     
    Converted
    rank:
    12
    registered:
     March 2009
    Status:
    offline
    last visit:
    Posts:
    0
    Thanx for your suggestions:

    1) Setting the images "-w" (writable by owner only) can be a problem if you need to do some manual file administration and don't have admin access on the server. The problem is that the files are owned by the webserver on some configurations, and so you can't get to them by your self. This could of course be an admin setting.

    Having an MD5 could identify problems - but not stop them. Besides I wouldn't know when to check it to avoid performance overhead (you could of course do it every random 100 or so time).

    2) Setting a DB/file flag would work. I'll put it on the list, but it will have a low priority.

    3) You will have to elaborate a bit on the language idea. Would you make it possible to have multiple descriptions for the same image?
  • Posted: 03.05.2003, 22:34
     
    Converted
    rank:
    12
    registered:
     March 2009
    Status:
    offline
    last visit:
    Posts:
    0

    Quote

    Thanx for your suggestions:

    Having an MD5 could identify problems - but not stop them. Besides I wouldn't know when to check it to avoid performance overhead (you could of course do it every random 100 or so time).



    Manually OR via Cron job (available in CPanel, any hosting provider has it). MD5 consumes resourses.

    Quote



    3) You will have to elaborate a bit on the language idea. Would you make it possible to have multiple descriptions for the same image?


    A table could look like these:
    [php]
    image_id INTEGER
    lang_code VARCHAR(30)
    short_desc VARCHAR(250)
    long_desc text.
    [/php]
    Indexed by image_id+lang_code.

    image_id is not unique.

    for instance,

    [php]
    SELECT short_desc,long_desc WHERE image_id=1 AND lang_code="russian"
    [/php]

    and

    [php]
    SELECT short_desc,long_desc WHERE image_id=1 AND lang_code="deutch"
    [/php]

    will produce different results.




  • Posted: 07.05.2003, 07:50
     
    Converted
    rank:
    12
    registered:
     March 2009
    Status:
    offline
    last visit:
    Posts:
    0
    I get the idea. But what about user interface? A page with N title/descr. entries (more or less like the upload page) for each image - and a "new" button for adding yet another description? I guess that should be okay.

Template courtesy of Designs By Darren.