We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 13993
    • 100 Posts
    I just upgraded. Now I can no longer use my subdomain.

    modxcms.domain.com redirects to domain.com/modxcms

    It happens on the front end and the manager and also the urls in the site are being written that way.
      • 33372
      • 1,611 Posts
      This may have to do with a minor change to the .htaccess file. It now uses a RewriteBase directive before the RewriteRule lines. If you can’t get it to work right with your subdomain, try going back to the previous .htaccess file and see if that fixes it.
        "Things are not what they appear to be; nor are they otherwise." - Buddha

        "Well, gee, Buddha - that wasn't very helpful..." - ZAP

        Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
        • 13993
        • 100 Posts
        OK I now can use modx.domain.com but the urls being written in the content say www.domain.com/modxcms

        Sounds like on install the www.domain.com/modxcms got written as the url to use. Is this store in the DB somewhere?
          • 22303 MODX Staff
          • 10,725 Posts
          Quote from: JeremyL at Sep 26, 2006, 08:26 PM

          OK I now can use modx.domain.com but the urls being written in the content say www.domain.com/modxcms

          Sounds like on install the www.domain.com/modxcms got written as the url to use. Is this store in the DB somewhere?
          It’s determined by the server configuration. Whatever PHP is reporting under $_SERVER[’HTTP_HOST’] is gonna determine your domain. Sounds like a misconfiguration of the web server in relation to PHP when setting up subdomains.

          If you want to change it, set the base_path, base_url and site_url before the auto-configuration code in config.inc.php
            • 13993
            • 100 Posts
            Nothing was wrong with $_SERVER[’HTTP_HOST’]. Not sure what was going on, but I did a change of front end template site wide and it fixed the issue. I had deleted the cache but maybe that didn’t take. not sure what the issue was but it seems fixed now.

            Must have been stored somewhere for a short time in cache when the htaccess was causing the other issue.
              • 13993
              • 100 Posts
              On Page /manager/index.php?a=76 (Manage resources page) there is a link not being parsed. This is in the source "/manager/media/style/.$theme./images/_tx_.gif"

              I’m actually seeing a number of broken images, but the others I can’t find errors in source. See the image I attached. The class="sectionHeader" seems to be the issue. I tried to re upload all styles in the manager and still no go.

              Theres a great firefox plugin out there to help find the broken images that aren’t obvious. http://chrispederick.com/work/webdeveloper/

              it has a drop down to see all broken images on all pages in all the frame.
                • 19777
                • 35 Posts
                Just a thought. I’ve noticed the line "RewriteBase /" has been added to the .htaccess file (or ht.access as the case may be).

                Some people may sit there wondering why their site doesn’t work anymore (as i did for a moment). I think that when you upgrade, there should be some sort of reminder, maybe near where it reminds you to delete the /install/ folder, to let people know to change the line RewriteBase incase their installation is in a subfolder. I.e. RewriteBase /root

                Just a thought...

                mark
                  • 25663 MODX Staff
                  • 12,272 Posts
                  Thanks JeremyL... the only theme that’s been remotely gone over is the MODx Light theme. All bets are off with the plain MODx theme.
                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                    • 33372
                    • 1,611 Posts
                    OK so there is a minor issue with the document tree PNG rollovers in the latest release that has an easy fix which will be committed soon. This issue will only be apparent when using IE6, since it is incapable of handling PNG transparency natively. The script uses a transparent gif and a filter workaround for IE6, but a couple things need to be changed to make it work properly.

                    First, the script is not finding the transparent gif. As a temporary fix, just upload a 1x1 transparent gif to the root of your manager directory and name it x.gif. Later this will probably live in the manager style folder, but for now this hasn’t been decided.

                    The other issue is that the script needs for the images to have declared sizes or they shrink to the size of our transparent gif (1x1). So this could be set in the image tags, the CSS file, or the JavaScript that does the replacing. For now we’re doing it in the JavaScript.

                    Open the file assets/js/pngbehavior.htc and make lines 63-68 look like this:

                    		// set filter
                    		element.runtimeStyle.filter = "progid:DXImageTransform.Microsoft." +
                    					"AlphaImageLoader(src='" + src + "',sizingMethod='scale')";
                    	   element.style.width = element.width + "px";
                        	element.style.height = element.height + "px";
                    	}


                    All you’ve done is add the two lines that set the correct size for the images after being replaced by the gif.

                    And lastly, there’s a tiny tweak to the CSS file to make the document tree’s icon bar not get taller on rollover in IE6.

                    Open manager/media/style/MODxLight/style.css and change the coolButtonHover class at line 913 to the following:

                    .coolButtonHover {
                    border: 1px solid #006400;
                    padding: 2px 4px 1px 4px;
                    height: 20px !important;
                    height: 17px;
                    background: #dee9c6;
                    }

                    That fixed everything for me. I gather that future versions of this release will have this corrected, and the fix may be slightly different. So make sure you look ahead in this thread and see if that’s the case before you bother doing this...
                      "Things are not what they appear to be; nor are they otherwise." - Buddha

                      "Well, gee, Buddha - that wasn't very helpful..." - ZAP

                      Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
                      • 19777
                      • 35 Posts
                      Whenever I edit a template, the text "<? echo isset($content[’newcategory’]) ? $con" is always found in the New Category text field.

                      I went through every template and this appears in every New Category text field. I accidentally saved the document with that in the field and it created a new category.

                      It is persistent and doesn’t go away, even if i save to an existing category and delete the "<? echo isset($content[’newcategory’]) ? $con" from the text field.

                      I would also like to be able to delete categories (especially ones with nothing in them). I know I can do it through MySQL, but it would be nice to have a tab called categories, with a list of categories and the word delete next to it. The Combined View doesn’t quite do this.

                      Cheers

                      mark

                      This discussion is closed to further replies. Keep calm and carry on.