Zenphoto
The simpler media website CMS
ZenphotoThe simpler media website CMS
Forum search only. You might also want to search on the main site's user guide.
Your support helps pay for this server, and helps development of zenphoto. Thank you!
Visit the donations page
Comments
Thanks.
Right now, the fields available are:
Location:
City:
State:
Country:
Credit:
Copyright:
I have no need for any of those. I would rather have fields of my own choosing. I don't know how to change those, or whether I should. I don't know if I can add others, or how.
It is technically possible to extend the "custom field" below via a plugin filters but nothing ready made exists for that.
I must be missing something important...
However, there are functions you can use to print this but you will have to insert this yourself.
This one is probably the easiest:
`printImageData($field, $label = '')`
So, in `image.php` insert something like this where you want it to appear:
`<?php printImageData('city', 'City: '); ?>`
Say you filled out New York in the "City" fied, this will output:
`City: New York`
a:1:{s:5:"en_US";s:19:"City: New York";}
You can use this instead:
`<?php echo "City: " . get_language_string(getImageData('city')); ?>`
This is similar for all fields, e.g.:
`<?php echo "Copyright: " . get_language_string(getImageData('copyright')); ?>`
…etcetera.
There are also object model methods who do it also correctly like
`echo $_zp_current_image->getLocation()`
In the meantime, thank you for the prompt and helpful responses.
Again, if you need full control of the display why don't you put the info right into the image description? Your visitors will not care which field the data comes from.
But, this is a database! In my mind, when objects share similar data they should have fields to contain that data. I have identified twelve items of interest for every one of my images.
I wonder how much I should pay for a modification to this software - one that would be open source for everyone to utilize.
There is a standard means for adding database fields. There is an example of this in the `userAddressFields` plugin. There is also another in the `customFieldExtender` example plugin. Unfortunately this is not included anywhere in the Zenphoto repositories, so you would have to install the ZenPhoto20 package to get it.
In all cases if the examples are followed the added fields WILL be included in the possible searchable fields. They default to not enabled just like the EXIF and IPTC fields from the image metadata.
Using existing database fields is a shortcut way to provide your own data, but it does have perils. Unless you disable the processing of image metadata that feeds these fields what you manually enter can be overwritten on metadata refreshes.
And, of course as you have noticed, the standard printing functions believe the know the "name" of this field and will show it.
If you still want to use these fields for your own purposes after reading the above, then to get your desired name you will have to provide your own printing function.
You ask how much it would cost to implement this. I would love to respond, but unfortunately the zenphoto team has seen fit to remove my details from the "pair support" page. Perhaps one of the team members who are left in the list has the knowledge and skill to quote you on this change. If not you can contact me at stephen [at sign] sbillard.org.
You have been removed from the paid support page because it was as you know always for team members only. You choose not to be one anymore. Also, pointing to the fork is not helpful.
As to the plugin you point to. Again, you have made a mistake. Perhaps you should research your answers more carefully so you do not mislead your users.
That plugin does not add any fields to the database at all. It is simply a means of storing data in the custom field of the database table. The whole reason for the new technique is that sharing the custom field is not parasitical as plugins tend to step on each other's data.
As to the paid support page--that is your call. But you should note that the page is really for your users to get features they need in zenpoto (or its fork on GitHub.) So right now you have only one option for someone who wants to customize the way zenphoto works--you. Given your propensity to mis-state the current features perhaps that is too limited a choice.
If you wished to have a say in how the project operates, and the ability to help and post information on the forums, then you should collaborate with us positively rather than dividing yourself and making fun of and deriding our statements. This isn't productive, and that's why it isn't helpful as Malte stated.
We welcome your help if it is positive and supportive. However, it is unwelcome if your posting continues to be derisive of our developers, or the statements they make about the software or how we support our users.
The information provided above is misleading at best. That is why I have posted the correct information. I did also react to acrylian's statement that pointing to the ZenPhoto20 fork is not helpful. I guess I disagree, since it does provide the example plugin for making these custom fields whereas the plugin acrylian links to does not.
Same thing for links that might help users get custom features they might wish. You can limit those to your team. No problem, but that does also limit the options of your users.
Now I just have to figure out whether I should delete all my zenphoto and run with zenphoto20, or just borrow the customFieldExtender page from 20, or stick with my blob of data in the description of each image with zenphoto.
I know I need to go zenphoto20; I'm just a little lazy about it all right now.
I do appreciate the help I have received here but I wish it had been a little more forthright.
Sorry again that you had to suffer from our controverses. Needless to say you are free to choose whatever tool you like and what fits your purpose right now best. So have fun with whatever project you choose to use.