mahara-contributors team mailing list archive

[François Marier <francois@xxxxxxxxxx>]

Public bug reported:

>From IRC:

<DonDadda> hi Guys, I have an issue with LEAP2A import. This is an import from 1.2.6 back into 1.2.6
 Is the email address issue responsible for this? http://mahara.org/interaction/forum/topic.php?id=2623
 Going to continue digging

<DonDadda> Hey: Just a quick side note.
 ith Mahara 1.2.6 implemented in the following environments <= PHP 5.3.2, this function bool property_exists() fails for private properties in base classes. Returning false when true.
 With Mahara 1.2.6 implemented in the following environments <= PHP 5.3.2, this function bool property_exists() fails for private properties in base classes. Returning false when true.
 Changing the classes privately declared properties to public resolved this issue.

There is also a comment to that effect on bug #576026.

We should make sure that this is fixed in 1.4 (and probably in 1.3 as
well).

** Affects: mahara
     Importance: High
         Status: Triaged

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/712904

Title:
  property_exists() returns False for private properties

Status in Mahara ePortfolio:
  Triaged

Bug description:
  From IRC:

  <DonDadda> hi Guys, I have an issue with LEAP2A import. This is an import from 1.2.6 back into 1.2.6
   Is the email address issue responsible for this? http://mahara.org/interaction/forum/topic.php?id=2623
   Going to continue digging

  <DonDadda> Hey: Just a quick side note.
   ith Mahara 1.2.6 implemented in the following environments <= PHP 5.3.2, this function bool property_exists() fails for private properties in base classes. Returning false when true.
   With Mahara 1.2.6 implemented in the following environments <= PHP 5.3.2, this function bool property_exists() fails for private properties in base classes. Returning false when true.
   Changing the classes privately declared properties to public resolved this issue.

  There is also a comment to that effect on bug #576026.

  We should make sure that this is fixed in 1.4 (and probably in 1.3 as
  well).