I know what you are thinking Rik... but it's not what you think... lol
I am moving my personal server to a VPS server using cloud hosting and I thought it would be neat to try PHP 5.3.1 before pulling the switch... When I was making sure my setup was decent, I noticed that when I went to edit the nodes, it gave me the access denied message. Narrowed it down to Revisioning since disabling it brought back the edit options... Reverted back to PHP 5.2.12 and now everything works as expected.
I just thought I'd mention this since I ran across it, but you might have even know about this and just not support 5.3.1 yet... Either way, just wanted to see if this information could be useful to you, however, it may just be the buggy Zend support in 5.3.1 that may have caused this.
Comment | File | Size | Author |
---|---|---|---|
#1 | revisioning_705380_php53_warning_1.patch | 688 bytes | dooug |
Comments
Comment #1
dooug CreditAttribution: dooug commentedPHP 5.3.0
Drupal 6.15
Revisioning 6.x-3.4
When viewing the revisions tab:
The following patch cleared the issue.
Comment #2
RdeBoerThanks for the patch doug!
While it may get rid of the error, it seems to me that it also may get rid of some of the functionality, namely the defaulting to view/edit the latest revision when a view/edit link is clicked. This functionality required the node->load_op
I need to implement a better solution that doesn't rely on the &ref.
Comment #3
rkodrupal CreditAttribution: rkodrupal commentedwatching
Comment #4
Moosa CreditAttribution: Moosa commentedhello,
can you provide me guys with the easiest way to apply this patch ?
Comment #5
RdeBoerHey Moosa,
Because it's only 1 character that you have to remove (the ampersand
&
), the quickest way is to open the file sites/all/modules/revisioning/revisioning.module in an editor and change line 378to
Good luck!
Comment #6
dooug CreditAttribution: dooug commentedMoosa:
Checkout the Drupal Handbook page to apply patches.
Comment #7
Moosa CreditAttribution: Moosa commentedthnx RdeBoer, the quick solution solved it, no need for the patch :)
Comment #8
Moosa CreditAttribution: Moosa commentedit works fine now, the only place i get this error now is when i click publish on some pending review
warning: Parameter 2 to revisioning_revisionapi() expected to be a reference, value given in C:\xampp\htdocs\drupal\includes\module.inc on line 483.
warning: Parameter 2 to revisioning_revisionapi() expected to be a reference, value given in C:\xampp\htdocs\drupal\includes\module.inc on line 483.
Comment #9
RdeBoerThanks for reporting Moosa. I'll have to fix that instance too.
Comment #10
losman CreditAttribution: losman commentedLike Moosa, I get thesame error after I publish and no email goes out either.
warning: Parameter 2 to revisioning_revisionapi() expected to be a reference, value given in E:\wamp\www\includes\module.inc on line 483.
warning: Parameter 2 to revisioning_revisionapi() expected to be a reference, value given in E:\wamp\www\includes\module.inc on line 483.
Thanks
Losman
Comment #11
RdeBoerEither check out HEAD from the repository or edit the file
revisioning/revisioning_api.inc
, line #82 (or thereabouts) to look like this:In other words, remove the ampersand that precedes
$node
.Please report back whether this worked for you.
Comment #12
Moosa CreditAttribution: Moosa commentedok. its great now, i did change it to function revisioning_revisionapi($op, $node)
and it works fine now.
thanks alot :)
Comment #13
RdeBoerGood to hear! As mentioned this fix is already checked into the repository, so will be included in Revisiioning versions 6.x-3.6 and later.
Comment #14
losman CreditAttribution: losman commentedThis is great. It works like a charm.
RdeBoer, this is truly a great system.
Thank you for all your help.
Losman
Comment #15
RdeBoerThanks for your support Losman. Much appreciated!
Rik