We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 38290
    • 712 Posts
    Is the ArticlesPlugin in your elements tree and active?
      jpdevries
      • 40088
      • 708 Posts
      Yes it is.
        Todd
      • discuss.answer
        • 40088
        • 708 Posts
        After an SQL dump and deleting the entire MODX installation and reinstalling the Articles posts are back and everything seems ok so far. Now to do it all over again on the live server. What a PITA.

        Thanks to all for the suggestions.
          Todd
          • 38290
          • 712 Posts
          Sounds like missing files, incorrect permissions or possibly something in the db. I wonder if Bob Ray's site checker would have spotted anything
            jpdevries
            • 45742
            • 10 Posts
            I have a similar (same?) problem on a fresh install. Selecting the “Articles” Container throws errors on the javascript console:
            [Error] SyntaxError: Unexpected token '<'
            	doDecode (ext-all.js, line 21)
            	(anonyme Funktion) (ext-all.js, line 21)
            	onStoreException (modx.grid.js, line 114)
            	fire (ext-all.js, line 21)
            	fireEvent (ext-all.js, line 21)
            	(anonyme Funktion) (ext-all.js, line 21)
            	fire (ext-all.js, line 21)
            	fireEvent (ext-all.js, line 21)
            	onRead (ext-all.js, line 21)
            	(anonyme Funktion) (ext-all.js, line 21)
            	handleResponse (ext-all.js, line 21)
            	f (ext-base.js, line 21)
            	m (ext-base.js, line 21)
            	(anonyme Funktion) (ext-base.js, line 21)


            Updating the articles’ grid, e.g., select “Unpublished”, leads to a never-ending “Loading”. Writing new articles works, however, I had to manually check this in the database.

            CSS and JavaScript compression is turned off in the manager context.

              • 38290
              • 712 Posts
              Been trying to reproduce this but haven't been able to even with compression turned on.

              ox6a6e, can you confirm these packages are installed:
                jpdevries
                • 45742
                • 10 Posts
                Confirmed – and i found the, well, reason.

                How to reproduce: remove “config.core.php” in the parent directory of “assets”.

                Articles puts .php-files into the “assets” directory. As there is no common gateway to find the core, they try to include “config.core.php” from outside the “assets” directory. There’s none in my installation.

                I'm not sure what to do about it: is it a bug in articles (quip, …?) or a design issue in modx?
                  • 38290
                  • 712 Posts
                  I'm sorry I don't understand you are saying to reproduce the issue remove the root MODX config.core.php file? Articles does not add a config.core.php to assets or elsewhere, that file is needed for the MODX core.
                    jpdevries
                    • 45742
                    • 10 Posts
                    In order to avoid a modx finger print, I integrated the root config.core.php into the index.php (plus renaming and moving around the root directories). Probably, I can achieve the same goal with .htaccess rewriting.

                    Technically, I'm free to put the assets directory anywhere. The “hardening MODX” documentation even suggests moving it to another server — possibly without PHP.

                    The manager and connectors directories are somehow self-contained: both have a separate config.core.php, can be moved to arbitrary directories/URLs. Assets isn't and extras rely on a config.core.php in “assets/..“.
                      • 45742
                      • 10 Posts
                      I put config.core.php back in and changed “.htaccess” to
                      […]
                      # The Friendly URLs part
                      RewriteCond %{REQUEST_URI} /config.core.php$ [OR]
                      RewriteCond %{REQUEST_FILENAME} !-f
                      RewriteCond %{REQUEST_FILENAME} !-d
                      RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
                      [...]

                      Hence, “config.core.php” is treated like a non-existing file.

                      If there’s interest, I’d like to help to get “assets/” somehow self-contained. In case, I’m quite new to MODX, so, how should I start: open a thread in “Revo Development”, e.g. “.php-files in ‘assets’ directory”? [ed. note: ox6a6e last edited this post 12 years, 10 months ago.]