Posted by JurgenHeiman on October 4, 2010 at 10:37pm
Yes
100% (7 votes)
No
0% (0 votes)
Total votes: 7
Do you want to give input for OpenPublish howto's?
Group organizers
Group categories
Subsystem
- Design/Theme (238)
- Functionality (299)
- Information Architecture (32)
- Install Profile (75)
- Modules (62)
Comments
100% agree
You are totally right, OP could be overwhelming and some of the points that you have commented are the same as I am having right now such as theming and structure.
Could you explain me how to backup, migrate and restore OP?
I am working in a localhost environment with wamp.
Thanks for this poll I think this a great idea to improve OP implementation and a good resource to solve problems. I don't know but sometimes could be fustrating to solve things around if you don't have a place to share your experiences.
Leo Berlin
We could do some integration
We could do some integration of "manuals" for OP. I'dd be happy to write about manuals for new OP users where I can.
@Leob,
imo first step is to install the backup and migrate module (http://drupal.org.project/backup_migrate) and have it run through cron the schedule you like. You can tell it to ftp to whatever you want, so that's the database part.
As for the files, you could do a backup of sites/default/* manually at 1st time and then get something like cvs orso to get it say weekly.
-Ronald
using collation utf8_general_ci and op manuals
Writing manuals will be great because in the offical OP site some of the documention is not completed such as theming and structure.
I am not sure if this collation that I am using for the db is the right one. I did a research before creating it and I found out that utf8_general_ci was the standard one.
I will try the backup_migrate and learn the whole process becasue for sure will be some issues after importing.
Any differences migrating db from pc to mac using in one wamp and in mac mamp?
Thanks for your help.
@leob and resveld "imo first
@leob and resveld
"imo first step is to install the backup and migrate module (http://drupal.org.project/backup_migrate) and have it run through cron the schedule you like. You can tell it to ftp to whatever you want, so that's the database part."
Just a straight backup of the database will do. Unless you customize templates the file's hardly change. A simple scheduled append to an archive will do. I have both of these scheduled with cron. This afternoon it took me less than 10 minutes to create a development version of a production website. The creating of a new dbuser, db and new virtualhost took me more time than the OP backup and importing of data. It was on the same server though.
Since I broke it already trying to figuring out gmaps, I'll start fresh again tomorrow. Throw away the database and import the latest backup. I'll leave the files intact, since I might want to work with some modules.
backup
I will use this approach and let you know if I have any problems.
The main pro for the
The main pro for the backup_migrate module is that it doesn['t take into account the caches build up by the site.
On my production site I have a lot cached which is in cache_* tables of the database. With the bm module, it creates the tables, but doesn't fill them.
If you have a backup with all cache entries in it, it will fail the import.
-Ronald
@resveld "If you have a
@resveld
"If you have a backup with all cache entries in it, it will fail the import."
Haven't experienced this (yet). I'll look into the backup_migrate module.