next »

[Mark]

Whats new in Ditto 2?

   •   New document and TV retrieval logic for up to 4x the performance of Ditto 1 when used with large quantities of documents
   •   No more tv prefixes!
   •   PHx support
   •   Optional randomization of the results
   •   Extender architecture to allow users to expand Ditto's functionality and create their own custom placeholders
      ⁃   Request extender for functionality like DittoMachine
      ⁃   Summary placeholder has been moved to an extender
      ⁃   All tagging code is now an extender
   •   New powerful debug console for quicker troubleshooting
   •   Archives have been removed and recreated in the new snippet Reflect available in the Ditto package as reflect.snippet.inc.php
   •   QE style placeholders with edit links now possible via the [+#item+] syntax
   •   Tags now support multiple tagData sources in a comma delimited fashion and the [+tagLinks+] placeholder for a nice tag list
      ⁃   There is now a case sensitive parameter that allows you to decide if you want the tag comparison to be case sensitive or not
   •   It is now possible to have multiple Ditto calls with url based features on one page thanks to the id parameter
   •   A new config architecture allowing users to create config files in the config directory with the simple php variable syntax
   •   Added new @bindings for templates including @CODE: and @FILE: for their respective purposes
   •   New formats including XML and ATOM
   •   Parents and documents options now available, start ID deprecated (will still work though...)
   •   Added between filtering for dates for use in conjunction with Reflect based archives or custom links
   •   Hooks for custom filters and placeholders in extenders and config files
   •   The obligatory much much more...

You can download a copy at the end of this post
You can browse the all new documentation and Ditto HQ at http://ditto.modxcms.com

Enjoy!

Version control provided by the awesome guys at CVS Dude

[rthrash]

Great job Mark. The documentation is really helpful and well-formatted.

[gcruz]

This tar seems to crash stuffit on my Mac. Any possibility you can provide it as a zip?

Looking forward to trying this out and thanks for all the hard work!

[sottwell]

I get a lot of stuff crashing stuffit on my mac... I downloaded EZ 7Z and have never had any problems with it. It's just a front-end to the command line gzip etc, so it's pretty solid.

[gcruz]

I was going through your documentation (very comprehensive!) and I was wondering if there is an example on how to use the tagging feature explained here:

http://ditto.modxcms.com/files/assets/snippets/ditto/extenders/tagging-extender-inc-php.html

I was trying this with not much success:
http://wiki.modxcms.com/index.php/Category_Tagging_with_Ditto

Is 2.0 different?

[Mark]

See the 0.9.6 demo content page "Blog" for a tagging example. After 2.0 is final I will release the screencast showing how to do it step by step.

[gcruz]

See the 0.9.6 demo content page "Blog" for a tagging example. After 2.0 is final I will release the screencast showing how to do it step by step.

I looked here but didn't see any tags?
http://modxcms.com/blog.html

I also did a forum search for 0.9.6 and got
Your query was not specific enough. Try using larger words, or less common phrases

Tried the EZ 7z app above and got this error:
7-Zip (A) 4.42  Copyright (c) 1999-2006 Igor Pavlov  2006-05-14
p7zip Version 4.42 (locale=C,Utf16=off,HugeFiles=on,2 CPUs)

Processing archive: /Users/gcruz/Desktop/ditto2rc3.tar

Extracting  trunk.tar
ERROR: E_FAIL

[Mark]

The MODx site is not running 0.9.6 nor is it running the demo content. You can get 0.9.6 RC1 from here: http://modxcms.com/beta.html

[mmjaeger]

Great work Mark - thank you.

I'm getting an error when opening the debug window:

Code:

« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »
 
PHP error debug
  Error:  wordwrap() expects parameter 1 to be string, array given   
  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:  172   
  Line 172 source:  $v = wordwrap($v,100,"\r\n",1);   
 
Parser timing
  MySQL:  0.0175 s (21 Requests)
  PHP:  0.1382 s   
  Total:  0.1557 s   

[ZAP]

Wow. Ditto just keeps getting better and better. I need to spend a weekend with it learning all the new tricks...

I just installed 2.0 RC3 and I'm having a very tough time getting the filter parameter to work. It seems that if I add any filter at all (including &filter=`id,999,1` and any number of others I've tried) I get the no documents found text. If I leave the filter parameter out I get results for all the documents in my parent folder.

What might I be doing wrong? I tried to use the debug console but I received a ksort parse error in the popup (with or without the filter param), which may be because this is 0.9.5 RC1. The filter class looks about the same as in previous versions (except for minor changes in syntax - thanks for the honorable mention btw...).

[Mark]

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

Code:

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?

[Mark]

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

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

[Perrine]

Hi there,

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

Code:

[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

[Mark]

Drat, the last fix didn't correct the warning....

Here is the proper change (now in SVN)

Code:

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

[doze]

Very nice Ditto HQ! Good job Mark!

[mmjaeger]

Mark, $stopOnNotice  is set to false - haven't done any changes to the index.php file.

the error still occurs

[Mark]

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

[mmjaeger]

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:

Code:

« 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   

[Mark]

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.

[mmjaeger]

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