This module provide an implementation of the odtphp library to allow the filling of odt template files through one node fields.
Just create a new content type containing the fields needed, upload the ODT template and associate its variable with the content type fields. Then a new button will appear on node view to download the filled in odt. To know how to create ODT templates in order to be used with this module refer to the tutorials described here.
I think there is not another module doing the same at this moment.
Project Page: http://drupal.org/sandbox/DarthDrupal/1334622
Git Repo: git clone --branch master DarthDrupal@git.drupal.org:sandbox/DarthDrupal/1334622.git
The module has been developed for Drupal 7.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | drupalcs-result.txt | 886 bytes | klausi |
Comments
Comment #1
chakrapani commentedIt appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Go and review some other project applications, so we can get back to yours sooner.
Comment #2
DarthDrupal commentedThanks for the tips! I'll correct them as soon as possible! It's the first time I develop a drupal module. :)
Comment #3
DarthDrupal commentedOk, I created the 7.x-1.x branch, fixed all minor warnings and removed the translations folder.
You can test the module again.
Thanks.
Comment #4
chakrapani commentedAll text files should end in a single newline (\n). See http://drupal.org/node/318#indenting
./odt_filler.module ./README.txt ./odt_filler.info ./odt_filler.admin.inc ./odt_filler_stream.inc ./odt_filler.install ./odt_filler.inc
Don't forget to change the status to 'needs review' after you make the changes.
Comment #5
DarthDrupal commentedFixed in 7.x-1.x
Comment #6
doitDave commentedAutomated review (Please keep in mind that this is primarily a high level check that does not replace but, after all, eases the review process. There is no guarantee that no other issues could show up in a more in-depth manual follow-up review.)
Review of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Go and review some other project applications, so we can get back to yours sooner.
Comment #7
DarthDrupal commentedFixed in 7.x-1.x
Comment #8
klausiThere are still files other than README.txt in the master branch, make sure to remove them. See also step 5 in http://drupal.org/node/1127732
Review of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Go and review some other project applications, so we can get back to yours sooner.
manual review:
Comment #9
DarthDrupal commentedThanks klausi.
- fixed the master branch
- fixed issues of the automatic review
- fixed all issues of the manual review but the first regarding the library path. I looked for a solution but the only alternative way seems to be the Libraries API implementation. I would avoid other module dependencies is possible. Can you provide me another solution for this issue?
Thanks
Comment #10
klausi"'#value' => $tpl->button_name,": button_name is user provided input, so you should run it through check_plain().
Otherwise looks good to me.
Comment #11
avpaderno