Can't get this working

You’re using WordPress 4.1?

yes.

So is this down for the count at the moment?
In my testing of various customizer plugins I noticed many conflicts between one and another, but, regardless, I haven’t been able to get this one working.

Cheers
Mike

Two more questions: do you a Loop with posts in it being listed in the preview (e.g. a posts page or a single template)? Do you have a JavaScript error in the console?

I did both – loop and single post. And I tried from Edit post -> Preview & Customize

From single post -> Customize (via admin bar) no Javascript error.
Nor from the loop page.

Did I forget a configuration step?

BTW I am using Mac – Safari 7.0.3 but along the way I did a bit of testing in Chrome with the same results.

Cheers
Mike

Thanks, Mike. When I get a chance I’ll investigate with the information you’ve provided here, probably sometime over the next 48 hours. There shouldn’t be any additional configuration step you need to do.

Thanks.

BTW I am very interested in using the customiser for configuring individual posts that would then be downloaded as standalone HTML5 docs – replacement for PDF and EPUB.

The file contains everything – CSS, JS, fonts, media compiled on the fly and configured per post – hence the interest in the customizer and this plugin.

I built a prototype with some samples. I have even more samples of complex docs using fullpage.js.

https://5doc.org and samples at https://samples.5doc.org

Should I follow along on Slack?

Cheers
Mike (@mac2net on Slack)

Humm, customize-posts is working for me with twentyfourteen.

Try putting this in your JS console:

wp.customize.previewer.bind( 'customize-posts', function ( data ) { console.info( 'customize-posts', data ) } )

Then try navigating around the site in the preview. On each page load, you should see an object written out to the console that has four properties:

• isPostPreview
• isSingular
• queriedPostId
• collection

The collection is the key one here. It is an array containing the necessary data to dynamically construct the settings and controls for editing the posts, and it is this array that is used when building out the list of posts in the dropdown.

Hi Weston

Thanks. i found the conflict – JetPack.
So while I apologise for wasting a bit of your time, hopefully since it is very widely used, this info is helpful.

I will play a bit with the plugin and make another post here ASAP.

Cheers
Mike

Thanks for the tip regarding Jetpack. However, I tried activating Jetpack and Customize Posts still worked as expected. Do you know which module specifically in Jetpack is causing the conflict? Do you have any specifics about what Jetpack is trying to do that causes the problem? Thanks.

Sorry, nevermind. I was on an old version of Jetpack. I updated to the latest and I’m seeing the same thing. Investigating…

I found the problem, but not really the reason for the problem. The problem is with how Customize Posts is registering scripts. When Jetpack was enabled, none of the Customize Posts scripts were persisting. PR for fix: https://github.com/xwp/wp-customize-posts/pull/26

Thanks.
I’m in the middle of troubleshooting a bunch of things with another eye on the news (I’m in Europe).

In my developer 5doc content site I use custom post types. The plugin seems not be conflicting but not showing any posts.

In class-wp-cusomize-posts.php line 95 I modified it to:

'type' => array('post','content'),

to add the contentcustom post type.
Do I need to make any other mods?

Before giving you the list of other plugins that conflict I will test the new version.

Cheers
Mike

Hi Weston

Now it seems to be working including my small patch to add another post type.

Some feedback:

1. There is no linkage between the Previewed post and the Customizer panel. So when previewing a post, the Customizer fields don’t change to reflect that post and selecting a post in the Customizer doesn’t change the Preview. I can sync them manually.
2. The plugin uses the traditional Custom Fields UI and shows a field’s ID, instead of Name (which I guess is optional in WordPress). But since the Customizer is for users, it might be better to use Name if there is one and to use the Metabox UI rather than the Custom Fields UI.
3. I’m using Posts2Posts which are not displaying at all. I see this data is stored in a separate table with a different structure. I suggest (easier said than done) some kind of API to add 3rd party metaboxes to deal with this and other (many I’m sure) cases like this.
4. Are edits of fields in the Customizer supposed to work? That doesn’t seem to be happening.

I will give you more feedback as other things come to my attention.

Cheers
Mike

Hi Weston

I just checked another site and editing/saving meta data is working.
The biggest difference between sites is the one that’s not working is part of a multisite.
I will have to do some playing to see if in fact it’s a conflict with another plugin.

Cheers
Mike