Skip to content
This repository was archived by the owner on Jul 28, 2024. It is now read-only.

Conversation

@x1024
Copy link
Contributor

@x1024 x1024 commented Jan 17, 2018

Resolves #1313

The logging message is at the "error" level, because that's the logging level for doing "wp core download" a second time.

@borekb borekb requested review from JanVoracek and borekb January 17, 2018 22:55
@borekb
Copy link
Member

borekb commented Jan 17, 2018

Nice! I also like your explanation why it's an error. The only thing I've noticed is that a file mode is changed as well:

image

That might not be intentional.

@borekb
Copy link
Member

borekb commented Jan 17, 2018

Related to this, I'm question the term "active" as we use it:

/**
* Returns true if VersionPress is active. Note that active != activated and being
* active means that VersionPress is tracking changes.
*
* @return bool
*/
public static function isActive()

What's your opinion, isn't it too close to "activated" and therefore confusing?

@x1024
Copy link
Contributor Author

x1024 commented Jan 18, 2018

I updated the commit again. The permissions change was unintentional.

"isActive" is descriptive enough, and during the installation process it was made obvious what that means. I don't think there is a need to change that.

Copy link
Member

@borekb borekb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! 👍

@borekb borekb merged commit 129bf97 into versionpress:master Jan 18, 2018
@borekb borekb added scope: workflows Features that involve multiple clones of a site: cloning, merging, pulling, pushing, ... scope: core Core VersionPress functionality like tracking actions, creating Git commits, etc. and removed scope: workflows Features that involve multiple clones of a site: cloning, merging, pulling, pushing, ... labels Apr 14, 2019
@borekb borekb added this to the 4.0 milestone Apr 14, 2019
@borekb borekb changed the title Added error when re-activating VP with WP CLI Add error when re-activating VP with WP-CLI Apr 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

scope: core Core VersionPress functionality like tracking actions, creating Git commits, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"wp vp activate" doesn't check if VersionPress is already active

3 participants