# Adding plugin to composer after installed trough wordpress

**URL:** <https://discourse.roots.io/t/adding-plugin-to-composer-after-installed-trough-wordpress/6397>\
**Category:** bedrock\
**Tags:** composer\
**Created:** [April 6, 2016, 6:51pm UTC](https://discourse.roots.io/t/adding-plugin-to-composer-after-installed-trough-wordpress/6397 "2016-04-06T18:51:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jecko](https://discourse.roots.io/user_avatar/discourse.roots.io/jecko/32/6956_2.png) [@jecko](https://discourse.roots.io/u/jecko)\
**Post date:** [April 6, 2016, 6:51pm UTC](https://discourse.roots.io/t/adding-plugin-to-composer-after-installed-trough-wordpress/6397/1 "2016-04-06T18:51:31Z")

</div>

Hi,

I have installed Wordpress plugins through usual admin interface.

After a deploy to staging environment, I realize that Bedrock is setup by default to manage plugin with Composer in stage/prod env.

As I see the advantage to use it after research about it and that I finally found this package that I wanted in packagist : Is it risky to required them with composer with a plugin like Polylang that affects a lot the database?

I don’t want to loose my translated texts or break the database structure for Polylang.

Thank you

---

<div class="post-metadata">

**Author:** ![masoninthesis](https://discourse.roots.io/user_avatar/discourse.roots.io/masoninthesis/32/13111_2.png) [@masoninthesis](https://discourse.roots.io/u/masoninthesis)\
**Post date:** [April 6, 2016, 7:06pm UTC](https://discourse.roots.io/t/adding-plugin-to-composer-after-installed-trough-wordpress/6397/2 "2016-04-06T19:06:55Z")

</div>

Hey @jecko,

Someone can correct me if I’m wrong– I believe you can manually add plugins through the local dev only, and those aren’t setup to push to staging/production unless they’re installed to composer.

As far as Polylang goes, I don’t think there should be a problem. If it’s a huge concern, you may want to look into managed db backups.

You can tie in [Polylang through wpackagist](https://wpackagist.org/search?q=polylang&type=any&search=), which is convenient.

Although it looks like [WPML](https://wpml.org/?) is a [roots recommended plugin](https://roots.io/sage/docs/extending-customizing-sage/) that does the same thing.

---

<div class="post-metadata">

**Author:** ![jecko](https://discourse.roots.io/user_avatar/discourse.roots.io/jecko/32/6956_2.png) [@jecko](https://discourse.roots.io/u/jecko)\
**Post date:** [April 6, 2016, 8:38pm UTC](https://discourse.roots.io/t/adding-plugin-to-composer-after-installed-trough-wordpress/6397/3 "2016-04-06T20:38:05Z")

</div>

Thank you, worked very well and confirm Composer is good to use.

---

<div class="post-metadata">

**Author:** ![jecko](https://discourse.roots.io/user_avatar/discourse.roots.io/jecko/32/6956_2.png) [@jecko](https://discourse.roots.io/u/jecko)\
**Post date:** [April 7, 2016, 3:06pm UTC](https://discourse.roots.io/t/adding-plugin-to-composer-after-installed-trough-wordpress/6397/4 "2016-04-07T15:06:30Z")

</div>

Ohh gosh! My staging environnement stops to work after I re-deploy to update composer uses. Says:

```
TASK: [deploy | WordPress Installed?] ***************************************** 
failed: [XXX.XXX.XX.XXX] => {"changed": false, "cmd": ["wp", "core", "is-installed"], "delta": "0:00:00.043192", "end": "2016-04-07 14:14:38.329698", "failed": true, "failed_when_result": true, "rc": 1, "start": "2016-04-07 14:14:38.286506", "stdout_lines": [], "warnings": []}
stderr: Error: This does not seem to be a WordPress install.
Pass --path=`path/to/wordpress` or run `wp core download`.

```

All the WP files are there, read a lot of thing about similar error message but not sure that applies to my case.

Should I pass the --path parameter to deploy command?

Thank you

---

<div class="post-metadata">

**Author:** ![ben](https://discourse.roots.io/user_avatar/discourse.roots.io/ben/32/11377_2.png) [@ben](https://discourse.roots.io/u/ben)\
**Post date:** [February 26, 2022, 3:08am UTC](https://discourse.roots.io/t/adding-plugin-to-composer-after-installed-trough-wordpress/6397/5 "2022-02-26T03:08:45Z")

</div>

Archived on February 26, 2022, 3:08am UTC


