K. Adam White

Hey @danw_wp! If you just use regular posts, nothing will be exposed through the API that isn’t already published and publicly visible on your site. If the post’s set to private, password protected, or restricted in any other way, it should be omitted from the API; only public data is exposed.

The specific fix noted in the release notes was related to when somebody creates a Custom Post Type. For example if you made a “books” type to keep track of books you’d read, or something. With a custom type you can have finer-grained control of how it is exposed to the world, so I could have said, “yes, I want these books to be viewable as public URLs.” However, maybe I don’t want those to show up in the API for whatever reason. The issue that just got fixed was that if the custom post type was public, it would automatically be included in the REST API — when that was intended to be an opt-in.

Hope this helps clarify!

@photocurio Thanks for the update, I’m glad you found the cause! That one had me stumped

I brought this up in slack, and one possible cause: are the posts that are in that collection private, password-protected, not published, or otherwise restricted in any way?

To make sure I understand the issue, when you authenticate and get the first page of results, and take the ID of the first post in that collection, then /wp/v2/posts/{that id} works without authentication; but yet, the post that is publicly visible, published, and not password-protected does not show up (nor do any others) in the /posts collection when you are unauthenticated?

+1 to the PR linked in the last comment. This is definitely not “resolved” for me, as I’m seeing the issue on multiple sites running the latest version of the plugin.

Please do not ever post login info on a public forum like this – these forums do not provide that level of support AND it’s likely to get your site hacked.

That is an extremely, extremely good point.

It looks like the stack trace you’ve posted was taken with SCRIPT_DEBUG set to false; can you set it to true and paste in the Chrome JS error content again? That should give more accurate line numbers, which ought to help with identifying where the problem’s coming from.

I’d log in to test myself, but the URL you provided (https://www.triangleenglightened.com) looks like it may have a typo? When I tried https://www.triangleenlightened.com/, it told me I had to use a Google account to log in, so there wasn’t anywhere to submit the username and password you provided.

Well, if anybody else has this issue: You’re probably forgetting to call wp_reset_query() after you query against the first custom post-type. That was my issue.

Case closed. I love this forum partly because getting your thoughts together enough to post often helps you solve the issue…

I’m not sure I understand what you mean by ‘blocks us from tracking our own views’? Tracking plugins are designed to permit viewing stats, not block it. If I don’t misunderstand your question, however, I’m afraid the short answer is “no:” I don’t know of any built-in stat tracking for www.remarpro.com.

You’ll need to install a plugin of one kind or another. I use google analytics for wordpress, and it works pretty well.

I was able to fix this without any modification of the plugin at all–All I needed to do was to remind my theme to parse shortcodes in widgets. I added this to my functions.php:
add_filter('widget_text', 'do_shortcode');

and that did the trick.

Hope that helps, -KA

This is happening to me too, but in my case I believe it is related to a BBPress install that is sharing cookies and database entries with my wordpress install. I have not found a fix, but I will post if i do.