dsm() and dpm() do not display protected or private object fields

same problem.

Closed #1246380: Expose module defined objects and their properties in Krumo as a duplicate of this issue.

The referenced bug in #1 has been fixed since 2 years before this bug report was created.

There are two upstream feature requests for krumo that have been untouched since 2007:
http://sourceforge.net/tracker/?func=detail&aid=1703502&group_id=194198&...
http://sourceforge.net/tracker/?func=detail&aid=1703503&group_id=194198&...

The last krumo-version is from 2007.

Subscribing.

Here's a patch that hacks the bundled krumo to use the Reflection-API to expose protected and private properties.

I think we can as well start maintaining it ourselves - the last commit to krumo's repository was 2008. http://sourceforge.net/projects/krumo/stats/scm?repo=SVNRepository&dates...

And AFAIK the LGPL allows redistribution under GPL. From https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License :

"One feature of the LGPL is that one can convert any LGPLed piece of software into a GPLed piece of software (section 3 of the license). This feature allows for direct reuse of LGPLed code in GPLed libraries and applications."

See
#1003570-1: Krumo outputs DateTime on date objects - might as well just print the text time
and
#1002462-7: Show "trail of keys" for nested krumo items
for Moshe's view on this.

Patch in #5 works fine for devel 7.x-1.3. Acceptable for me.

No, it doesn't. stdClass objects (quite common in Drupal) aren't rendered properly.

I changed line 978 from

  if ($_is_object) {

to

  if ($_is_object && get_class($data) != 'stdClass') {

and now it is acceptable.

Thank you for your work on this, but donquixote is rewriting krumo in #1853112: Replacement for Krumo?.

Please chime in there...

That'll take another year or so though. Long live open source communities.

Hehehe, I had to become Devel maintainer for some of my patches to get in...

It's no secret that we wanted to get rid of krumo. In the meantime you're free to use the patch...

That should make you happy!   :-)

Since nobody wants to maintain Krumo any more, and that I still really like Krumo and have some improvements/bugfixes I wish to make to it anyway, I've volunteered to be maintainer.

I've forked the code to github here: https://github.com/matthewbaggett/krumo and applied torotils patch.

Pull requests welcome.

Devel has added a few patches to its krumo over the years. Would be good if you would consider those on Github. After that, we could consider switching to using your project. Thanks!

Just for convenience: Here's the patch including the suggestion from comment #11.

Hi guys,
patch from #11 and #17 loses public properties when use __get and __set.

Attached patch which uses reflection to get protected and private properties and normal krumo algorithm to retrieve public properties.
Protected properties are suffixed with ":protected" and private properties are suffixed with ":private".

I found the patch from #18 to be extremely helpful. Thanks Mav-im and everyone else who worked on this.

#18 looks nice and clean, except, please don't touch any unrelated lines:

+++ b/krumo/class.krumo.php
@@ -988,18 +1011,18 @@ This is a list of all the values from the <code><b><?php echo realpath($ini_file
-      }
+    }
 
     // get real value
     //
     if ($_is_object) {
       $v =& $data->$k;
-      } else {
+    } else {
       $v =& $data[$k];
-      }
+    }
 
     krumo::_dump($v,$k);
-    } ?>
+  } ?>

Leave the bad indenting as it is. We want to touch Krumo as little as possible.

>> #18 looks nice and clean, except, please don't touch any unrelated lines:

Sorry, PHPStorm insisted this )
Please, change it if needed.

patch works well

Status bump. :)

Sorry, PHPStorm insisted this )

So do I... :-)

Patch in #18 worked as a charm for me... I reupload this patch without last unneeded lines.

Ok, thanks all!

Thank you Salvis!

Edited, I thought there was a problem but there's no problem.