We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 19257
    • 141 Posts
    Hey all! I’m sure this is a very common issue, I don’t mean to re-post if it’s already been solved, but I didn’t see the exact situation I have.

    Theres one site in which I’m using a local provider of hosting space and for years their servers have been anything but reliable. Ever since I installed MODx on this one server, I can’t seem to be able to add any new snippets, chunks, or edit existing ones. Whenever I press "save" on the "new snippet" or "new chunk" screen, it takes me to a 404 error page.

    This only happens when I try to add new snippers, chunks or whenever I add javascript to a template. Funny thing is that it doesn’t happen when I add a new template or edit an existing one.

    In case this has anything to do with it, I’m using Firefox 2.0.0.12 undecided

    I’ve modified the permissions of every related folder inside of /assets with a permission of 777. This is something I haven’t been able to get around, please if anyone has any advice I’d greatly appreciate it!

    Blessings,

    Josh grin
      • 19257
      • 141 Posts
      Quote from: ganeshXL at Mar 06, 2008, 03:52 PM

      Are you using "SEO-friendly URLs"? Check your configuration inside the manager.

      Check also if you have an .htaccess file in your site’s top directory and also in the manager directory. It sounds a bit like URL-rewriting is not set up correctly. e.g. you should not use mod_rewrite inside the manager-folder.

      Also, 404 errors have nothing to do with Javascript; your server simply tells you that you have requested a file which isn’t there.

      If the mod_rewrite problem can be ruled out, upload all modx-docs again. Maybe some stuff got corrupted during the FTP-upload.

      Hey thanks for the quick reply!

      I am using SEO-friendly URLs.

      This is what the .htaccess file looks like in the root install of MODx:

      # MODx supports Friendly URLs via this .htaccess file. You must serve web
      # pages via Apache with mod_rewrite to use this functionality, and you must
      # change the file name from ht.access to .htaccess.
      #
      # Make sure RewriteBase points to the directory where you installed MODx.
      # E.g., "/modx" if your installation is in a "modx" subdirectory. If you have
      # problems with your .htaccess working at all, try un-commenting the first 
      # line above the "RewriteEngine On" directive.
      #
      # You may choose to make your URLs non-case-sensitive by adding a NC directive
      # to your rule: RewriteRule ^(.*)$ index.php?q=$1 [L,QSA,NC]
      
      #Options +FollowSymlinks
      RewriteEngine On
      RewriteBase /
      
      
      
      # Rewrite www.domain.com -> domain.com -- used with SEO Strict URLs plugin
      #RewriteCond %{HTTP_HOST} .
      #RewriteCond %{HTTP_HOST} !^example-domain-please-change\.com [NC]
      #RewriteRule (.*) http://example-domain-please-change.com/$1 [R=301,L]
      #
      # or for the opposite domain.com -> www.domain.com use the following
      # >>> DO NOT USE BOTH THE ABOVE AND BELOW <<<
      #
      #RewriteCond %{HTTP_HOST} .
      #RewriteCond %{HTTP_HOST} !^www\.example-domain-please-change\.com [NC]
      #RewriteRule (.*) http://www.example-domain-please-change.com/$1 [R=301,L]
      
      
      
      # Rewrite secure requests properly to prevent SSL cert warnings, e.g. prevent 
      # https://www.domain.com when your cert only allows https://secure.domain.com
      #RewriteCond %{SERVER_PORT} !^443
      #RewriteRule (.*) https://example-domain-please-change.com.com/$1 [R=301,L]
      
      
      
      # The Friendly URLs part
      RewriteCond %{REQUEST_FILENAME} !-f
      RewriteCond %{REQUEST_FILENAME} !-d
      RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
      
      
      
      # Make sure .htc files are served with the proper MIME type, which is critical # for XP SP2. Un-comment if your host allows htaccess MIME type overrides.
      
      #AddType text/x-component .htc
      
      
      
      # If your server is not already configured as such, the following directive
      # should be uncommented in order to set PHP's register_globals option to OFF.
      # This closes a major security hole that is abused by most XSS (cross-site
      # scripting) attacks. For more information: http://php.net/register_globals
      #
      # To verify that this option has been set to OFF, open the Manager and choose
      # Reports -> System Info and then click the phpinfo() link. Do a Find on Page
      # for "register_globals". The Local Value should be OFF. If the Master Value
      # is OFF then you do not need this directive here.
      #
      # IF REGISTER_GLOBALS DIRECTIVE CAUSES 500 INTERNAL SERVER ERRORS :
      #
      # Your server does not allow PHP directives to be set via .htaccess. In that
      # case you must make this change in your php.ini file instead. If you are
      # using a commercial web host, contact the administrators for assistance in
      # doing this. Not all servers allow local php.ini files, and they should
      # include all PHP configurations (not just this one), or you will effectively
      # reset everything to PHP defaults. Consult www.php.net for more detailed
      # information about setting PHP directives.
      
      #php_flag register_globals Off
      
      
      
      # For servers that support output compression, you should pick up a bit of
      # speed but un-commenting 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


      Can you expand what you said about mod_rewrite? I’m kind of clueless. undecided
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        The line
        RewriteEngine On

        turns the mod_rewrite feature of the Apache server on. You don’t want the index.php file in the Manager to be rewritten, so there is another ht.access file in the /manager folder that needs to be renamed to .htaccess. It contains one line),
        RewriteEngine Off


        You also might want to try uncommenting the line above that in the main .htaccess file (remove the # from the beginning of the line:
        Options +FollowSymlinks

        Some servers need it, some don’t, but it doesn’t hurt anything in any case.
          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
          • 19257
          • 141 Posts
          Thanks Susan. You are a blessing to this forum!

          Josh
            • 19257
            • 141 Posts
            Thanks again for your advice, I upgraded MODx with the latest release, no problems with the upload, and that seemed to fix a problem I had with TinyMCE.

            I also changed the .htaccess file in my "manager" folder so it could look like this:
            Options +FollowSymlinks
            RewriteEngine Off
            RewriteBase /


            But I still get a 404 error page, and now I get it when trying to make a new template! embarrassed

            I can edit chunks/snippets though undecided