Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Activate' link on Extensions screen results in 'Plugin file does not exist.' #502

Closed
Japh opened this issue May 5, 2014 · 6 comments · Fixed by #512
Closed

'Activate' link on Extensions screen results in 'Plugin file does not exist.' #502

Japh opened this issue May 5, 2014 · 6 comments · Fixed by #512
Assignees
Labels

Comments

@Japh
Copy link

Japh commented May 5, 2014

While troubleshooting #464, I noticed that the 'Active' links on the Extensions screen don't work. The plugins can be activated from the Plugins screen as normal though.

@Japh Japh added the bug label May 5, 2014
@Japh
Copy link
Author

Japh commented May 5, 2014

This issue appears to be caused by using a different plugin path locally than that specified by https://wp-stream.com.

For example, I have the Data Exporter extension installed at 'wp-stream-data-exporter' instead of the 'stream-data-exporter' that is expected by the Extensions screen using information provided by https://wp-stream.com.

The extension is still detected correctly as being installed though.

@Japh
Copy link
Author

Japh commented May 5, 2014

@fjarrett @shadyvb This will need some work on both sides. Anyone see any potential problems with going ahead?

@fjarrett
Copy link
Contributor

fjarrett commented May 6, 2014

@Japh My guess is because you have the plugins installed on your local as direct clones from the GitHub repo and they are still using the wp- prefix in the directory names, which won't work.

Instead, the directory name should be changed when cloning, like so:

$ git clone git@github.com:x-team/wp-stream-extension.git stream-extension

@shadyvb
Copy link
Contributor

shadyvb commented May 6, 2014

@Japh @fjarrett We'll probably need to match extensions using their titles, as that won't change on both sides, at least not easily as slugs would. I'll look into this tomorrow.

@lukecarbis
Copy link
Contributor

I'm on it.

Sorry - just read your comment all the way through @shadyvb . It's all yours.

@Japh
Copy link
Author

Japh commented May 8, 2014

Brilliant, thanks guys! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants