It would be useful to be able to tie editions to specific revisions of a node. For example, you want Edition 1 of your e-publish publication to point to some page content type. But, you also want Edition 2 to point to the same page, but on a newer revision. That way, when users browse through the archives, the specific edition will pull the correct revision from the nodes that make up that edition.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | epublish.module.txt | 108.79 KB | rconstantine |
| #3 | epublish.zip_.patch | 40.96 KB | rconstantine |
| #2 | test_0.patch | 70.79 KB | rconstantine |
Comments
Comment #1
rconstantine commentedI'm working on this. Will post some kind of patch-like thingy when I finish.
Comment #2
rconstantine commentedI use subversion for my local repository and I'm not sure my patches end up the same as those typically used here. So I'm going to attach a patch here, then follow that up with a zip of the complete files.
You should now see a list of revisions when selecting which nodes to include in a publication. Nodes without multiple revisions have unchanged links, while those with have links that look like this: node/$nid/revisions/$vid/view.
It seems you can't use the URL structure above unless more than one revision exists.
Anyway, all layouts should work. There's a new install file update, so be sure to update your database. There's also now an uninstall function which it seems there never was before. I still need to add the removal of all variables from the variables table, but who knows when I'll get around to that. At least the db tables can now be removed at uninstallation.
Please review these mods.
Comment #3
rconstantine commentedAnd the whole module, zipped (you'll have to rename from .zip.patch to .zip).
Comment #4
rconstantine commentedBy the way, ignore all of the TODO notes. Those are for me to OG-ify the module.
Comment #5
rconstantine commentedSorry guys. It seems I changed something toward the end that was working before. I'll have to hunt down what I did and repost.
Comment #6
rconstantine commentedChanged the last two functions in the module file and all seems to be well now. Either use the above patch then cut/paste the last two functions from this file over the top, or use the zip file and replace that module file with this one. Of course, remove the .txt extension from the file.
Comment #7
rconstantine commentedI forgot to mention the limitation - you cannot have the same revision appear in multiple editions as the navigation links will get messed up. You can have two revisions in the same publication. So if you need the same text in more than one edition, I suggest creating a fake revision.
Comment #8
sdague commented5.x has been moved to unsupported, closing all outstanding 5.x issues to clean up the tracker