Anyway, I'm cool. All my sites are running great with the new version 3.4.14 with that added config.php code in each field. (I already have other stuff in the config anyway)
What I am referring to is someone new to boltwire is probably most certainly going to test drive it in a subfolder of root and not in the root of the webspace when they are testdriving the new CMS. i.e. something like this -localhost/testbw/ -localhost/testbw/boltwire -localhost/testbw/fieldone -localhost/testbw/fieldtwo When they do that, they will run ito problems with farmURL and possibly be discouraged with BW that images aren't working. I guess, I'd suggest making the above method of setting the farmURL the default for 3 reasons: 1) Prior versions of BW worked that way. Easier upgrade with no user customization necessary at each site. 2) On my system at least, the same code above for farmURL also works correctly even when you install at the suggested default location: -localhost/boltwire -localhost/fieldone -localhost/fieldtwo 3) Folks experienced in BW are probably using custom settings anyway, and would be changeing this and several things anyway. Want to make sure that NEW BW developer has no roadblocks. Boltwire still rocks. Thankx Dan. -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
