There's no way to fix this without breaking the API, so I'm filing this as a documentation issue.

For 2.x, this needs to be changed to using a compound property, so it's $wrapper->remote->foo->value() rather than $wrapper->foo->value(), and so the clash is avoided.

Comments

das-peter’s picture

I think that would be a smart move.
I started to prefix the the properties in Clients SuiteCrm.

  • joachim committed 7c44232 on 7.x-2.x
    Issue #2379615: Changed Entity metadata remote properties to be in a...
joachim’s picture

Component: Documentation » Code
Status: Active » Fixed

Fixed in 2.x, since it breaks the API.

joachim’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev

Status: Fixed » Closed (fixed)

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