We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27408
    • 33 Posts
    For a couple of websites that I maintain I’m doing some research into migrating to Revolution from Evolution. I really like Revolution sofar. Just that a lot of documentation seems to lack some depth in explaining certain aspects of Revolution, in this case using xPDO instead of the old API. Since a lot of my websites have snippets with a lot of calls to the old API in it I would like to know how exactly I can use the full power of Revolution and xPDO. I know that I still can use the old API in Revolution, but I’d like to employ the full opportunities that Revolution would give me.

    What I would like to know is how I can replace the calls to the old API with xPDO in a detailed way. For example what should I replace a db->select() call with? Or what parts ot the old API are still valid in Revolution, and which are only legacy supported? The documentation located here doesn’t really explain in depth how to do this. (Or I’m too tired from reading through all the documentation, thats also a possibility).

    Could someone provided me with some simple examples to build on? And as a second question, are there any plans to expand the existing documentation on using Revolution?




      • 28215
      • 4,149 Posts
      Quote from: Sitethief at Dec 21, 2010, 07:35 AM

      What I would like to know is how I can replace the calls to the old API with xPDO in a detailed way. For example what should I replace a db->select() call with? Or what parts ot the old API are still valid in Revolution, and which are only legacy supported? The documentation located here doesn’t really explain in depth how to do this. (Or I’m too tired from reading through all the documentation, thats also a possibility).
      You should read this: http://rtfm.modx.com/display/xPDO20/Home

      Could someone provided me with some simple examples to build on? And as a second question, are there any plans to expand the existing documentation on using Revolution?
      Sure, look at any of the existing components, such as Quip, tagLister, FormIt, Login, Discuss, Batcher, Peoples, FileLister, getResources, etc. Any of those will show you some good examples of how to use Revo’s API.

      And yes, we plan to much improve the current documentation.





        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 3749
        • 24,544 Posts
          Did I help you? Buy me a beer
          Get my Book: MODX:The Official Guide
          MODX info for everyone: http://bobsguides.com/modx.html
          My MODX Extras
          Bob's Guides is now hosted at A2 MODX Hosting