Title + patch say all there is to say.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | print_pdf.880400_1.patch | 368 bytes | drclaw |
| #7 | print_pdf_lib_path.patch | 369 bytes | drclaw |
| #6 | print_pdf_lib_path.patch | 349 bytes | drclaw |
| print_pdf.libraries.patch | 4.61 KB | roderik |
Title + patch say all there is to say.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | print_pdf.880400_1.patch | 368 bytes | drclaw |
| #7 | print_pdf_lib_path.patch | 369 bytes | drclaw |
| #6 | print_pdf_lib_path.patch | 349 bytes | drclaw |
| print_pdf.libraries.patch | 4.61 KB | roderik |
Comments
Comment #1
jcnventuraThe module already supports that for a very long time.. In fact, the PRINT_PDF_LIB_PATH in the lines above your patch is defined as follows:
define('PRINT_PDF_LIB_PATH', 'sites/all/libraries');But you're right.. It needs to be better documented. I've improved the INSTALL.txt file.
Comment #2
roderikLOL. That was silly of me, then.
One nitpick though: why not do a Libraries API call instead of defining the constant yourself? That way, a multisite installation can install their PDF conversion tool of choice in sites/SITENAME/libraries. Seems at least theoretically relevant to this module.
Comment #3
jcnventuraIndeed, the multisite install is important.. The problem with adding the API at this moment is the problem of having to rename the library folders to something standard.. With the obvious annoyance that you can't have a folder for TCPDF 5.7 and 5.8 residing side by side.
I'll probably submit some patches to the Libraries API to remove that annoyance and then update the module when I am satisfied..
Multisite installs can always use the sites/all/libraries anyway. And I fail to figure out why someone would want to have a version of a tool for one site and a different version for another site.
João
Comment #5
mrfelton commentedI'm reopening this issue as IMO libraries api is still needed. The libraries API allows you to put the library in an of the standard drupal locations - including /profiles/profilename/libraries - this is very important when you are working with installation profiles.
Comment #6
drclaw commentedHere's a quick fix (patch) for anyone using an install profile. Make things even easier by using drush make and patching in your make file! (that's what I'm doing)
Comment #7
drclaw commentedActually this one should work with drush make...
Comment #8
drclaw commentedNope, this one should work for sure though... =/ Sorry everyone.
Comment #9
pearcec commentedThe issue I have is that we use aegir, and drush make. We define what libraries we want during a make of the platform. If this doesn't get fixed to use Library API properly, than I have add my pdf library by hand every time I do a new build.
The original patch looks great to me. Not sure how why you need versioning of the directories.
Comment #10
jcnventuraComment #11
jcnventuraI've committed the original patch. The module will still find the libraries in /sites/all/libraries even without the libraries module, but if that is available, it will be able to find them in the additional paths provided by it.