We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 20725
    • 32 Posts
    Help!.... Help!..... All of my pages are invisible!

    I have a few MODx sites running OK (on 2.0.7), but yesterday I did a 2.0.8. new install for another web site, and the Apache server keeps saying "404 Not Found" for all of my pages in the MySQL DB -- except for my Main page which is visible.

    Clue A) All the invisible pages show properly in "preview" (and everything else seem to be OK).

    Clue B) These versions 2.0.7. and 2.0.8. are on two different servers and at two different hosting companies, so is it possible this invisibility is related to the server and/or the hosting company? One hosting company is trying to tell me the Apache web server software cannot load pages directly from the database because -- they say -- when the content (of let’s say, my sitemap.html document) is in the MySQL database, then some script (of MODx) should retrieve it from the database.

    To my great frustration, there goes another full DAY of my life on this issue. I’ve already tried many things and found:

    #1: The solution is NOT to preview/call the page from the DB using "//mysite.com/index.php?id=2" where id=2 is the doc ID of the resource.

    #2: The solution is NOT to "publish" these documents -- all of them were "published"!

    #3: The solution is NOT to replace an EXTERNAL html page (with an INTERNAL html page in the DB) -- this was already done.

    #4: The solution is NOT to add <base href="[[++site_url]]" /> to the head -- this was already done.

    #5: The solution is NOT to add HTML code like <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> -- this was already done.

    #6: The solution is not to rename my ht.access file. Naturally, if there are "404 Not Found" error messages, then usually there is no redirect, and probably the ht.access probably was never renamed. As expected, all of my pages are redirected to my main page, if ht.access is changed to .htaccess. But this is not a solution.

    #7: The MODx documentation is not an in-depth guide, because it only touches the surface. It’s little or no help at http://rtfm.modx.com/pages/viewpage.action?pageId=18678051

    Help!.... Help!..... All of my pages are INVISIBLE!
      Best regards,
      Mike

      MODx Revolution 2.0.7 and 2.0.8 powered by PHP 5.3.5 / Apache 2.2.17 / MySQL 5.0.7 on Shared hosting
      MS Vista and FF 3.6.15 / Many dot com web sites.
      Timezone: America/New_York
      • 21257 MODX Staff
      • 730 Posts
      You have a much better chance of someone figuring out your problem for you if you post the environment information that the forums recommend.. it could very well be something to do with Apache, but there’s no way to know without more information.
        Mike Schell
        Lead Developer, MODX Cloud
        Email: [email protected]
        GitHub: https://github.com/netProphET/
        Twitter: @mkschell
        • 20725
        • 32 Posts
        Quote from: netProphET at Apr 12, 2011, 02:50 PM

        You have a much better chance of someone figuring out your problem for you if you post the environment information that the forums recommend.. it could very well be something to do with Apache, but there’s no way to know without more information.
        Please see my signature as follows:

        MODx Revolution 2.0.7 and 2.0.8
        Timezone: America/New_York
        My system error log is blank.
        Many dot com web sites.
        MS Vista and FF 3.6.15
        PHP Version 5.3.5
        Shared hosting
        Apache 2.2.17
        MySQL 5.0.7
          Best regards,
          Mike

          MODx Revolution 2.0.7 and 2.0.8 powered by PHP 5.3.5 / Apache 2.2.17 / MySQL 5.0.7 on Shared hosting
          MS Vista and FF 3.6.15 / Many dot com web sites.
          Timezone: America/New_York
          • 21257 MODX Staff
          • 730 Posts
          Sorry I didn’t notice the software versions there, but I was hoping for a little more configuration info to understand your environment.
          Any opcode caching?
          Anything in your apache error log?
          You mention that your MODX error log is empty, but you also said there were errors all over the place trying to get the site going? Any specific error messages could be very helpful.
            Mike Schell
            Lead Developer, MODX Cloud
            Email: [email protected]
            GitHub: https://github.com/netProphET/
            Twitter: @mkschell
            • 27708 MODX Staff
            • 2,502 Posts
            One of the most likely issues is that there was a bad upload or incorrect file permissions on the server. When MODX works in an unexpected way immediately after an install this is often the first thing to do: reupload the files and rerun the installer (upgrade is fine).

            If you have the ability to view the apache logs they may provide additional information to share here. Also as netProphET notes more environment information from your phpinfo() output could help identify some problems.

              Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
              • 20725
              • 32 Posts
              Quote from: netProphET at Apr 12, 2011, 03:05 PM

              Sorry I didn’t notice the software versions there, but I was hoping for a little more configuration info to understand your environment.
              Any opcode caching?
              Anything in your apache error log?
              You mention that your MODX error log is empty, but you also said there were errors all over the place trying to get the site going? Any specific error messages could be very helpful.
              1. Sorry, this ’opcode catching’ stuff is unfamiliar territory to me.

              2. There is nil, zilch in the Apache error log, according to my hosting company. They say it appears to be perfectly normal, at least according to them.

              3. Yes, my MODx error log is (or appears to be) empty.

              4. The "many errors all over the place" was a vague reference to the many-many bugs I’ve come across in the last 30 days. And to the 13 bugs that I submitted (e.g. bug #3655, 3736, .... , 4242). And to the just as many bugs that I should submit as soon as possible. For the benefit of the whole MODx community.

              5. As to the MODx error log. This is one of these bugs I should submit, because it may appear to be empty, but if you (the user) do a little probing or prodding, you might find that most of the time it isn’t. For example, right now mine does have some new and additional error messages/clues (for you and me). Today’s log reads as follows:

              [2011-04-11 21:12:38] (ERROR @ /connectors/element/propertyset.php) Could not cache context settings for mgr.
              [2011-04-12 09:25:50] (ERROR @ /connectors/element/propertyset.php) Error caching lexicon topic lexicon/en/core/default
              [2011-04-12 09:25:50] (ERROR @ /connectors/element/index.php) Error caching lexicon topic lexicon/en/core/element
              [2011-04-12 12:19:51] (ERROR @ /connectors/element/index.php) Error caching lexicon topic lexicon/en/core/default
              [2011-04-12 13:17:23] (ERROR @ /connectors/element/index.php) Could not cache context settings for mgr.
                Best regards,
                Mike

                MODx Revolution 2.0.7 and 2.0.8 powered by PHP 5.3.5 / Apache 2.2.17 / MySQL 5.0.7 on Shared hosting
                MS Vista and FF 3.6.15 / Many dot com web sites.
                Timezone: America/New_York
                • 20725
                • 32 Posts
                Quote from: smashingred at Apr 12, 2011, 03:16 PM

                One of the most likely issues is that there was a bad upload or incorrect file permissions on the server. When MODX works in an unexpected way immediately after an install this is often the first thing to do: reupload the files and rerun the installer (upgrade is fine).

                If you have the ability to view the apache logs they may provide additional information to share here. Also as netProphET notes more environment information from your phpinfo() output could help identify some problems.
                Sorry, smashingred, I should’ve mentioned this in my OP. This would have been #8 in my OP.

                a) My first install on this server/host was uneventful, was completed successfully and went OK, but later I ran into permission issues (e.g. 777 vs. 755) on my folders, and into ’path’ issues because I did the installation without changing the name servers, so I decided to delete all MODx files and re-upload and repeat the installation.

                b) I did the 2nd installation after changing my name servers. My 2nd installation on this server/host was also uneventful, was completed successfully and went OK, but repeatedly I ran into ’path’ issues in connection with trying to install one of the extras known as "simplesearch", so once again I decided to delete all MODx files and re-upload and repeat the installation.

                c) I did the 3rd installation after deleting my MySQL DB. My 3rd installation on this server/host was also uneventful, was completed successfully and went OK, but once again I kept running into ’path’ issues in connection of trying to install "simplesearch", so at this time I decided to keep all my MODx files, and not to re-upload and re-repeat the installation. However, now my pages (in the DB) are invisible!
                  Best regards,
                  Mike

                  MODx Revolution 2.0.7 and 2.0.8 powered by PHP 5.3.5 / Apache 2.2.17 / MySQL 5.0.7 on Shared hosting
                  MS Vista and FF 3.6.15 / Many dot com web sites.
                  Timezone: America/New_York
                  • 27708 MODX Staff
                  • 2,502 Posts
                  Yeah, sounds like you following the right steps unfortunately for you, you seem to be uncovering (and filing issues—thanks). Hopefully someone much more insightful will be able to come up with a possible solution for your issue.

                  I think some additional info from the Reports>System Info w/ the key personal data removed might be helpful for people here.

                  Best of luck and hang in there.
                    Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
                    • 6228
                    • 249 Posts
                    One thing I would recommend NEVER doing is uploading decompressed MODx installation files but rather, upload the single zipped installation file and decompress it on the server. It takes just one corrupt uploaded file to screw up your whole installation, or at minimum make it seem as though Revo has many more bugs than it legitimately does.
                      lo9on.com

                      MODx Evolution/Revolution | Remote Desktop Training | Development
                      • 31037
                      • 358 Posts
                      Latest two weeks I have made well over 10 complete site moves/upgrades on different servers. Often working fine but sometimes with troubles.

                      When I get into trouble, this is what I do, perhaps it could help:

                      When I get blank pages it is always because of some php error caused by "something". Just as it should be if "display error = 0" in php conf.

                      So what I would do first is to be sure I can see a log that catches errors. The Modx error log very often is empty even when there is a php error.

                      When I can read a working error log I can see what the error is, and then pretty easy correct it.

                      The phpinfo should tell where to look for error log. Very often it isn’t any defined. Force a php error and look in the log for it. If nothing there, the log isn’t logging.

                      When I have had problem with upgrades it is usually from one of these sources:

                      * /core/config/config.inc.php:
                      When upgrading sometimes some of the path becomes incorrect.
                      First thingh I check is line 57: $http_host=’yoursite.something.com’;

                      * Rewrite (FURL) is on in Modx config but not on server.

                      * File permissions
                      Modx and ftp is not running as same user or group. Can (will) cause all kind of errors, like not being able to install addons.

                      * Something missing in the enviroment that should be there.

                      * By misstake I copied files that I shouldn’t copy, like config.inc.php, after I made the complete install.

                      How I solve it:

                      I make sure to read a log that catches errors, like I started this message.

                      If not working, I do:

                      Make a clean install, add a few pages and check everything is working.

                      Install the addons from within Modx package manager instead of transfering components dir from old install.

                      When still working I copy my assets folder onto the server.

                      I then add a few tables from my old install, like site_contents, and the tables for chunks, template vars, site templates and perhaps snippets.

                      If everything still works I import all tables except site_config.

                      When I do it in parts like this I can see when it goes wrong and then it is easy to find the problem.

                      So far it has never been an error that I can blame Modx for.

                      (I do blame Modx for forcing me to install Modx on many VPSs to find one that can cope with the soon to be solved heavy caching load wink )

                      I think Modx is extremely stable and works fine in many different enviroments.

                      Btw, two things I *never* do:
                      1. Trust anything a hosting company says. Never.
                      2. Start blaming the scripts I’m installing. As most people get the scripts to work without problems it would make me look like a fool shouting about bugs, I know it is almost always me doing something wrong.