[theme-reviewers] Themes With Customizable Logos *and Featured Images*

Edward Caissie edward.caissie at gmail.com
Thu Sep 2 18:54:53 UTC 2010


The idea looks feasible for using Post-Thumbnail but I can also see it as
having the potential to have two different images representative of the post
whereas the custom fields would support the second image. The author is
suggesting the theme is testing for the custom field <featuredimage -
image_URL> key-pair ... which may conflict with testing for an existing
Featured Image provided via post_thumbnail.

Technically speaking both could be used on a post and both images could be
different ... or the same. That would be at the end-user's discretion.


Cais.

PS: I did not look at the code to see if post_thumbnial is being implemented
already. EAC


On Thu, Sep 2, 2010 at 12:21 PM, Chip Bennett <chip at chipbennett.net> wrote:

> The Theme developer is also using custom fields for "Featured Images",
> rather than supporting Post Thumbnails.
>
> Here are the instructions:
>
>  *How do I add the featured thumbnails to the sidebar gallery?*
> You can select 8 posts to be featured. For each post,
>
>    1. Add the “Featured” category.
>    2. Add a custom field with
>    Name = featuredimage
>    Value = image url e.g http://yourdomain.com/image.jpg (recommended:
>    75px by 75px)
>
>
> Any reason this shouldn't be done using core Post Thumbnails feature?
>
> Chip
>
> On Thu, Sep 2, 2010 at 11:07 AM, Edward Caissie <edward.caissie at gmail.com>wrote:
>
>> Making it a strongly recommended suggestion and providing the code is
>> about all you can do ... but as its not a "specific" requirement, but one
>> inferred from other criteria it is still at the authors discretion to use.
>>
>> I would also suggest including your points in this thread with the
>> comments to explain why what you are suggesting would be much better for the
>> author and the theme end-users.
>>
>>
>> Cais.
>>
>>  On Thu, Sep 2, 2010 at 12:02 PM, Chip Bennett <chip at chipbennett.net>wrote:
>>
>>>  On Thu, Sep 2, 2010 at 10:52 AM, Ryan Hellyer <ryan at pixopoint.com>wrote:
>>>
>>>> >> In this particular Theme, the documentation basically says, "A
>>>> logo.psd
>>>> >> and independence.ttf is included in the psd folder. Edit the psd
>>>> file, save
>>>> >> as logo.gif and upload to the images folder".
>>>>
>>>> >> At a minimum, it's a recommend with respect to Custom Image Header
>>>> >> functionality. I'm leaning toward require.
>>>>
>>>> Using a custom header like that then adds a "custom header" option in
>>>> the admin panel, which the theme developer likely did not intend. So
>>>> it should not be a requirement IMO.
>>>>
>>>> Ryan,
>>>
>>>
>>> It's a case-by-case consideration.
>>>
>>> Take a look at the Theme in question: http://themereview.chipbennett.net
>>>
>>> That "Food Recipe" is the header logo. The Theme gives instructions for
>>> how to change it. Thus, it would seem that the developer intends for it to
>>> be customizable.
>>>
>>> So, I'm not so much concerned about whether or not the Theme developer
>>> "intended" for a "Custom Header" menu item to display in the users' back
>>> end, as I am concerned with whether or not the Theme developer intended for
>>> the header logo to be customizable.
>>>
>>> Again, these are the instructions he gives:
>>>
>>> A logo.psd and independence.ttf is included in the psd folder. Edit the
>>> psd file, save as logo.gif and upload to the images folder.
>>>
>>>
>>> That implies to me that the logo is intended to be customizable. The core
>>> functionality vastly improves the user experience with respect to uploading
>>> customized logos.
>>>
>>> All that it would take to implement the core feature would be:
>>>
>>> 1) include add_custom_image_header()
>>> 2) define the custom header image dimensions
>>> 3) define the default image
>>>
>>> Easy peasy. In fact, I'm going to put the code into a comment on the
>>> ticket, to show how easy it would be to implement.
>>>
>>> In the end, I don't see how this is all that much different from
>>> requiring wp_nav_menu() when a Theme is using wp_list_pages() as a
>>> navigation menu.
>>>
>>> Chip
>>>
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>
>>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20100902/d8fcb203/attachment-0001.htm>


More information about the theme-reviewers mailing list