There are guidelines for making a backup of Vaultwiki? I need to reinstall my server and would be fine to have a proper backup of the vaultwiki content.
There are guidelines for making a backup of Vaultwiki? I need to reinstall my server and would be fine to have a proper backup of the vaultwiki content.
If you make a mysqldump of your database, VaultWiki should be included.
If you store attachments as files, make sure to backup the contents of the VaultWiki attachments directory (whatever you have it set to). In the Admin Panel, go to Content > Attachments. Near the bottom of the page it should say if attachments are stored as files and if so, what the directory path is.
- lead developer for VaultWiki
Thanks, I have all n the server and the backups. So if I restore the database and all paths are correct all will be fine. Next step should be the installation of the new version of VW, I need to collect for this.
Pegasus: you made the installation. Now I go to the settings and see that the images are on the database. Is possible that this setting has changed after you installed it? Or it's possible that you left the images in the database?
The Vaultwiki installation has evolved slowly so there was not a lot of content new after the importation form version3.
But there are problems in the installation, some related to codepages and the database has grown a lot and suddenly in the last week. I would restore form a past state before the abrupt size increase and I suspect that perhaps one of the problems is there.
As no edits on the wiki in the last month involved images. Can I extract the images from the database and restore from a previous state?, I expect that in the case in the prevoius backup the images were in the database, they will be restored, and if not, they will be found in the restored images directory
I'm wrong?
The problem I've noticed is that some settings are lost, the rendered codepage of the site is wrong and the users cannot choose another codepage in their browsers. I suspect that on of the two plugins that have problems with the database codepage have mangled something. Yours is one, the other is photopost. There are conflicts between the two mods: i cannot edit the photopost galleries without deactivating vaultwiki.
The problems are not solved deactivating all plugins, so something is bad in the database and I want to restore to some past moment and try to solve all things one step after one.
I've navigating the site and the wiki images are not visible. My suspicions are true: there is something wrong with the settings and the content.
It is possible that PHP didn't have permission to create the attachment directory when I installed, so I left them in the database.
Anyway:
When you make a database backup, you have to make sure that you add a command-line setting to export with the charset that matches the database connection you usually use in includes/config.php (in vBulletin the historical default was 'latin1'). When you restore the database, you have to add a command-line setting to import with the charset too. The character set of the database connection doesn't necessarily match the charset of the content in the database and mysqldump doesn't have a way to know what the charset of the dump file really is unless you say what it is.
All the charset settings between your old MySQL config file and the new one have to match. If your new server uses a newer version of MySQL, then the defaults may be different. With MariaDB, it's easy to miss some of these settings, as there are different ones for server, client, etc.
I had the same problem when we changed to a new server recently. There was a way to fix it after it was exported wrong, but I don't remember currently what we did. It wasn't easy. I think we had to use iconv on the whole dump file or something like that.
It is important that you get this fixed before worrying about other issues.
If some images and other content are not visible it might be that some paths changed if you are on a new server, or it might be something else. I would fix your character set problem first, since it is the only thing that requires the whole database to be imported again.
- lead developer for VaultWiki
We have successfully migrated the site to UTF-8 so soon I'll ask you for the installation of the latest version. I have a problem on 4 gamma: I need to deactivate it to configure anything on photopost, the plugin that manages the gallery on our site.
After the upgrade we should export the images out of the database to fix the space grow.
I have noticed some problems: after the migration to UTF-8 I see the contents correctly. The translation of the VW messages had some problems from a mismatch, I've corrected this. But now ihave another problem: If I edit one page the contents on the edit page is mangled as out of codepage, and If I save it the problem persists. You can see it on: http://www.leicaeme.com/wiki_index.p...encia-en-Leica
I want to migrate to the new version of VW but I need to fix some problems before that
Bookmarks