We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 49277
    • 7 Posts
    Hi,

    My site (using MODX Revolution 2.2.14) has 2 contexts, an English version and a Japanese version. We make use of the articles (v1.7.8) plugin. An issue we have is the Japanese articles container list is blank, making it difficult to access/modify the articles. I have found that setting the "Per Page" to 1 and then scrolling through the pages shows each article in turn until I get to the 2nd and 4th article (of 4) these article never display in the list.

    Investigating this a bit further it appears some Japanese characters in each article cause this issue, deleting the line in question brings the article back in the list. In one of the articles I discovered "お客" (no quotes) causes the issue, even placing a space between them prevents this issue. I haven't fully narrowed down the problem in the other article but it's a different character string that's causing the issue.

    I've tried placing the problem Japanese characters in an English article but this doesn't reproduce the problem, putting it in one of the ok Japanese articles causes the problem so there's something it's not liking for some reason.

    So far we've tried upgrading the articles plugin from 1.7.6 to 1.7.8 but this hasn't resolved it. (we have another test server which doesn't have this issue but had 1.7.8 installed). Has anyone any suggestions about how to resolve this?

    I have found this thread https://forums.modx.com/thread/?thread=79683&page=3 although it's an old thread and some of the suggestions reference links which are now broken so I thought it best to kick off a new thread.

    Thanks.
      • 49277
      • 7 Posts
      As soon as I post I find a partial solution from https://forums.modx.com/thread/?thread=79683&page=3

      You've probably tried some of these, but:

      1. Turn off the compress_js and compress_css System Settings.
      2. Log out.
      3. In PhpMyAdmin (via cPanel), repair all tables in the DB
      4. Delete all files in the core/cache directory.
      5. Clear your browser cache and cookies.
      6. Run Setup in upgrade mode.

      I just did 1. and it appears to have resolved the problem for one of the articles, meaning there's now only one affected article, clearing the cache (via Site -> Clear Cache) didn't help. I'm also concerned about the affect disabling compress_js and compress_css will have on the performance of the site, any comments on this?
        • 25429
        • 32 Posts
        I have noticed that saving a new article as Published makes te Manager unable to load the articles list. Also, changing an article's status to Published in a list that contains only unpublished articles produces the same problem. If I edit the database manually, I am able to unpublish and then republish a resource, so that it shows up in the list and is editable. However, a new articles breaks the list again.

        MODX Revolution 2.3.3
        Articles 1.7.10

        Any ideas?
          • 3749
          • 24,544 Posts
          I've never noticed any significant performance effect from turning off the compress_ System Settings. I always leave them off.
            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
            • 25429
            • 32 Posts
            @BobRay

            This might have something to do with publishing dates. My site runs on Apache 2.4 on Windows Server 8 (Revo 2.3.3, Articles 1.7.10). The publishing date generated in the database (PHP 5.6.1, MySql 5.0.11) seems to cause Articles not to display the list of articles in the Manager.

            This date string was created in my development environment (Linux) and works with Articles: 1409039100

            This was created in my new production environment (specified above) and it throws the glitch: 1428993601

            If I replace the non-working string with the good one, or simply remove it, things are fixed until I need to unpublish the resource, or publish another.

            Any ideas?
              • 3749
              • 24,544 Posts
              Certain of the format tokens used by strftime() don't work on some Windows servers. MODX sometimes displays the dates in human-readable form with strftime(), then converts them back to a timestamp with strtotime(), so it's possible that something is getting mangled in the process.

              I think it's more likely, though, that you have a mismatch on the Windows server between the MODX, MySQL, and/or PHP date/timezone settings. You can check them manually, or SiteCheck will do it for you (plus a lot of other stuff).
                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