Content type currently hard-wired to 'story' - need to provide an interface to allow content type selection

It's a permission... Go to Admin >> Users >> Permissions and find node_to_word... enable it for the roles you wish to be able to see the links.

Hi there!
I´ve enabled that and cannot actually see the link. Maybe it has something to do with my template. How is this link being created, so I can try to manually reproduce it?
Thanks!
Rosamunda

I think I´ve found the problem. Inside the module, look at line 82
if ($type == 'story') {
I´ve changed to "page" and all pages show that link...

Ah, I see. I forgot I hard-wired it. Sorry.

Please test the attached patch. I have *not* tested it, but it will apply to 6.x-1.0 or 6.x-1,x-dev, they're the same at the moment. Here's what it does:

• Additional permissions, one per type (Word and text files)
• Users with 'administer node_to_word' permissions can see an additional fieldset when they edit a content type with checkboxes for enabling/disabling both text and Word files, independently of one another, for that content type
• You can control link appearance by content type settings AND by user role

I stress again, this is untested and I'm tired. But if I'm lucky, it'll work first time. ;-)

subscribe

subscribe

Did anyone try the patch??

subscribe

Please can someone (other than me) try this patch and either mark is as "needs work" or "reviewed and tested by community". Until someone actually bothers to try this patch, instead of just typing "subscribe", it won't be committed.

I have given the permissions and changed "story" to "page". But even then I can not see those 2 links under the edit content type. Can anybody help

Am I talking to myself? Use the patch, Luke! ;-)

I've enabled the word document type for a user role, and enabled the word document download for a content type. When browsing as a user with the enabled role on the enabled content type, the link correctly appears at the bottom of the node. However when the user clicks on it, they get an access denied message.

Have you checked the permissions? Two new permissions were added, replacing the old blank permission. I did say that in #4.

+    'access Word documents',
+    'access text files',

Thanks for testing, btw - appreciate it. Please let me know if this is just a permissions problem.

Also, I should probably include auto-switching the permissions in an update hook, so users do not need to worry about this, once it is committed.

Setting back to 'needs review' for now, so more people test.

I've tested this and also see #905844: Can't get Save as Word on new node types. I think that's enough to mark it as R&TBC.

This is committed to the dev snapshot (accidentally, as it happens, but a happy accident - though I had a heart attack when I did it!)

I won't roll a release until this issue is fixed: #926530: Update from 6.x-1.0 to 6.x-1.x-dev will break permissions