We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

front-end not works after upgrade revo 2.0.6 to the latest (modx-2.2.14-pl)

  • modx.customize Reply #1, 9 years, 10 months ago
    Hi everyone

    modx rocks and people who initially selected this cms for their websites decide to stay with this very cms - hopefully forever ;-)

    So, once used revo 2.0.6 and build in a few templates + content people may notice their core is old.

    I have downloaded one website of those and upgraded to modx revo 2.2.14 (big jump rather then doing it version by version - but I have confirmed it here on Russian thread for upgrade issues 
    http://modx.im/blog/docs/592.html#comment21280
    ):

    - overwritten the files
    - launched the setup/ which has finished successfully

    all was fine on my ubuntu server @ laptop but on live site the only manager works


    the error log is attached, most of the issues is connected to the : 
    Resource URI  already exists for resource id = XXX; skipping duplicate resource URI for resource id = YYY


    when I have disabled the friendly urls this problem stopped to occur. I was happy thinking it would be good at least for temporary resolution but the front end still did not come up live - so still the blank page viewed on front-end

    * I have just discovered (also reported in the same thread 
    http://modx.im/blog/docs/592.html#comment21315
    ) that page dies on the very last line of index.php with 
    $modx->handleRequest();


    Please please help - one of the internet sites is down since june 18th 2014 + it's on modx cms revolution :-(
      modx and ecommerce pro
      • 3749
      • 24,544 Posts
      BobRay Reply #2, 9 years, 10 months ago
      I've seen this before. More recent versions of MODX need the uri field of each Resource to be filled in. It happens when you save the resource (and is supposed to happen when you upgrade, but sometimes it doesn't).

      Try editing and saving the Home page and see if it then shows up in the front end.

      If that works, this utility snippet should fix all of them. Crete a page called UriFix with this content:

      [[!UriFix]]


      Then create a snippet called UriFix with this code:

      <?php
$docs = $modx->getCollection('modResource');
foreach ($docs as $doc) {
    $doc->save();
}
return 'Finished!';


      View the UriFix resource, then clear the cache. See if that fixes things. If it does, you can delete the resource and the snippet.
        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
      • modx.customize Reply #3, 9 years, 10 months ago
        Thanks Bob!

        I have followed the instructions and this snip has added the alias I think to all of the resources. However the page with templates did not load so I have figured it out that it's some snippet could not work that was used on html integration.

          modx and ecommerce pro
        • modx.customize Reply #4, 9 years, 10 months ago
          Finally, having found out that wayfinder did not work properly and having update it - the template got parsed successfully
            modx and ecommerce pro
          • modx.customize Reply #5, 9 years, 10 months ago
            Have also applied back the enable FURLS and all pages work again, thanks Bob.

            *Have updated the initial thread for Russian users if anyone get into the same problem http://modx.im/blog/docs/592.html#comment21388
              modx and ecommerce pro
              • 3749
              • 24,544 Posts
              BobRay Reply #6, 9 years, 10 months ago
              I glad you got it sorted. Thanks for reporting back. smiley
                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
                • 40045
                • 534 Posts
                exside Reply #7, 9 years, 10 months ago
                you can also just go to system settings and disable FURLs, then enable them again, this triggers the method refereshUris() for all resources and basically does what Bobs utility snippet does =)!
                  • 3749
                  • 24,544 Posts
                  BobRay Reply #8, 9 years, 10 months ago
                  Quote from: exside at Jun 21, 2014, 04:47 PM
                  you can also just go to system settings and disable FURLs, then enable them again, this triggers the method refereshUris() for all resources and basically does what Bobs utility snippet does =)!

                  Good to know. wink
                    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
                  • modx.customize Reply #9, 9 years, 9 months ago
                    Quote from: exside at Jun 21, 2014, 04:47 PM
                    you can also just go to system settings and disable FURLs, then enable them again, this triggers the method refereshUris() for all resources and basically does what Bobs utility snippet does =)!

                    Upgrading another 2.0.7 to 2.2.14 and this issue raised again just like on the previous site ;-) But having disabled FURLs the clear cache is processed with no error - great!

                    I could not even use Bob's fix because I can't edit any resource ((

                    I was hoping that having fixed the errors connected to FURLs & disabled WISIWIG editor the Update resource functions will work - but still blank page ((

                    So when manager clicks to update any resource the page with URL like http://localhost/newupdate207to2214.com/manager/?a=30&id=115 is blank while the quick update content is OK ;-)

                    Can anyone suggest a way to fix this or to find an issue, please?

                      modx and ecommerce pro
                    • modx.customize Reply #10, 9 years, 9 months ago
                      oh I think I was wrong
                      & disabled WISIWIG editor
                      in fact I have disabled just 
                      which_editor
                      (from tinyMCE to NONE) and once I have disabled 
                      use_editor
                      from YES to NO the update page URL works.. with some issues ;-) as follows:

                      Most of the pages are ok to be UPDATED but some certain resources fail to load content field data from db.

                      Attached is an example for resource id 199: db data has content but on the backend update field per this resource - it's empty
                        modx and ecommerce pro