Ditto 2.0 RC3

• • 
  • 3,250 Posts
  MARKSVIRTUALDESK Reply #11, 19 years, 6 months ago

  @mmjaeger: Do you have $stopOnNotice set to true in the index.php file?
  Anyways, try adding:
  

  			if (!is_string($v)) {
  				$v = var_export($v,true);
  			}
  

  
  
  Before the first $v = line in the debug class file and see if that helps
  
  
  @ZAP: &filter=`id,999,2` would be the filter to not remove anything. Saying 1 would mean only include id==999.
  
  I only test on the latest production release (at the moment 0.9.5) so running RC1 could be the problem. Also the parseFilters function changed drastically in Ditto 2.
  
  Found the problem. Will commit the fix to svn soon.
  
  What exactly was the ksort error?
• • 
  • 3,250 Posts
  MARKSVIRTUALDESK Reply #12, 19 years, 6 months ago

  Ok, the attachment above has the filters patch...
  
  

  
  [FIXED] wordwrap non-string warning
  [FIXED] filter variable overwrite resulting in all filters failing
  
• • 
  • 1,842 Posts
  Perrine Reply #13, 19 years, 6 months ago

  Hi there,
  
  Seems some guys have problem with .tar, here is the .zip with the last fix
  
  

  [FIXED] wordwrap non-string warning
  [FIXED] filter variable overwrite resulting in all filters failing

  
  
  Mark, if you prefer give your version in .zip, don’t hesitate to moderate my post
• • 
  • 3,250 Posts
  MARKSVIRTUALDESK Reply #14, 19 years, 6 months ago

  Drat, the last fix didn’t correct the warning....
  
  Here is the proper change (now in SVN)
  

  			if (!is_string($value)) {
  				$value = var_export($value,true);
  			}
  
• • 
  • 4,213 Posts
  doze Reply #15, 19 years, 6 months ago

  Very nice Ditto HQ! Good job Mark!
  
  
  "He can have a lollipop any time he wants to. That's what it means to be a programmer."
• • 
  • 616 Posts
  mmjaeger Reply #16, 19 years, 6 months ago

  Mark, $stopOnNotice is set to false - haven’t done any changes to the index.php file.
  
  the error still occurs
• • 
  • 3,250 Posts
  MARKSVIRTUALDESK Reply #17, 19 years, 6 months ago

  Did you change the lines I specified in the post a few minutes ago? (the second one, not the first one)
• • 
  • 616 Posts
  mmjaeger Reply #18, 19 years, 6 months ago

  Quote from: Mark at Mar 06, 2007, 03:36 AM

  
  Did you change the lines I specified in the post a few minutes ago? (the second one, not the first one)
  

  
  just downloaded the latest svn - now I’m getting this one:
  
  

  « MODx Parse Error »
  MODx encountered the following error while attempting to parse the requested resource: 
  « PHP Parse Error » 
    
  PHP error debug 
    Error:  implode() [function.implode]: Bad arguments.   
    Error type/ Nr.:  Warning - 2   
    File:  C:\Documents and Settings\Marco M. Jaeger\My Documents\My Web Sites\www\cms\modx\assets\snippets\ditto\classes\debug.class.inc.php   
    Line:  51   
    Line 51 source:  $ditto_IDs = array($ditto_lang["ditto_IDs_all"]." (".count($ditto->prefetch["dbg_IDs_pre"]).")"=>implode(", ",$ditto->prefetch["dbg_IDs_pre"]),$ditto_lang["ditto_IDs_selected"]." (".count($ditto->prefetch["dbg_IDs_post"]).")"=>implode(", ",$ditto->prefetch["dbg_IDs_post"]));    
    
  Parser timing 
    MySQL:  0.0106 s (21 Requests) 
    PHP:  0.0816 s   
    Total:  0.0921 s   
  
• • 
  • 3,250 Posts
  MARKSVIRTUALDESK Reply #19, 19 years, 6 months ago

  Ok, [FIXED] implode error in debug
  in the SVN HEAD
  
  And I found why I didn’t catch this. I’d made an adjustment to the phpError function in the MODx core to send a Growl notificiation on notices but mistakenly typed a 2 instead of an 8 for the error code bypass. And since stopOnNotice was false, the errors got surpressed.
• • 
  • 616 Posts
  mmjaeger Reply #20, 19 years, 6 months ago

  Quote from: Mark at Mar 06, 2007, 03:57 AM

  
  Ok, [FIXED] implode error in debug
  in the SVN HEAD
  
  And I found why I didn’t catch this. I’d made an adjustment to the phpError function in the MODx core to send a Growl notificiation on notices but mistakenly typed a 2 instead of an 8 for the error code bypass. And since stopOnNotice was false, the errors got surpressed.
  

  
  that did it - thank you

This discussion is closed to further replies. Keep calm and carry on.