I'm getting an error that I don't understand. I'm using the beta 1 version of openchurch, but it was happening when I was on the alpha 3 version as well. I'm not sure it is really an openchurch issue. I've created an issue report, but I thought I'd ask here as well.
The error is:
There was the following error - Manifest: http://173.254.28.25/~njumccom/?q=profiles/openchurch/apps.js Not Found
I understand the error is telling me it can't find the apps.js file. Yet, when I go to There was the following error - http://173.254.28.25/~njumccom/profiles/openchurch/apps.js I'm able to load in the file just fine.
When we were first looking to move to openchurch, I installed it in my personal webhosting account (hostgator) and it worked fine. However, the church's webhosting account is on justhost.com and that is where the error is showing up.
I'd like to get this resolved before we move forward.
Thanks for any insight or suggestions! - peace, Dave.
Comments
Solution (kind of)
Well, the solution is to not put openchurch in a subdirectory. We are moving to a new webhost and the URL was http://temporaryURL/~njumccom (njumc.com is our production domain). We used the temp URL to get things setup before we went life. However, the ~njumccom made it a subdirectory (even though it is in the root of the webhosting account).
So here's my dilemma, we want to install openchurch, configure it, populate it with the data we had in our old Drupal 6 installation, and then point our production domain to it. That means the base URL will be changed...and it looks like fixing that is difficult.
Right now I'm setting things up on an old domain I had (http://twomiddleagedpastors.com). I had to reinstall so that the new URL would be reflected in the install. However, once we want to go live, we will want to use the njumc.com domain...but everything in openchurch will be, basically, hardcoded to the twomiddleagedpastors.com domain.
Is there an easy way to fix this? Where in the database is the base URL stored (I tried changing base_url in the settings.php file but it didn't seem to have any effect.
Thanks for any info on how to deal with production vs. development drupal 7 installs.
Peace - Dave.
Hmmm. base url...
Unless I'm misunderstanding your question, or unless things have changed in D7 (I'm running a D6 site), there is essentially no use of base URL in Drupal. Internal site links should just the local portion. The base url is handled by the webserver.
I can tar up my Drupal site, get a database dump, move the whole pile over to my local linux box, untar, restore the database, and it works. The church website url automagically becomes 'http://localhost', as it should.
For production vs development, you should look up tutorials on how to move a Drupal site. And the Backup and Migrate module comes in very, very handy.
Changing URL
When I go into the Configuration-> Site Info, all the base URLs are set and there isn't an option to change them. When I tried to move openchurch from a subdirectory to the root, I had all sorts of problems because Drupal kept trying to find things on at the subdirectory. That's when I went into configuration -> Site Information and discovered that the URLs were still set to use the subdirectory.
This also happened when I was using a temporary URL that had the IP address in it. When I switched to use a domain name, the Site Information still had the URL and was using it to find things. That wasn't a big deal, but, if I remember right, it would end up showing up in the browser.
I'll have to look at the backup and migrate option. What I was hoping to do was get everything setup and then just have to point the current domain over to it. RIght now our production website is on a different hosting service.
Thanks!
still is the webserver... I think
I just got into my local linux box and looked at my (D6) development installation site information admin page. I opened two different browsers (firefox and chrome) to get two different sessions, logged in and looked at the site info page, BUT I accessed the site using http://localhost on one, and http://192.168.0.198 (the local IP) on the other. The site info page dutifully reported exactly the URL I used (localhost vs IP address), which was passed through by my webserver.
(If you're using the mobile tools module, whatever URL you use to access the site is converted to another URL by the module, one URL for the desktop site and another URL for the mobile site. Which is why I earlier said that Drupal almost never needs to know your base URL.)
So maybe your situation is new behavior for D7. The session may well keep the original base URL -- did you logout and close your browser between using the different URLs? Maybe I ought to try a D7 install just to see what's going on...