typofi

Thanks for the thorough reply! I’ve tried a different browser and now also with a different authenticator. So far no change. Wordfence and server time are aligned. But I’ll keep digging further following your advice.

Thank you so much! It works perfectly now!

I basically a site which is completely private. All pages and posts are private. But the clients who log in have the capability to read_private_posts. And each client sees different posts designated with category tags.

It has been quite difficult to set up, but your plugin has now made this much much easier!

It works nicely! Thank you!

But it only works with the basic settings.

I tried using the option for “Do not ignore other parameters” and set “Get posts with this post status” to Private, and that doesn’t work. Then it just lists all the posts that are private.

The same problem is if I mark “Get posts with this post status” to Any. Then it lists all the posts.

Optimally, it would be great if these two options could be combined. So all the posts are private, but the logged in user sees a lists of posts that are designated to them through a category label.

Thank you so much! I will test this during the weekend and get back to you.

Thank you! Works perfectly!

Hi, thanks for the reply but you missed the bit where I tried to tell that in this case the user is not the author. That’s the whole point of what I am trying to do.

I’m not displaying the author’s posts to the author. That would be simple. I want to display a certain set of posts to the user by using a category, regardless of who the author is.

So the easiest way to do this, as far as I can see is to have a category that is the same as the user name. Then I just need to query the user name and feed that into Display Posts as an attribute.

• This reply was modified 4 years, 7 months ago by typofi.

Thanks for the advice!

I can achieve the result like this:

1. In child theme’s functions.php:
a) Create customised twentysixteen_entry_meta function which does not include the Author & Date info.
b) Create a new function custom_entry_meta which contains only the Author & Date info.

2. Create custom page content-single.php to the child theme:
a) Which enters the new custom_entry_meta to the entry-header after the entry-title.
b) Which enters the modified twentysixteen_entry_meta into the entry-footer.

But I would love to know if this can be done only with the child-theme’s functions.php or something lke that. Or if anyone has better suggestions on how to do this.

Basically I’m trying to avoid creating custom pages to the child theme.

Okay, looks like my question might have been based on using a misbehaving MAMP. Because when I was seeing those odd media query overrides the site was just on MAMP localhost. Now that my site is actually online, the css works like it should. All non-specific css seems to work in all screen sizes.

Regarding the specificity: In the child theme’s style.css file, should I place changes to media queries above or below the global changes?

Is everyone just confused because I said this was a newbie question? Yes, I get the whole point of media queries. And therefore, my question:

What is the best way to write CSS modifications to Twenty Sixteen theme through a child theme, so that the changes are implemented always despite what @media the user is on. (I.e. we could call such changes… oh, I don’t know… “global”.)

Thanks for replying and that specificity link looks great. But I wasn’t expecting a generic answer but a theme related one. After all this is the Twenty Sixteen forum, right? (Hence the question about “global modifications to THE theme”. ?? )

My point was how to best do global css modifications to Twenty Sixteen. I already assumed that this is done with a child theme. I should have been clearer in my question.

I tried writing generic css mods to my 2016 child theme but they usually seemed to get overridden by the various media queries etc. by the parent theme. For example, writing a non-specific removal of the avatar did the trick for the mobile versions of 2016, but then the avatar popped back up when I viewed the large screen versions.

So I came up with what I showed in my example. And that made me wonder about if I’m doing it wrong in some way. That perhaps there’s a better way of doing global changes for Twenty Sixteen?

Thanks from me too. While this plugin is already great, I think it would be even better if excluding it from certain content could be made a bit more practical. Either some kind of checkbox thing in the plugin settings or on the page/post edit page (like AddToAny).

Or simply a field in the settings for excluding pages & posts by ID [Exclude=”x,x,x,x”].

Ok. Thanks for the quick response! At least now I won’t waste any time on trying to do it. ??

Thanks nandanjha! I’ll try that one. Looks very promising.

No replies? No ideas?

Just to prove my point, we already had one person pushing the wrong button and publishing immediately.

Is there a way to even implement a confirmation question: “Are you sure you wish to publish immediately?”