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

Version confusion #672

Closed
hced opened this issue Oct 9, 2013 · 7 comments
Closed

Version confusion #672

hced opened this issue Oct 9, 2013 · 7 comments

Comments

@hced
Copy link

hced commented Oct 9, 2013

On this page, it's indicated that docpad@6.53 is currently the newest version.

Having the latest node & npm installed, grabbing docpad via npm install -g docpad and then doing docpad --version gives me docpad 6.48.1.

@greduan
Copy link
Contributor

greduan commented Oct 9, 2013

That's strange...

Could you try running sudo npm install -g docpad@6.53.1 and then in your project's root folder (where you can find the package.json and docpad.coffee files) could you run docpad udpate?

After that what does docpad --version return?

@balupton
Copy link
Member

balupton commented Oct 9, 2013

As a todo for the core, we should have docpad --version output at the end which installation or is for.

@hced
Copy link
Author

hced commented Oct 9, 2013

Greduan: thanks, your advice helped me at least partially:

Did what you said and the global docpad won't update further from 6.48.1 for some weird reason (I've experienced this before; seems something's odd with npm on my system). However, doing docpad --version inside my project outputs 6.53.2.

Edit: I will close this issue as I highly suspect this problem is isolated to my system only.

@hced hced closed this as completed Oct 9, 2013
@greduan
Copy link
Contributor

greduan commented Oct 9, 2013

@hced Ah OK. The reason for this is because it's outputting the version of the local DocPad version. The one inside your project and not the global one.

Glad that helped. :)

@balupton balupton reopened this Oct 10, 2013
@balupton
Copy link
Member

Re-opening, we need to figure out why @hced's global version is not updating, as other users may be experiencing this but not reporting it.

balupton added a commit that referenced this issue Oct 10, 2013
- v6.53.3 October 10, 2013
	- No need to load in the DocPad `package.json` file each load
	- We now output whether or not we are a global or local installation with `docpad --version`
		- Thanks to [Henrik Cederblad](https://github.com/hced) and [Eduán Lávaque](https://github.com/Greduan) for [issue #672](#672)
@balupton
Copy link
Member

v6.53.3 just released which will now outputs what installation the version is for - doesn't fix the issue, but helps debugging it.

balupton added a commit that referenced this issue Oct 23, 2013
- v6.53.3 October 10, 2013
	- No need to load in the DocPad `package.json` file each load
	- We now output whether or not we are a global or local installation with `docpad --version`
		- Thanks to [Henrik Cederblad](https://github.com/hced) and [Eduán Lávaque](https://github.com/Greduan) for [issue #672](#672)
@pflannery
Copy link
Contributor

@hced are you on windows by any chance?

because there is an npm plugin installation path difference when using different console types on windows..see here for more info and fix

@balupton it maybe useful to add the program location too...i.e. when running "npm" by itself it outputs it's program location with it's current version at the very bottom

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

No branches or pull requests

4 participants