First of all: Thanks for your support. But I included the base-href because of OpenGeeks suggestion, and the double "tobrands" only cause trouble while loading the .css & .js-files, right? It shouldn’t confuse the rewrite engine. And the .htaccess looks exactly as you propose. Plus, as I said, this works perfectly with 0.9.2.2. So I’m not sure what’s going on here.
Where exactly is the $_GET[’q’]-parameter processed? I’d like to understand how that works.
-
MODX Staff
- 10,725 Posts
The base href is the best way to set the root path of your sites in your templates and keep it consistent, regardless of what virtual directory is being accessed within the MODx site, or what physical directory it is being hosted from. Site content is best defined in a portable way by using paths relative from the site root (not the web server document root), as Ryan is trying to explain. Otherwise, anytime you deploy to another location on the same server or another environment, you’ll have to adjust all your content.
The logic involving the GET[’q’] parameter is scattered throughout the system currently, though most all of it is centered around the /manager/includes/document.parser.class.inc.php, particularly the cleanDocumentIdentifier() and getDocument() methods. You should be able to easily find it with a search through the code.
DISCLAIMER: However, if you change something in the core, don’t expect future upgrades to work your way; in fact, this is likely the last major/minor release in which any core logic will be located in the manager at all. In fact, these future releases will allow you to customize a majority of the core logic without hacking any core code, and is the reason I bring up the disclaimer at all.
I do see the advantage of the base href, and I do absolutely agree. But as far as I see, this is not my problem - although I might be wrong, of course. The problem is that the document I get when I request ___/news/news3.html is not the document that I want to get. I get, basically, an error page, whereas the document that I want to get is for some weird reason under ___/news3.html. What I want is the document to be under ___/news/news3.html: Within the "tobrand" folder, modx behaves as though friendly alias paths are switched off. If I copy the same page to a different server and try it right within the domain’s document root, there is no problem.
By the way: I have set the base-href correctly now. Doesn’t work.
I have used 0.9xx for quite a while now and never ran into any trouble. This is the first time that I just don’t get what’s happenig. And thank you for warning me not to change core functionality. I wasn’t going to, just interested. I believe that one fundamental thing that separetes modx (and most open source cms’ I know) from commercial products is the fact that you can’t change core functionallity without changing the very core of the application. I believe that modx is already one of the best, if not the best product there is, but it is going to be somewhere completely different if you are actually able to modulize the core.
-
MODX Staff
- 12,272 Posts
josh1013,
Have you tried changing everything as I suggested above yet? I see pages rendering (just without content) on both links above.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 12,272 Posts
I’m seeing content on every link you’ve sent. Which one is working and which one isn’t?
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 12,272 Posts
Please copy paste the contents of your .htaccess file here.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 12,272 Posts
Also, if you could, please PM me a manager login. Thanks.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
