WordPress

Feature request

Place the access_log and error_log directives inside the main server block instead of http block.

Feature description

Disable access_log at http block:
File: /etc/nginx/nginx.conf

# ...
http {
    # ...
    access_log off;
    # ...
}
# ...

Enable per site access_log and error_log at main server block:
File: /etc/nginx/

Quick summary

This is to track the underlying bug behind issues like Automattic/wp-calypso#63291 (and as originally discussed for example at p1651671145311929-slack-C0117V2PCAE).

Basically the problem is that Calypso makes API requests to /rest/v1.1/products?type=all for WordPress.com sites and /rest/v1.1/products?type=jetpack for Jetpack sites (the latter o

The package @wordpress/viewport attempts to use @wordpress/element from build/with-viewport-match.js and build-module/with-viewport-match.js, but does not declare a dependency or peer dependency on that package.

This happens to work with npm's hoisting due to other dependencies pulling that package in, but will fail with yarn's p'n'p or pnpm with hoisting disabled.

Reproduction

Performance/Caching section of the docs isn't clear enough. It says that the default caching mode is CACHE_TRANSIENT, but there's no explanation on what does it actually mean.

Does it mean that all queries are cached using transients? If so then it would be good to mention what is the default cache expiration and what are the implications

• Corcel Version: "jgrossi/corcel": "2.5.*",

• Framework Name & Version: "laravel/framework": "5.5.*",

• PHP Version: 7.1

Description:

Cant find model... for

// clean and simple all posts from a category
$cat = Category::slug('uncategorized')->posts->first();
$cat->posts->each(function($post) {
echo $post->post_title;
});

MySQL has phpMyAdmin integration with Lando for administration, is there a similar solution for PostgreSQL?

Expected behavior

When I tap a "Spotlight suggestion" to go to a specific site I expect to go to this site.

Actual behavior

The currently selected site doesn't change:

https://user-images.githubusercontent.com/7040243/155019852-cc84cf93-31f1-4254-aaca-f8c4c2dec52c.MP4

Steps to reproduce the behavior

1. Install the app
2. Log in into an account with multiple sites

As a user, I would like to be able to query a comment by database id.

Currently, the comment query doesn't allow for different id types (such as database id), but many other "single node" entry fields in the Graph support an idType field, such as:

{
  post( id: 123, idType: DATABASE_ID ) { __typename, id }
  contentNode( id: 123 idType: DATABASE_ID ) { __typename, id }
}

Bug report

• I've updated both my project and my packages to the latest Frontity versions: https://docs.frontity.org/guides/keep-frontity-updated
• I've searched for existing issues.
• I've checked the documentation: https://docs.frontity.org
• I've checked the community forum: https://community.frontity.org

As brought up at p5T066-3c9-p2#comment-12233, it'd be nice to display the app's current locale as a secondary label to the main Interface Language label under App Settings:

This could likely be achieved by utilising `mLanguagePreference.setSumma

Need to create /etc/hosts entry for non-wildcard alias domains in site create and site update.