So far, the only way I've been able to install OP on a shared server is by
a) copying the OP files into the server
b) exporting a rather simple OP site database from a simple OP site I host elsewhere.
c) edit the databse to change all references to the new url
d) create a database and then import the edited database into it
e) change the settings to include the passwords/usernames/db_name
This will work at register.com, on a shared server hosting platform. But ONLY if the database you are importing is rather flimsy. Don't try to copy over the db for a crazy, really heavy site.
My suggestion is for the OpenPublish file package to include a really simple, barebones database, that can be edited and imported into a typical shared server ......
I don't know a heck of a lot about drupal, and OP and databases or php. But I can tell you that this program drives a layman like myself insane. And it would be awesome if the creators and OP community did more to make this more accessible and easy for small web publishers.
Comments
BUMP
Seriously,
You guys need to get serious about shared servers.
I can't this didn't get a response, given all the headache people had with 1.6.
FYI, I have OP 1.6 installed
FYI, I have OP 1.6 installed for my small newspaper's website on register.com.
But it wouldn't have worked if I didn't copy over the db from pinchost.com.
I have no way of even installing 1.7 unless I buy more server space.
Wow.
So OP creators don't care?
@midek, thanks for sharing
@midek,
thanks for sharing your experience. What you did is definitely a good way of doing it. A lot of people also install locally (using a packaged lamp stack like that from: http://apachefriends.org can simplify it a lot) and then move database to the production server.
We do care about making things simpler, but unfortunately there are technical limitations to what we can do. Drupal and OpenPublish (which adds many modules on top of Drupal) are complex systems that need memory and CPU power. Ruthlessly resource-constrained shared hosting plans are just too weak.
We make it very clear what the minimum requirements for OpenPublish are. Alas most shared hosting providers don't meet the requirements. Yet, since people are trying to use OP on shared hostings, we try to help them and try to squeeze every last bit of optimization in every new version, but there's only so much we can do.
Shipping OpenPublish with a database dump is not a sustainable solution. It is hard to maintain and would result in a whole bunch of different problems. That's why we try to avoid doing it. At least for now.
Just trying the best we can.
Thank you
.............................................
http://twitter.com/inadarei