Path & URL Vars
Documentation > Previews for 4.xx > Path & URL Vars
One of my goals for 4.xx is to reduce options no one uses. It should make the code simpler, cleaner, faster, and easier to develop. The risk is we cut out some option someone actually needs. :) I will be adding lot's more pages like these as I work through the core, but as I looked at this today, here's a start.
Currently we have the following variables set in BoltWire
boltwire
barnPath
scriptPath
systemPath
farmPath
imgPath
pubPath
pluginPath
skinPath
fieldURL
farmURL
imgURL
pubURL
fieldName
index
scriptURL
pagesDir
configDir
In most installations, none of these need to be set. With most non-standard installations, my guess is the only ones one really needs to set are boltwire and farmPath. And with cleanURL's you might need to add farmURL.
I'm inclined to simplify this so that most of the others are set automatically, and that we remove the options to change them. That is, you can still put your farm, field, and barn anywhere you want--but you wouldn't be able to move the subdirectories, or rename them. Similarly, index.php would be fixed. Just these changes would likely remove hundreds of lines of code and memory... With no loss of functionality for 99% of us. I would like a compelling reason not to simplify these things...
I think I am only using filePath which is not on the list. As I have two similar fields but with different pages. As all other fields don't use these files, I didn't put them in the farm.
Sounds like a custom setup. So that shouldn't affect us here. My question is more--are there any on the list you are using? I'd like to drop most of these...
Along the lines of changing the directory structure, would you consider changing these variables to match the upcoming structure as well?
