Just curious as to how easy/hard it would be to integrate this module Node Revision Reference. Or if perhaps this should be a separate module.
It may be too difficult to implement, and potentially not worth it due to the small popularity of Node Revision Reference. But thought I'd just enquire.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | nodereferrer_1034386_12.patch | 9.44 KB | bverc |
| #9 | nodereferrer_1034386_9.patch | 4.71 KB | bverc |
| #8 | nodereferrer_1034386_8.patch | 4.71 KB | bverc |
| #1 | nodereferrer_1034386_1.patch | 4.71 KB | bverc |
Comments
Comment #1
bverc commentedAfter working on this for a short time, I have a working solution. I'm not sure how stable it is, but it works.
The biggest change was to the nodereferrer_referrers() function. I would have preferred to the send the node object through, however in order to keep backwards compatibility with other modules that call this function, I added $node->vid as the last (optional) argument.
I haven't tested view integration yet, that will need some work too I assume.
Lastly, as I'm working on a postgres db, this patch assumes the #926918: Postgres compatibility patch #7 has been applied.
Comment #2
bverc commentedI'm stuck with views. when I add a relationship using a revision reference field. I get the following error:
I can see the error is caused by the incomplete query where ON node.nid = node2. LEFT JOIN, but i am unsure where this error is caused. This could potentially be a bug outside of this patch, as a incomplete query like this shouldn't happen.
@andypost, i may need your expertise here.
Comment #3
acbramley commentedApplied patch and functions as expected. The cache can throw it off a bit though. Also getting the same error as above.
Comment #4
andypostIs this patch still valid? I have no PG installs but commited #926918: Postgres compatibility
Comment #5
bverc commentedYes it should be. Did you have trouble applying it?
Comment #6
andypost@roborat I can't test your patch because have no PG installs right now
Please re-roll a patch against current d6-dev
Anyway I need another review to commit this patch
Comment #7
bverc commented@andypost, it doesnt require postgres. It just assumes the pg patch was applied in advance, which should match the current dev version. Will re-roll to be sure though.
Comment #8
bverc commentedHere is the updated patch.
As its only in RC2, do you think it would be better to send the entire node through to the function?
Could you also have a look at the views stuff, as I'm not familiar with the views integration and can't figure out what would cause that error.
Comment #9
bverc commentedOk, the patch wasn't applied to the dev version somehow, here is the real patch.
Comment #10
acbramley commentedTested patch from #9 and works as expected.
Comment #11
andypost@roborat Thanx a lot for new patch! let's gather more reviews before commit. maybe someone could provide a views fixes
I'm trying to make a D7 port of current version for now so can't test this, glad see more reviews
Comment #12
bverc commentedUpdated patch with views integration.
Comment #13
acbramley commentedThe patch in #12 was used and tested a long time ago by me in an internal project, I just forgot to update this issue. Works as expected.
Comment #14
andypostI see no definition of this type...
same
Powered by Dreditor.