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.

CommentFileSizeAuthor
#1 revisioning_705380_php53_warning_1.patch688 bytesdooug
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dooug’s picture

Status: Active » Needs work
Issue tags: +PHP 5.3
FileSize
688 bytes

PHP 5.3.0
Drupal 6.15
Revisioning 6.x-3.4

When viewing the revisions tab:

warning: Parameter 2 to _revisioning_view_edit_access_callback() expected to be a reference, value given in XXXXXX/includes/menu.inc on line 452.

The following patch cleared the issue.

RdeBoer’s picture

Assigned: Unassigned » RdeBoer
Category: feature » task

Thanks 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.

rkodrupal’s picture

watching

Moosa’s picture

hello,
can you provide me guys with the easiest way to apply this patch ?

RdeBoer’s picture

Hey 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 378

function _revisioning_view_edit_access_callback($revision_op, &$node) {

to

function _revisioning_view_edit_access_callback($revision_op, $node) {

Good luck!

dooug’s picture

Moosa’s picture

thnx RdeBoer, the quick solution solved it, no need for the patch :)

Moosa’s picture

it 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.

RdeBoer’s picture

Thanks for reporting Moosa. I'll have to fix that instance too.

losman’s picture

Like 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

RdeBoer’s picture

Either check out HEAD from the repository or edit the file revisioning/revisioning_api.inc, line #82 (or thereabouts) to look like this:

function revisioning_revisionapi($op, $node) {

In other words, remove the ampersand that precedes $node.
Please report back whether this worked for you.

Moosa’s picture

ok. its great now, i did change it to function revisioning_revisionapi($op, $node)
and it works fine now.

thanks alot :)

RdeBoer’s picture

Status: Needs work » Fixed

Good 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.

losman’s picture

This is great. It works like a charm.
RdeBoer, this is truly a great system.

Thank you for all your help.

Losman

RdeBoer’s picture

Thanks for your support Losman. Much appreciated!
Rik

Status: Fixed » Closed (fixed)
Issue tags: -PHP 5.3

Automatically closed -- issue fixed for 2 weeks with no activity.