Thread

Yeah, that seems to have fixed the redirect, but I generally don’t want to force the URL to be auto generated for me because I like to use relative links, instead of absolute. Any other ways around it?

Hmm, I’ve looked into this and that doesn’t look possible without a core hack, which, well… you know :-D

What’s the rationale behind wanting to use relative paths only?

Relative paths (specifically, root relative paths) = small file size per page as the links don’t have to have the giant URL on there, easier to transfer between hosts or switch domain names (if needed)—all the paths are the same.

Hey Lea–

The difference in file size for an HTML file using relative versus absolute paths is going to be pretty insignificant. I’d say it’s one of those optimizations that ends up costing far more in other areas than the benefits it provides.

For moving between servers, why not use a multi-server config.php setup so that your EE installation automatically detects the correct site URL?

Kevin

Hi Kevin,

Whether it’s insignificant or not, page speed is all about the micro optimization, anyway. I’d rather it’s in favour of smaller page size. How would relative links cost “far more?”  I mean, the majority of navigation for sites ARE relative. It’s a rare instance to see someone go out of their way to link to an internal page typing out their entire url instead of /images/whatever.jpg. I’m genuinely curious. I’m not a developer so I may be completely missing something.

As for moving between servers… that’s all fine and dandy, but uh, how is that user experience for the developer better/simpler than simply deleting ONE line in ONE place in the CP? 😉

Oh, and in terms of redirect stuff, all the other redirects work except for default login and logout (ie. whatever.com/member/ sections)—I created a front-facing login page using the login form tag and the redirect to the homepage happened without issue, even when the root directory was not filled in.

Cheers,

Lea

Hi Lea,

I don’t think you’re missing anything, it’s just that some parts of EE depend on that path being populated, and the {path} variables use it as well. Typically when you move servers you’ll need to update server paths too, not just that one URL. You make a good point though that all these paths should be easier to change, and you shouldn’t even need to use the CP to change them (or alter the database). This is actually on our radar to improve significantly; right now we’re just focused on bug fixes and getting 2.2 out the door, so thanks for your patience, and the feedback!

Sweet, appreciate all the feedback and work you guys have put in. 😊 I’ve kept the URL out for some of my sites and haven’t had any issue, really. I think with membership stuff, though, it looks like it’s more needed.

If you can give me one more request, it’d be nice to know which parts of EE depend on that path being populated either in the docs or somewhere. I also don’t use the {path=} variable, anyway. 😊 Generally speaking, for my other sites which I’ve left it out, it hasn’t affected EE’s performance, page load, or anything. It’s only with this particular project where there were more membership options/logins/etc. 😊

Thanks again!

The path variables are really the main ones that come to mind. This particular bit of code that handles the refresh/redirect is actually in CodeIgniter, so it could affect some add-ons as well, I suppose. It’s good to know that everything else in EE seems to work, though I still wouldn’t depend on it, just from a “best practice” angle.