WordPress with Composer and different plugins for dev/live.

I’m using a Bedrock-like setup where I handle WordPress core & plugins with Composer. I have my usual plugins in my composer.json within the “require” block, and some dev related plugins in “require-dev”. On dev/staging I do composer install and on the live site I do composer install –no-dev. Thats fine and all, but when … Read more

In a continuous integration environment how do you implement the database entries for plugins and themes

I’m setting up a wordpress continuous integration environment – git->composer->bitbucket-AWS codepipeline, etc. I have yet to figure out how I automate, for the development team, the setup of the WordPress meta data stored in the database. Theme customization, plugin setup/configuration, how to handle licensed plugins such as Offload Media Pro – where I can’t share … Read more

How can I have case-sensitive theme directory names when installed with Composer?

I’m using SatisPress (https://github.com/cedaro/satispress) to expose some premium plugins and themes as composer packages, because I would like to use the roots/bedrock boilerplate. Now I have the following issue: The Divi theme (https://www.elegantthemes.com/gallery/divi/) uses a capital letter for the themes directory (“Divi” not “divi”). Now when I use composer require satispress/divi it downloads the package … Read more

Install wordpress using composer in a specific language

I’m using composer to automatically deploy wordpress on a ubuntu-server. Additionally, I need to install the german language pack. I learned that there are some guys who create composer-packages from the wordpress.org files. Using the following composer.json I get wordpress with german language pack: { “repositories”: [{ “type”: “composer”, “url”: “https://wp-languages.github.io” }], “require”: { “johnpbloch/wordpress”: … Read more

Namespacing WordPress project according to FIG standards

I am trying to wrap my head around the namespaces, autoloaders and FIG standards and most importantly how to achieve their integration to WordPress as close as possible. Here is my file structure, created with help of awesome roots/bedrock WordPress stack. |– /web | |– /app | | |– /mu-plugins | | | |– autoload.php … Read more

Using composer for dependency management in plugindevelopment

I’m new to wordpress plugin development. Normally I would use composer to add thirdparty libs to my code, but I couldn’t find any wordpress plugin on github that uses composer for that. I read about wpackagist.org and the way composer can be used to manage dependencies between wordpress plugins. In this case there would be … Read more

Autoloading in Child Theme

I’m trying to autoload the vendor/autoload.php from my parent theme into my child theme. heres what i have tried but to no avail: function beast_theme_setup() { $var1 = get_theme_root_uri() . ‘/beast/vendor/autoload.php’; $var2 = get_theme_root_uri() . ‘/beast/functions.php’; $var = locate_template( array( $var1, $var2), true, false ); var_dump($var); } add_action( ‘after_setup_theme’, ‘beast_theme_setup’, 11 ); and include get_theme_root_uri() … Read more