Thank you kp52 for this, it's great to see such a great resource restored. I only noticed it missing last week when I needed some help. It did leave me wondering whether it was time to give up on Evo and move over to Wordpress or another light CMS.
-
☆ A M B ☆
- 24,524 Posts
I was really sorry to drop Evo altogether, but with my eyes giving me trouble I just don't have the computer time to work with both versions. I had to make a very difficult decision. So I wish the Evo/Clipper community the very best, and hope that my poor efforts over the years will continue to be useful.
"Slowly" I'm copying the documentation to the clippercms site.
Thanks Sottwell for the work done in the past.
Would be great if some coders stood up and continue to build some nice snippets/plugins and improve the cms.
Evolution user, I like the back-end speed and simplicity

-
☆ A M B ☆
- 24,524 Posts
Well, considering the topic, how about
http://sottwell.pogwatch.com/how-plugins-work.html
The Evo API is fully documented here
http://wiki.modxcms.com/index.php/Category:API
There's also a sample plugin here
http://rtfm.modx.com/display/Evo1/Plugins
You might want to take a look at this; it would be easy enough to adapt it to use IP addresses.
http://modx.com/extras/package/pagehitcounter
Oops, sorry Susan, I don't know how I've missed those locations completely while being so close. Thanks for the links.
Quote from: sitecms at Jan 07, 2013, 05:26 PMIt's not quite clear to me. At this moment, is clippercms the same as evo 1.0.7
Not exactly. The evo project is continueing as Clippercms. Modx is only bringing security updates for evo. Clippercms is also adding other core improvements. For new websites, if you ask me, the best is to use Clippercms. I'm not a coder and don't know if plugins might work on both, but I think it would.
Evolution user, I like the back-end speed and simplicity
