How does one enable SES URLs after the installation has been completed?
I suppose to expand on this a bit… I’ve had to change my original plan of having everything at the site root, to being in a subfolder. The admin links work. The homepage comes up on the front end. However, none of the front end links are working correctly. Therefore I was going to just scrub using the /index.cfm/ bit and go straight to a friendly URL rewrite.
Did you do this via the installer?
Will you be using apache or iis?
Luis F. Majano
CEO
Ortus Solutions, Corp
www.ortussolutions.com
ColdBox Platform: http://www.coldbox.org
Linked In: http://www.linkedin.com/pub/3/731/483
Blog: http://www.luismajano.com
IECFUG Manager: http://www.iecfug.com
I did not make the choice via the installer, and was hoping there was a flag or the like in the admin. I’ll be using both IIS and apache (local dev uses apache for me as I just cannot stand IIS, production and remote stage/dev will be IIS).
Ahh ok.
No we do not have one in the admin, might be a good feature enhancement.
For Apache, we ship in the root a .htaccess file
For IIS, we have it inside of the installer module as web.config
Just drop those in your web root and open the /config/routes.cfm file and remove the “index.cfm” references, which should only be 1.
Luis F. Majano
CEO
Ortus Solutions, Corp
www.ortussolutions.com
ColdBox Platform: http://www.coldbox.org
Linked In: http://www.linkedin.com/pub/3/731/483
Blog: http://www.luismajano.com
IECFUG Manager: http://www.iecfug.com
Awesome. I’ll try this first thing tomorrow.
If that doesn’t clear up your static resources, turn on your browser’s debugging to see what the URLs are as that might shed light on what’s wrong. If you moved the app into a subdirectory, make sure you reinit (or possibly just restart CF) to ensure the app mapping is correctly picked up.
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
It’s the first time it’s been been run on the box (moved to remote dev last night). It looks like you can create an appMapping somewhere, and if found, it’ll append that to the URL. Question then; how does one go about setting that value?
Generally speaking, you don’t need to. ColdBox will figure out if it is running in a sub directory and adjust accordingly. There are a couple exceptions to that rule, but neither of them typically apply to ContentBox.
Why don’t you step back a bit and explain exactly what isn’t working? I thought you said something about images not loading, but re-reading your posts I see you said, “front end links” which I guess could mean anything. Can you give us a URL where we can see this in action, or show us what the " front end links" look like? We’ll probably a lot farther if we can actually see your issue.
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
What’s slightly odd is that all the admin items, login, reports, pages, etc. all work just fine in that sub directory. It’s the blog pages that aren’t rendering correctly and throwing a 404.
Start by reinstalling your IIS web server connectors. That alone has caused more problems like this than anything.
Next, try changing your blog entry point to something else like “articles” to see if having “blog” twice in the URL is breaking it.
Do you have rewrites installed? You may also need to modify them to work in a subdirectory. I just ran a test and our stock Apache rewrites don’t work in a sub folder.
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
Yeah… I’ve noticed that on the apache rewrites. I’ve been fiddling with them for a bit here, and it’s not producing a good result for me (yet). I’ve noticed the same behavior in terms of the 404 on this machine locally with apache as the machine with IIS in that it’s producing a 404 for everything but the admin. I’m going to try changing the subdirectory name and see if that helps.
Before you do anything, reinstall your IIS connectors. I’m very serious. That one thing has solved DOZENS of similar issues on this list.
When Adobe didn’t automate that part of the CF10 update process they seriously underestimated how many people wouldn’t do it as a manual step.
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
In both cases this is actually CF9.
Eww, in that case upgrade CF 
I would check make sure it’s not the rewrite rules screwing up due to the sub folder then. Enable detailed error messages in IIS and try to look at what URL it’s hitting.
Interestingly enough, /blog/index.cfm/blog/ works, but not /blog/index.cfm/blog/slug
Also, what version of IIS is this? You can’t enabled any JRun connector settings about verifying if the file exists, have you?
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
7.x. Whatever ships with 2008 Server. Sadly, there’s no budget for updating CF at this point at least as far as their current host is concerned. I’ll continue to poke about locally with apache/CF9 to see what may be happening.
Also make sure CF9 is fully updated. I’ll also note that CF9 is now 5 years old and no longer supported by Adobe unless you have purchased extended support for it. There’s no reason why a reputable host should still be using it IMO.
On the other hand, Railo is free and completely compatible with ContentBox. In fact, all the Ortus Solutions sites run on ContentBox/Railo (with the exception of Coldbox.org which is in the process of converting). We’re dropping support for CF8 in our next release of ColdBox (overdue) and our scopes will be set on CF9 next. We just can’t let old CFML engines hold us back any longer. So the moral with software is upgrade, or using something free
Back to your problem though, perhaps there’s some additional logging you can enable? The 404 coming from IIS indicates the ColdFusion code isn’t even being executed, meaning the issue has to be with IIS/rewrite/connector/etc configuration.
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
There’s things in the sphere of my control, for instance all of the sites I personally hosts are on a complete open source stack (Railo/mysql/apache/ubuntu). Sadly, this is an area outside my control ;).
However, it’s fixed! And it’s turned out to be easy… sortof. I changed the blog entry point to be “posts” instead of “blog” and it started working. Both locally and up on the remote server. I presume it’s mostly because ACF got all kinds of lost with the /blog and /blog on the same URL, but I’m going to just let it go as “fixed and I don’t care why” at this point. Onward to skinning at this point, I guess, and passing in authentication from a different admin area.
Glad to hear it’s working!
As far as customizing the login, ContentBox should let you implement your own security service to decide what consitues a logged in user. I’ve done that so hopefully Luis will chime in on how to do it.
And, if you haven’t seen them, we have a good webinar on skinning ContentBox sites:
http://www.coldbox.org/media/cbdw2013#1_3
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com