BUG: Windows 8.1

[sohailalam2]

There seems to be a bug in the License Agreement module.
I know this is a duplicate issue, but none of the solutions worked for me. :(

Couple of points:

1. Nothing happens after the License, whatever I choose (Y/n) doesn't matter, and it quits abnormally without displaying any error.
2. Docpad is not remembering my choice of License Agreement and asking about the License again
3. I have manually created .docpad.cson as pointed out by @nikoskip in docpad run in windows 8.1 64bit (keep asking for terms of use) #851 but nothing happens. Docpad still asks me about the License
4. And, Yes! I also tried running Command Prompt (Console) as an Admin, but unsuccessful.
5. I also tried the same on Fedora 20 (running as a VM on Windows 8.1) and strangely enough it DID NOT work there either.

node v0.10.28
npm v1.4.9
docpad v6.69.0

[greduan]

This is a different issue though as far as I can tell. This is about the newsletter, while the other problem was about the license agreement.

However, it seems they are related.

@balupton I really think this should be looked into, enough users have encountered this problem in order to confirm it's a real issue.

[sohailalam2]

@greduan
Actually, this issue was/is also about the License.
I used --offline to accept the license agreement once hence its not showing now. But without --offline it was showing everytime I ran Docpad.

Just a few suggestions:
Why not remove the Licensing and Newsletter module from current release all-together.
We can simply display something like "By using this piece of software, you agree to the terms and conditions...." etc.
And for newsletter, one could subscribe from the website instead of CLI.

I need something like Docpad soon... :(

[greduan]

That's something for @balupton to decide. I am not yet familiar with the codebase in order to make changes like that...

[mikeumus]

This is happening for me on Chromebook as well.

[adam-stokes]

Happens on Linux as well

• Ubuntu 14.04
• docpad v6.69.0 (global installation: /home/adam/npm/lib/node_modules/docpad)
• npm 1.4.23
• node 0.10.30

Also tested on a skeleton site https://github.com/Clearskyabove/zurb-foundation.docpad and same issue happens there as well

[balupton]

#488 (comment)

[pflannery]

I see this issue on Windows 7 too and I have full admin rights when running.

I've found that it doesn't execute the callback when adding this track runner task but instead it just drops out of the app.

A temporary workaround is to create docpad.coffee file in the root containing the following:

module.exports = 

    reportStatistics: false

Exec docpad run, complete the questionare and once you've completed it then delete the docpad.coffee file. Now run docpad run again and it will give you the scaffold project menu.

[adam-stokes]

@pflannery awesome!, thanks for the workaround I can verify this works on Ubuntu as well.

[adam-stokes]

@balupton and no I don't run npm/node as sudo everything is installed within my user's home dir, my .npmrc has

prefix = /home/adam/npm

and docpad is installed in $HOME/npm/lib/node_modules/docpad