We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3749
    • 24,544 Posts
    That's very weird. You should get a file called gorevo-1.2.0-pl.transport.zip in the download. Is it possibly that your browser is unzipping it automatically?

      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
      • 10165
      • 129 Posts
      Hi BobRay, thanks for the reply - I've now re-installed using the correct transport ( I used Firefox instead and specified download format this time )
      Re-created the evo.zip (without the huge assets folder which I've moved in manually) which seemed to work OK and show the final completed screen.

      Now after putting the evo.zip in place in the revolution site (installed in the root and working with just the home page), when I run the terminal command I'm getting the following:

      php /Applications/MAMP/htdocs/gorevo/evo.zip
      
      Parse error: parse error in /Applications/MAMP/htdocs/gorevo/evo.zip on line 1272
      


      Any ideas?

      I'm hoping I don't need to start rebuilding the whole site from scratch in revolution, obviously I'd rather not do that if GoRevo can save me a good bit of time rewriting a lot of it. This is the first time I've actually tried to use it although I bought it some time ago in readiness for this project.

      Many thanks
        • 10165
        • 129 Posts
        Hi BobRay, I just thought I'd give it a try using the browser option (as I couldn't seem to get terminal option working).

        It spat out a long list of errors in the browser window referring to users --- [GoRevo] Could not save user ........ --- and duplicate entries etc. but appeared to finish, or at least stop loading.

        At this point I appear to have all the resources added but no elements at all, (no templates, snippets, chunks)

        Could that simply be down to it being such a big site and the browser method not being suitable?

        thanks
          • 3749
          • 24,544 Posts
          It's possible. Did the Evo export or the Revo import take more than 30 seconds?
          That would suggest that it timed out.

          You may also be running out of memory, though, if the site is very big.

          Before you abandon the browser, see if you can increase the max_execution time. You can put this in your php.ini file:

          max_execution_time = 120


          You may also be able to increase the PHP memory limit.
            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
            • 10165
            • 129 Posts
            Hi BobRay,

            I already had my php.ini set to the following see below bottom - the evolution gorevo seemed to complete although took several minutes - the Revolution side didn't complete properly (i.e. I didn't see a completed screen if that's what was supposed to happen, it simply stopped loading/progress) would you suggest re-doing it all on even higher max_execution_time?


            edit - I just looked at the php log and even though I've edited php.ini in Mamp it still shows:
            [21-Jan-2018 12:32:27 Europe/Berlin] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /Applications/MAMP/htdocs/core/xpdo/om/xpdoobject.class.php on line 1030

            I've just re-imported the fresh Revolution and installed the package again but noticed even though it says successfully installed it gives the following errors:

            Error 23000 executing statement: INSERT INTO `modx_access_policies` (`name`, `description`, `parent`, `template`, `class`, `data`, `lexicon`) VALUES ('ManagerUserPolicy', 'Policy for imported Manager Users from Evolution', 0, 1, '', '{\"change_profile\":true,\"class_map\":true,\"countries\":true,\"edit_document\":true,\"frames\":true,\"help\":true,\"home\":true,\"load\":true,\"list\":true,\"logout\":true,\"menu_reports\":true,\"menu_site\":true,\"menu_support\":true,\"menu_tools\":true,\"menu_user\":true,\"resource_duplicate\":true,\"resource_tree\":true,\"save_document\":true,\"source_view\":true,\"tree_show_resource_ids\":true,\"view\":true,\"view_document\":true,\"view_template\":true,\"new_document\":true,\"delete_document\":true}', 'permissions') Array ( [0] => 23000 [1] => 1062 [2] => Duplicate entry 'ManagerUserPolicy' for key 'name' ) 
            Error 23000 executing statement: INSERT INTO `modx_user_group_roles` (`name`, `description`, `authority`) VALUES ('ManagerUserRole', 'Role for imported Manager Users from Evolution', 15) Array ( [0] => 23000 [1] => 1062 [2] => Duplicate entry 'ManagerUserRole' for key 'name' ) 
            Error 23000 executing statement: INSERT INTO `modx_access_policies` (`name`, `description`, `parent`, `template`, `class`, `data`, `lexicon`) VALUES ('WebUserPolicy', 'Policy for imported Web Users from Evolution', 0, 1, '', '{\"change_profile\":true,\"class_map\":true,\"countries\":true,\"edit_document\":true,\"frames\":true,\"help\":true,\"home\":true,\"load\":true,\"list\":true,\"logout\":true,\"menu_reports\":true,\"menu_site\":true,\"menu_support\":true,\"menu_tools\":true,\"menu_user\":true,\"resource_duplicate\":true,\"resource_tree\":true,\"save_document\":true,\"source_view\":true,\"tree_show_resource_ids\":true,\"view\":true,\"view_document\":true,\"view_template\":true,\"new_document\":true,\"delete_document\":true}', 'permissions') Array ( [0] => 23000 [1] => 1062 [2] => Duplicate entry 'WebUserPolicy' for key 'name' ) 
            Error 23000 executing statement: INSERT INTO `modx_user_group_roles` (`name`, `description`, `authority`) VALUES ('WebUserRole', 'Role for imported Web Users from Evolution', 15) Array ( [0] => 23000 [1] => 1062 [2] => Duplicate entry 'WebUserRole' for key 'name' ) 
            Successfully installed package gorevo-1.2.0-pl
            


            ;;;;;;;;;;;;;;;;;;;
            ; Resource Limits ;
            ;;;;;;;;;;;;;;;;;;;
            
            max_execution_time = 3500     ; Maximum execution time of each script, in seconds
            max_input_time = 60	; Maximum amount of time each script may spend parsing request data
            memory_limit = 256M      ; Maximum amount of memory a script may consume (8MB)
            



            Quote from: BobRay at Jan 20, 2018, 12:03 PM
            It's possible. Did the Evo export or the Revo import take more than 30 seconds?
            That would suggest that it timed out.

            You may also be running out of memory, though, if the site is very big.

            Before you abandon the browser, see if you can increase the max_execution time. You can put this in your php.ini file:

            max_execution_time = 120


            You may also be able to increase the PHP memory limit.
            [ed. note: freshwaterwest last edited this post 8 years, 8 months ago.]
              • 3749
              • 24,544 Posts
              The DB errors suggest that you didn't empty the DB tables before the import. I don't think those duplicate entry errors would cause a problem because the new values should be the same as the old ones. However, it will cause trouble if there are extra MODX elements (resources, users, etc.) in there. You need to empty/truncate (but not remove) all the tables when doing a "clean" install of MODX (which is what GoRevo requires).

              See this on the MAMP memory limit: https://stackoverflow.com/questions/25996782/cant-increase-mamp-php-memory-limit

              If you go to Reports->System Info and click on the phpinfo() link, you can see the real max_execution_time value.

              You can also search that page for php.info and find the location of the real php.ini file ("Loaded Configuration File"). Try editing the values there.

              BTW, if you can run the GoRevo import from the command line (path/to/php.exe path/to/gorevo/index.php) or create a cron job to run it, that will bypass the time limit completely (though not the memory limit). [ed. note: BobRay last edited this post 8 years, 8 months ago.]
                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
                • 10165
                • 129 Posts
                Hi BobRay,
                thanks again for your comments - just a quick one as well as trying all the other things - I'm not over-confident in Terminal but do use it for large DB actions etc. when I need to - when you say "path/to/php.exe" I've just been using:
                "php /Applications/MAMP/htdocs/gorevo/index.php"

                is there another way I should be doing it - i.e. the path to php execute?

                many thanks
                  • 3749
                  • 24,544 Posts
                  I don't use MAMP (I use XAMPP, which MODX users seem to have fewer problems with), but that looks right to me, assuming that your MODX install is not in a subdirectory.

                  What I actually use for stuff like that is PhpStorm, where I can load that index.php file into the editor and tell PhpStorm to run it (after setting up the server to use and the path to php.exe). It's the equivalent of running it from the command line, but with debugging capability and great navigation through related code files. For example, if I see a $modx->getObject() call in my code, I can put the cursor on getObject() and press Ctrl-B. In a flash, PhpStorm will load the MODX file containing with that function and navigate to the function. I can set a breakpoint in that function and then run in debug mode to step through the function and see the variable values as it executes the code line by line.

                  I have the entire local MODX install as a project in PhpStorm, which is really handy for debugging and searching and viewing the MODX source code. PhpStorm will use more memory, but I have 16 Gigabytes of memory on my machine.
                    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