We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 38004
    • 96 Posts
    I tested out articles, and copied some posts that I had already created to the articles container.

    These posts are still in the system somewhere, but do not showup in articles or in the resource tree.

    How can I restore these?

    Secondly how do I completely remove articles? It's failing on being unable to locate Quip. Probably because I removed the old version that articles was using and installed the newest version.
      • 42562
      • 1,145 Posts
      How did you copy these posts to Articles? Dragged and dropped?
        TinymceWrapper: Complete back/frontend content solution.
        Harden your MODX site by passwording your three main folders: core, manager, connectors and renaming your assets (thank me later!)
        5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
        • 38004
        • 96 Posts
        I set Articles as their container from within each of the posts.
          • 42562
          • 1,145 Posts
          Okay...they are not going to be visible any longer because by default Articles hides all its children in the Resource Tree. And since you did not create these resources with Articles, or import them properly into Articles they are not true Articles resources; that's the reason you can't see them even when you open the Articles Container.

          If you knew their id number you could manually edit them, in order to change their parent.
          yoursite.com/manager/?a=30&id=378


          Or, what I do: install the Addon called batcher, this would certainly save your life now or someday.
          Batch can view all resources no matter where, even if they hide in hell.

          Go to the top menu in Manager / Components / Batcher .... look for all the lost / hidden resources; tick them, right-click, change parent.

          [ed. note: donshakespeare last edited this post 13 years, 5 months ago.]
            TinymceWrapper: Complete back/frontend content solution.
            Harden your MODX site by passwording your three main folders: core, manager, connectors and renaming your assets (thank me later!)
            5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
            • 3749
            • 24,544 Posts
            You could also (and probably should) go into the modx_site_content table PhpMyAdmin. Sort by class_key. That should bring them to the top. For all of them, change the class_key to modDocument and the show_in_tree field to 1.

            Or, this utility snippet might do it:


            <?php
            /* UnArticle Snippet */
            $count = 0;
            $docs = $modx->getCollection('modResource', array('class_key' => 'Article'));
            
            foreach ($docs as  $doc) {
            
                $doc->set('class_key', 'modDocument');
                $doc->set('show_in_tree', 1);
                if ($doc->save()) {
                  $count++;
                }
            
            return 'Modified ' . $count . ' Articles';
            }
              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
              • 38004
              • 96 Posts
              Thanks.

              I decided that Articles is more trouble than it's worth. I've restored an old backup instead.
                • 38290
                • 712 Posts
                Quote from: x0149128 at May 01, 2013, 03:24 PM
                Thanks.

                I decided that Articles is more trouble than it's worth. I've restored an old backup instead.

                Definitely has drawbacks and short comings. I've worked on addressing a few things, like making Articles less obsessed with clearing the cache in a recent pull requests that is awaiting approval.

                If there are any particular complaints or additional feedback you have, I'd love to take them into account.
                  jpdevries