Skip to content
This repository was archived by the owner on Dec 16, 2022. It is now read-only.

Conversation

@mehigh
Copy link
Member

@mehigh mehigh commented Apr 21, 2016

I encountered two warnings on a basic environment, which I fixed with some extra conditionals.

Warning: array_keys() expects parameter 1 to be array, null given in
/wp-content/plugins/customize-posts/php/class-w
p-customize-posts-preview.php on line 150

Warning: Invalid argument supplied for foreach() in
/wp-content/plugins/customize-posts/php/class-w
p-customize-posts-preview.php on line 156

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 2266b3c on bugfix/customize-post-setting-warnings into * on develop*.

mehigh added 3 commits April 21, 2016 10:31
Warning: array_keys() expects parameter 1 to be array, null given in php/class-wp-customize-posts-preview.php on line 150
Warning: Invalid argument supplied for foreach() in php/class-wp-customize-posts-preview.php on line 156
@westonruter westonruter force-pushed the bugfix/customize-post-setting-warnings branch from 2266b3c to e8e8990 Compare April 21, 2016 17:32
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling e8e8990 on bugfix/customize-post-setting-warnings into * on develop*.

@westonruter westonruter changed the title Bugfix/customize-post-setting warnings Fix handling the discovery of postmeta settings for posts that lack any postmeta Apr 21, 2016
@westonruter westonruter merged commit a1eb7eb into develop Apr 21, 2016
@westonruter westonruter deleted the bugfix/customize-post-setting-warnings branch April 21, 2016 17:41
@westonruter westonruter added this to the 0.5 milestone Apr 28, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants