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

    I am trying to set up a site with a new host. Have 7 modx sites running fine, but this one only lets me use the manager, but the preview remains a blank page. Helpdesk suggested a db connection was not established, tried Analyzer by CastleCops, which seems to connect. I downloaded MODX again last night, created a new db. Installed MODX with the example website, helas, still a blank page. Was told toinstall phpnuke or Joombla for a test( they come pre-loaded), installed phpnuke, seemed okay.Installed Joomla, that works okay. Only difference is the both Joomla and PHPnuke installed in a subfolder of the root, so: http://www.barassoboys.eu/joomla. Now I will try that with modx but it does not seem very elegant to have www.baraso...eu/modx.

    Any ideas someone?

    Thanks, Frank.

    Error in server log: [Tue Nov 20 10:37:15 2007] [error] [client 84.222.20.144] mod_security: Filtering against POST payload requested but payload is not available [hostname "www.barassoboys.eu"] [uri "/phpnuke/admin.php"]


    env::

    PC XP SP2

    Modx 0.9.6

    Linux srv425.flexwebhosting.nl 2.6.18-ovz028stab035.1-smp #1 SMP Sat Jun 9 12:15:32 MSD 2007 i686
    Virtual Directory Support disabled
    Apache Version Apache/1.3.37 (Unix) PHP/5.2.3 mod_ssl/2.8.28 OpenSSL/0.9.8a mod_perl/1.29 FrontPage/5.0.2.2510

    Active Persistent Links 0
    Active Links 0
    Client API version 4.1.12
    MYSQL_MODULE_TYPE external
    MYSQL_SOCKET /var/lib/mysql/mysql.sock
    MYSQL_INCLUDE -I/usr/include/mysql
    MYSQL_LIBS -L/usr/lib/mysql -lmysqlclient
    Server Version 4.1.12-standard
    Client Version 4.1.12
    Host Information Localhost via UNIX socket
    Protocol Information 10


    Loaded modules: mod_suphp, mod_php5, mod_security, mod_ssl, mod_perl, mod_frontpage, mod_setenvif, mod_so, mod_headers, mod_expires, mod_auth_anon, mod_auth, mod_access, mod_rewrite, mod_alias, mod_userdir, mod_actions, mod_imap, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_info, mod_status, mod_negotiation, mod_mime, mod_log_referer, mod_log_agent, mod_log_config, mod_env, mod_vhost_alias, http_core
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      It can be named anything you want... I’d be inclined to name it whatever language it’s in, that would make it look like it’s in more than one language and impress people more!

      I would also try turning off mod_security in your .htaccess file.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 10076
        • 1,024 Posts
        @ sottwell I am not sure what you mean with
        what language its in
        ?
        Guess you mean to installit eg in www.ba...eu/english ? But impress people more, is not my goal.

        @ganeshXL I was trying to change something in the .htacces file. And currently uploading modx to a folder, probably the reason of those errors.
          • 10076
          • 1,024 Posts
          Quote from: sottwell at Nov 20, 2007, 04:21 AM

          It can be named anything you want... I’d be inclined to name it whatever language it’s in, that would make it look like it’s in more than one language and impress people more!

          I would also try turning off mod_security in your .htaccess file.



          Just installed from a folder: start.
          Changed the htaccess:

          ## START ##
          <IfModule mod_security.c> 
              SecFilterEngine Off 
              SecFilterScanPOST Off
          </IfModule>
          ## END ##
          
          RewriteEngine On
          RewriteBase /start
          
          RewriteCond %{REQUEST_FILENAME} !-f
          RewriteCond %{REQUEST_FILENAME} !-d
          RewriteCond %{REQUEST_URI} !(.*[^/,\.])$
          RewriteRule ^(.*)[/\.,]$ /$1 [L,R=301]
          
          
          RewriteCond %{HTTP_HOST} ^tillda* 
          RewriteRule ^/*(.*)$ http://www.barassoboys.eu/$1 [L,R=301,QSA]
          
          
          RewriteCond %{REQUEST_FILENAME} !-f
          RewriteCond %{REQUEST_FILENAME} !-d
          RewriteRule ^(.*)$ index.php?q=$1 [L,QSA,NC]
          
          
          
          AddType text/x-component .htc
          
          
          
          #php_flag register_globals Off
          
          
          
          # For servers that support output compression, you should pick up a bit of
          # speed but uncommenting the following lines.
          
          #php_flag zlib.output_compression On
          #php_value zlib.output_compression_level 5
          
          
          
          # The following directives stop screen flicker in IE on CSS rollovers. If
          # needed, un-comment the following rules. When they're in place, you may have
          # to do a force-refresh in order to see changes in your designs.
          
          #ExpiresActive On
          #ExpiresByType image/gif A2592000
          #ExpiresByType image/jpeg A2592000
          #ExpiresByType image/png A2592000
          #BrowserMatch "MSIE" brokenvary=1
          #BrowserMatch "Mozilla/4.[0-9]{2}" brokenvary=1
          #BrowserMatch "Opera" !brokenvary
          #SetEnvIf brokenvary 1 force-no-vary


          and still all the same, a blank page.?
            • 7231
            • 4,205 Posts
            May be unrelated, but I had a similar scare after an upgrade. The solution was to go to /install rather than directly to the index.php page. In other words try going to www.domain.com/modx/install/ <-- in this case modx was installed in a directory called modx.

            As I said this may not be your case but it is what I went through. The index.php file should either redirect to the install if necessary or have an error message, the blank screen is scary.

            EDIT: Also adding the above to htaccess to disable modsec does not always work. I found it necessary to disable or edit the modsec rules in order to get modx to work well on occasions. I never had this issue with other CMSs, modx must use some parameter that has been abandoned by others or labled as bad in general modsec filter rules...or modx is more advanced than others.
              [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

              Something is happening here, but you don&#39;t know what it is.
              Do you, Mr. Jones? - [bob dylan]
              • 10076
              • 1,024 Posts
              Well, as the mysql used by host is only just the one needed for 9.6, I installed 9.5 and eureka! It runs.
              As it is a "private" site (small senior football club) I guess it will do fine.

              Thanks all, Frank.
                • 22303 MODX Staff
                • 10,725 Posts
                Quote from: Frank at Nov 20, 2007, 08:11 AM

                Well, as the mysql used by host is only just the one needed for 9.6, I installed 9.5 and eureka! It runs.
                As it is a "private" site (small senior football club) I guess it will do fine.

                Thanks all, Frank.
                Frank, you were installing 0.9.6.1, released just a few days ago, and not 0.9.6 right? There was a very prominent and well-documented error on some server configurations with 0.9.6 that sounds exactly like what you describe. I’d be willing to bet that was the issue.
                  • 10076
                  • 1,024 Posts
                  Hi Jason,

                  you are right, downloaded last night. Just to make sure my local copy was not the issue.
                  Never found that documentation, only a ticket on 9.7 with the "same" issue.
                  http://svn.modxcms.com/trac/tattoo/ticket/47.

                  I´ll try to find the docs, curious to find out what happened,

                  Thanks, Frank.