Title: array for post type parameter do not work
Last modified: August 21, 2016

---

# array for post type parameter do not work

 *  [grosbouff](https://wordpress.org/support/users/grosbouff/)
 * (@grosbouff)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/array-for-post-type-parameter-do-not-work/)
 * When registering a new MultiPostThumbnails with an array as post_type parameter,
   it is broken… Only works with a string 🙁
    Do you know that bug ?
 * [http://wordpress.org/extend/plugins/multiple-post-thumbnails/](http://wordpress.org/extend/plugins/multiple-post-thumbnails/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Chris Scott](https://wordpress.org/support/users/chrisscott/)
 * (@chrisscott)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/array-for-post-type-parameter-do-not-work/#post-3856914)
 * This isn’t a bug per-se since it expects a string and nothing in the docs says
   it can be and array. Because of the way the thumbnail is registered, accepting
   an array isn’t a straightforward change to implement.

Viewing 1 replies (of 1 total)

The topic ‘array for post type parameter do not work’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/multiple-post-thumbnails_d94965.svg)
 * [Multiple Post Thumbnails](https://wordpress.org/plugins/multiple-post-thumbnails/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/multiple-post-thumbnails/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/multiple-post-thumbnails/)
 * [Active Topics](https://wordpress.org/support/plugin/multiple-post-thumbnails/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/multiple-post-thumbnails/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/multiple-post-thumbnails/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Chris Scott](https://wordpress.org/support/users/chrisscott/)
 * Last activity: [12 years, 11 months ago](https://wordpress.org/support/topic/array-for-post-type-parameter-do-not-work/#post-3856914)
 * Status: not resolved