Are there any documentation on how to deploy this to production? right now if you look at the source code, bunch of codes __NEXT_DATA__ I want to see if these codes are gone in production.

has anyone deployed the front-end to digital ocean?

Issue is about..

• [x ] a Bug Report

The logic in the sidebar templates that set the column width to .col-md-3 if both sidebars are active, or .col-md-4 if only one sidebar is active, only checks for the theme option understrap_sidebar_position. It does not take into account if a page has explicity chosen the Left and Right Sidebar Layout page template (and therefore shows both

Is your feature request related to a problem?

Yes. When writing code like the following, it's flagged as unescaped (WordPress.Security.EscapeOutput.OutputNotEscaped):

printf(
    'Foo %d Bar',
    $id
);

With some string formats, the format itself can provide adequate sanitising/escaping support. Specifically, any format which does not treat the input as a string: b

Your instructions do not mention the use of a readme.txt file on the Self Hosted Plugin or Theme instructions. Does that mean if we are going to have a self hosted plugin or theme (not in GitHub or BitBucket) that this code will not read a readme.txt file? Does the readme.txt file only get read if we have GitHub or BitBucket integration?

stylelint-webpack-plugin should be updated to ver 0.10.0, so it will install sylelint in ver 8.0.0 where new rules are available.

As a follow up to #119 … details in this GH blog post

• Add .github directory
• Add .gitignore
• Add CONTRIBUTING.md
• Add ISSUE_TEMPLATE.md
• Add PULL_REQUEST_TEMPLATE.md

Preface: This is likely to be a rare case but I figured I would raise it in case there's something we can do to prevent this in future.

I was working on a site that was getting errors after upgrading to 3.0. The original error was:

Fatal error: Uncaught RuntimeException: Error saving action: Error saving action: Table '.wp3zd0_actionscheduler_actions' doesn't exist in /var/www/html/wp-

Hello there,

Google Lighthouse tells me that the superpwa-manifest.json file is not served by HTTP/2 while the other resources are. Is this normal? Do you have the same behavior on other website?

It looks like all requests that are served from the Service Worker are marked with HTTP/1.1. This could be a bug with Google Chrome & Lighthouse (GoogleChrome/lighthouse#71

Add an option for a front-page.twig template in page.php.

Code is very similar to what we have in index.php

<?php
global $post;

$context   = \Timber\Timber::get_context();
$templates = [ 'page-' . $post->post_name . '.twig', 'page.twig' ];

if ( is_front_page() ) {
	array_unshift( $templates, 'front-page.twig' );
}
Timber::render( $templates, $context );

I have a local working https://wordpress.local with a valid autogenerated local ssl certificate (green lock in all browsers), but if i try to configure wpackio.server.js this way:

	host: 'localhost',
	proxy: 'https://wordpress.local',
	port: 3000,

i got empty response.

I'm on linux using latest master version (with latest version of all packages).

I'm not a `browser-sync/

Our wp-cli container's home page says 1.2.1 is the latest yet the tags show 1.5.1. This is not good for us if someone only looks at the main page and not the tags page.

Either we need to move to a fully-automated generation of these Docker main pages **or probably better since we can implement sooner we should remove the _"Supported tags and resp

Not sure how I missed this for so long... but I need to add a Create-React-WPTheme specific README instead of leaving the one from Create-React-App.

We have given links (Anchor Links) to enable the user to jump to various sections of the page in our website. As a result, with each click on the link, a #hash is appearing in the browser URL bar. So if a user clicks on 5 links to jump to different sections within a page, he will require 6 clicks to the browser back button to actually go back a page. How can I remove this #hash from the URL?

Describe the bug

If we run our web server on an alternate port, like 8080, let's say using wp server, then $_SERVER SERVER_NAME will not provide the correct WP_HOME calculation value, but $_SERVER HTTP_HOST does.

print_r( $_SERVER );

Array
(
    ...
    [SERVER_NAME] => localhost
    [SERVER_PORT] => 8080
    [REQUEST_URI] => /
    [HTTP_HOST] => localhost:8080
   

We should get rid of template-parts/content-*.php files because we don't use those in projects. Instead, we should add content-modular.php to the theme as it is used in every project.