|
xListSize | pixels number | optional | maximum width of the image in tracker items list ( automatically rescaled if the upload image is larger) | |
yListSize | pixels number | optional | maximum heigth of the image in tracker items list ( automatically rescaled if the upload image is higher) | |
xDetailsSize | pixels number | optional | maximum width of the image in item view (automatically rescaled if the upload image is larger) | |
yDetailsSize | pixels number | optional | maximum width of the image in item view (automatically rescaled if the upload image is higher) | |
uploadLimitScale | pixel number | optional | maximum size of a picture. If the image is larger or higher, the uploaded image will be rescaled automatically- the initial image will not be saved | |
shadowbox | string or number | optional | allows a shadowbox when clicking on the img: special values: item, individual(see below) | tw>=3.0 |
For instance this option field
100,100,400,400,,item
will limit the picture size to 100 in list mode, to 400 in item view, and will allow a shadowbox popup
The shadowbox option allows you if the feature is activated Shadowbox to provide a popup on the image.
{$f_1} <div style="display:none"> {$f_2} {$f_3}</div>
where f_1, f_2, f_3 are 3 images fields with type shadowbox=item
Administration
The images are stored in the sub directory img/trackers. The filenames are encoded at the upload.
Note for IIS users
Tiki stores images without any extension, Apache handles this fine, but IIS uses the file extension to determine which handler it should use for the filetype. Extra configuration to make IIS interpret these extensionless files is needed.
Solution
On the /img/trackers directory add a mimetype handler for "*" (on newest IIS (7.5) use "." instead) and set it to application/octet-stream this way IIS will look on the content type instead of the file extension.