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
    Yes, and latin1/latin1_swedish_ci are the defaults in Php.
      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
      • 43957
      • 79 Posts
      I have a very similar issue to this since copying my site to local host. I initially reported in this thread https://forums.modx.com/thread/?thread=80552&page=3, but I found this one is directly relevant to the problem so have moved over here, hope that's ok.

      As I reported on the other thread. Package Manager just sits there trying to load the grid. It is fine on page one, but if I click to page two is doesn't load, I have <30 packages installed. Tried clearing the cache manually and browser cache and disabling auto_check_pkg_updates. If I set view to show one per page I can click through and the grid loads for many packages, until I get to 'Login', then won't load the next view. I've not pinned down exactly what package this is, but if I also go to the last page and click back it show "wayfinder" and then get stuck again at some point with packages starting with M, N or R.



        • 43957
        • 79 Posts
        I have now gone through the database and narrowed it down to all of these packages:
        mobiledetection-2.1.0-pl
        modmailchimp-1.0.6-pl
        montwitter-1.0-beta1
        newspublisher-1.4.2-pl
        revossl-1.0.3-pl

        I deleted the database entries in modx_transport_packages. I then went back and searched locally for packages and it listed them to install. I installed them again, but montwitter hung the grid again, so I remove that one and it all loads properly now. A bit of a pain as I am using montwitter and if the package is there the grid will not load. :-(

        If I debug with Chrome I get the following error in the console when it tries to load the grid with montwitter:

        Uncaught SyntaxError: Unexpected token < ext-all.js:7
        Ext.util.JSON.doDecode ext-all.js:7
        (anonymous function) ext-all.js:7
        Ext.extend.onStoreException modx.grid.js:114
        h.Event.fire ext-all.js:7
        h.Observable.fireEvent ext-all.js:7
        (anonymous function) ext-all.js:7
        h.Event.fire ext-all.js:7
        h.Observable.fireEvent ext-all.js:7
        Ext.extend.onRead ext-all.js:7
        (anonymous function) ext-all.js:7
        Ext.extend.handleResponse ext-all.js:7
        f ext-base.js:7
        m ext-base.js:7
        (anonymous function) ext-base.js:7

        Any ideas as to how to fix this one? or if there is a better work-around.

        Many thanks.
        [ed. note: dave-b last edited this post 13 years, 3 months ago.]
          • 3749
          • 24,544 Posts
          As you probably know, monTwitter is from Nov. 2010. It's Version 1.0.0-beta and was never updated. I couldn't find any GitHub repo for it so there's no way to know what its build code looks like.

          Unless the author chimes in, you're best bet is to look at that record in the modx_transport_packages table in the DB and try to see how it's different from the rest. See if the signature has the right form and if the case of the signature and source match that of the transport file.
            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
            • 43957
            • 79 Posts
            I've just run into this problem again. I copied my live 2.2.8pl site to local host.

            I went through all the Setup process and everything seems fine apart from Package Manager hanging on some packages. These are:

            mobiledetection
            modMailchimp
            NewsPublisher

            Very odd.

            I fixed it again by manually removing the transport packages from the database and then reinstalling. [ed. note: dave-b last edited this post 12 years, 1 month ago.]