wordpress-core | Content Management System library

I'd been setting up WordPress and obtaining its required plugins via composer for some years now, it works great, but I've given up trying to hack or be tricky when it comes to installing plugins that does not know how to use WP_SITEURL and also PaaS that doesn't support non-standard WordPress folder structure.

So I am wondering if I can still use composer to setup WordPress-core (or any other package) but I want it to be installed first.

Say in your composer.json, you have the following packages:

I want to add PHP CodeSniffer to VScode.

Within VScode I am getting the error 'phpcs: The phpcs report contains invalid json'

However when I run the following command in the terminal:

How can we customize Wordpress coding standards on Windows and use them with VSCode? I am trying to do this globally so I don't have to do it for every project (I don't think currently that this is a bad idea?) but I guess the same thing can be applied to local project, only paths should be changed.

First, I have installed them in C:\wamp64\www\_standards\wpcs and I have set correct path using:

In my composer.json I have the following:

There are many wonderful tutorials describing in great detail how to set up a horizontally scaled WordPress install in AWS' Elastic Beanstalk - that part is no problem. But I haven't found any follow-up advice yet on how to manage plugin updates after the initial setup, let alone updating wordpress-core itself. Does anybody know the most optimal way to do this?

This is the methodology I'm using so far, but I'm not sure if it is the best way:

1. Download the plugin's update file and unzip it. Remove and replace the relevant folder in /wp-content/plugins (local git repo)
2. Run the update in the live site like normal - to ensure that any database changes get pushed up to the RDS
3. eb deploy from the local repo to commit the file changes and make the update persistent

Is that a sane method? Could anything get corrupted down the line?

For updating wp-core, the tutorials I've read seem overcomplicated - basically rebuild the site from scratch every time an update comes out. Below is what I have been using (used it successfully for WP 5.0.2). Is there any chance of files and databases getting out of sync using this method?

1. Download and unzip the new wordpress version locally
2. Replace wp-admin, wp-includes, and the root files except for wp-config.php (local git repo)
3. Run the update in the live environment, so that any database changes get pushed up to RDS.
4. eb deploy

This is my code to load wordpress posts outside the wordpress installation directory. I've found very useful my precedent question about and an old topic that will discuss about this usage of the wp functions in other indipendent php pages.

PHP query

Recently I unignored composer.lock along with package-lock.json (likely unrelated), and I changed our gulp deploy script to use composer install instead of composer update. Before pushing new code to prod servers I updated the lock files to the latest using composer update and npm update to make sure there was nothing weird in there from branch merges.

However the gulp deployment script hit various issues, the most problematic of which was: "Requirements could not be resolved to an installable set of packages"

gulp-tasks/deploy.js in its current state:

I'm updating Fishpig Wordpress-Integration to version 4.5.1.5 (with addons ACF, CPT, CS, Root, Multisite) in a new ansible-deployment. Now I get the follwoing error in the Magento-Backend :

I’ve installed the WordPress Coding Standards for phpcs. Running phpcs -i confirms this: