custom post types – Conditional editing CPT – using editor’s role and author’s usermeta

I have created a custom post type.

Each author is attributed to a editor group when her/his account is created.
This is save on the author’s user meta

I created two roles with administrator capabilities, one for each editor group.

I want to allow (or deny) the editors to edit the posts based on their role and on the author’s user meta.

Where can I begin?

List of all authors avatars

I’m looking for a way to retrieve all authors with their avatar.

I know there is a way to get an authors avatar but I want to get all avatars of all the authors 🙂

echo get_avatar(get_the_author_meta('ID'), '160');

I tried to combine this command with wp_list_authors() but didn’t find a way.

How can I retrieve a list of all authors with their avatars?

Thank you!

bitcoincore development – I have written a test for an open Bitcoin Core PR. Should I open a PR to the author’s fork or wait for it to be merged?

It depends on the situation. When the change is a few lines of code it is sufficient to show the author the patch and they will amend the pull request. You can do this using a “` diff in the comments or link to your branch in the comments.

If it is a bigger change, to avoid the clutter of the GitHub UI you can surround it by <details><summary>patch to do foo</summary>```diff ... ```</details>.

However, if it is a really significant change you should probably open a PR to the author’s fork of the Bitcoin Core repo asking to merge yourfork/yourbranch into PR-author/PR-branch.

One difference between posting the patch in the GitHub comments vs linking to your branch is that the former will continue to exist even after you delete your branch. Somebody may be curious to look at the patch years later.

This question was answered by vasild on IRC and has been paraphrased.

wp query – Get authors by term id or slug

This question sounds wired but I am in a situation where I need to list all author who posted in a particular term.

What I did so far, I am able to get all posts under a particular term and stored the author id into an array. But, the problem is that to create pagination over it. Does anyone know any better way to do that or any query to achieve that or any functions to solve my issue(I tried to find it out but did not get any good solution)?

Allowing anonymous users to contact node authors

I want anonymous users to send messages to node authors. Also I want the sent messages to be visible to node authors in their user account. Here is what I have tried so far:

  • Private message – Solves what I am looking for but does not work for anonymous users
  • Webforms – New to it but I don’t see a way for node authors to access the sent messages within their account

html – When making a website that is font-size responsive, are there any guidelines to what font-sizes authors blow text up to?

It seems an opinion whether or not, as web-developers, we should design websites taking into account the user increasing font-size (e.g. on Chrome: Chrome>Settings>Customise fonts). (Although it was last suggested to me that most people do not).

However, going on the basis that we do:

I presume people test by increasing the font-size of their pages at different viewport dimension sizes. Are there any guidelines as to what font-sizes people blow the font up to (for any given viewport dimension)?

http – Why didn't browser authors make 127.0.0.1/localhost-hosted websites skip the referrer?

For a long time I was so convinced that 127.0.0.1/localhost-hosted websites, ie with URLs like:

http://127.0.0.1/MySecretControlPanel/sensitive.php?stuff=goes&here=dude

… did not send the "HTTP referrer" header when you click on hyperlinks.

But they do it! That is, unless you go out of your way to find out and proactively add a special header:


This means that for the longest time every damn site I visited via a link in my control panel saw my private, sensitive URLs!

I clicked a lot of links. In many cases I have links that I can use to easily check things out. All of these websites could see my URLs. Even though they were hosted on site.

Again, I was so sure that browser writers would have the basic sense to skip the header for such websites. After all, they explicitly skip 127.0.0.1/localhost for proxies by default, so in my opinion this was a matter of course. But it was not a matter of course. It wasn't done at all.

Now a number of websites around the world could theoretically find out exactly what I saw on their website (because the name of my application and therefore the URL after the / is very unique), and they have it metric tons of sensitive "search query" data that I entered because I thought it was private and secure, even though the stupid fucking browser (Firefox / Pale Moon) only shared that data with the world.

I just wonder why they made that decision. The whole concept of "referrer" is initially evil, at least if it contains more than the host name. At least if they only saw "127.0.0.1" it wouldn't be that bad.

And it doesn't help me to say that I should "have checked". I know I should have had. Just as I will know that I "should" have done this and that after it is too late, but the point is that I never thought of testing it because it seemed like something that was not even tested had to.