This is my first time trying to install a production site (on Drupal stack local on my pc) to hosting server. Would appreciate if someone could help me get this straight in my head.
Initially I downloaded a new installation onto the hosting server using fantastico. I kinda got this to work but there were lots of bits missing here and there which I figured must be because my local installation has all sorts of modules and things that the new version doesn't, so now I'm uploading the core files from my pc - I really hope that's what I'm supposed to be doing. I exported/imported my database and reconnected it (not sure that I could do it again!!) and all content seemed to be there.
What I can't get straight in my head is whether using the Aquia stack for multiple sites is a good idea. Surely that means if I upgrade to a newer version (locally), copies of any sites I've already done may break and I'll be forced to go through all sites I've done and upgrade them also.
So would it be better to get a stand-alone version working on my local pc first and then upload that to the hosting server.
Very confused - very new to this.
If anyone can shed any light, I would be very grateful.
Comments
The question is the same
The question is the same here.
Built the site using aquia drupals stack (d7.7) on the local machine and then tried uploading to 1and1. tried ftping the whole thing which sort of worked but got a mysqli error, so I changed it to mysql in the settings .php, then a couldn't connect to database 127.0.0.1 error.
Deleted all that and ftp'd a copy of 7.7 and after adjusting the .htacces file to suit 1and1 ran through set up and was able to see most of the site with some menu errors.
To add to the above question: Can someone possibly provide or point to some clear guidance on taking a site created on the localhost using the aquia stack to the web server?
**** I did find this and it was very, very helpful but I think there's a step missing 'cause it isn't working as easily as it shows in the video........http://learnbythedrop.com/drop/132
ok well.... I officially give
ok well.... I officially give up on drupal.
It was fun to learn and the extensabilty is great and I did learn a lot - however after days and days and days of trying to get a site built using core drupal 7.7 within the aquia drupal damp stack on my local machine to actually work properly on the web host (with NO success) it is obvious that the ROI just isn't there. (heck could you imagine if it was a customer site and not just a test site?)
Good luck to those still trying I hope you win.
Hope this helps
I didn't have any problems once I got it connected.
I ftp'ed all the files
Exported the database thru the acqui desktop thingy
Created a database on the host server
Imported the database
Changed the name of the folder that sits just inside the sites folder. Was something like sitelocalhost and needed to be changed to the url site.com
Then inside that folder there is a settings file and down the bottom there is a url line that needs commenting out with // because thats to do with a multiple site and then you need to put in the database name, password etc (this bit can be tricky and depends on your host). My cpanel gave the new database a really obscure password (i was thinking it would be a password i assigned) and to be honest I can't remember where I eventually found it
Hope this helps, but seriously, there has to be an easier way
_
not knowing how to migrate a site from dev to production is hardly a drupal issue-- and if you have 'clients' I would certainly hope you 1) knew the difference and 2) knew how to migrate from dev to production, lol.
Your point is noted and while
Your point is noted and while it may not be a Drupal issue specifically it was (I believe) an issue with the hosting company (1and1) which they were unable or unwilling to resolve.....and as I researched it out, it became clear that issues of going from prod to dev came up a lot with a many hosting companies. It seems to me that if this was a client site it would have under a number of circumstances created to many headaches to be worth the return.
All that said I really like Drupal and spent to much time learning it to give it up (yes I know what I said (....never give up, never surrender)) so I looked into Drupal Gardens and can say that it works perfectly. Not being a high end designer or coder DG provides all the tools without the concern of "will it work on the server or not" but with all the benefits of Drupal's power and of exporting to a different host if needed for specific modules etc.