Error Upgrading to concrete 5.7.5.2 -> Cannot access protected property Concrete\Core\Page\Page::$vObj

Permalink
After upgrade Concrete to version 5.7.5.2, I get the following message: Cannot access protected property Concrete\Core\Page\Page::$vObj

It appears in the register->
Exception Occurred: /homepages/0/d563658968/htdocs/esDenia/concrete5.7.4.2/packages/sb_breadcrumb_trail/blocks/sb_breadcrumb_trail/controller.php:50 Cannot access protected property Concrete\Core\Page\Page::$vObj (1)

Does anybody know what to do? Thanks!

1 Attachment

View Replies:
Mnkras replied on at Permalink Reply
Mnkras
Contact the author of sb_breadcrumb_trail, they need to update their addon.
elfo replied on at Permalink Reply
This add-on is excellent and has worked well with all versions of concrete 5.7
We need someone to help us fix it. I have it installed on more 200 pages on the sitehttp://esdenia.es/, and in three more places.
Something has happened in the new version 5.7.5.2 of concrete
Anyone can help?
ramonleenders replied on at Permalink Reply
ramonleenders
The vObj has become protected, which means you can not acces this property from the "outside" (only within the Page class and those who extend it). I think most of the things you need from a page are accessible using functions on the page object (search for the Page class and look up the function you would need). The code your/the Add-On uses should be rewritten to use these functions. I'm not my station right now, but can have a look tomorrow perhaps if you're not able to solve this problem. Is this a public Add-On you're using?
elfo replied on at Permalink Reply
ramonleenders replied on at Permalink Reply 1 Attachment
ramonleenders
Drop the contents of the attachment into your /packages directory!
il2k replied on at Permalink Reply
This works great. Maybe roll it into the official addon.
Steevb replied on at Permalink Reply
Steevb
My add-on has stopped working with 5.7.5.2 for some reason.

I cannot fix it at the moment, although I've tried.

If someone has any ideas I'd be grateful.
AndyJ replied on at Permalink Reply
Hi Steevb,
I think you are safe just to use getCollectionName() instead of vObj->cvName.
Steevb replied on at Permalink Reply
Steevb
I've already used 'getCollectionName' and received a different error.

What I'd wrong was modified controller code with add-on installed!!

I should have modified and then reinstalled.

Thanks for your help, uploading new version. All should be good now?
ramonleenders replied on at Permalink Reply
ramonleenders
That seems to have done the trick. My message earlier is to no use then, as I made the same changes as you did.

@elfo, just update to the latest version of the Add-On!
Steevb replied on at Permalink Reply
Steevb
@ramon

If you had not given me the block to insert and start again I would still have the error. So thanks for making me do a fresh install.

Regards
Steev