As you may know from our about section, Wolf CMS is a fork of the Frog project. As such, Frog users may be considering to migrate to Wolf CMS for one reason or another.

Since the Frog and Wolf CMS projects are already veering off onto different development paths, it is probably advisable not to wait too long with any migration.

We can't tell you. Frog and Wolf CMS each have their own project goals, roadmap and are practically the same when you compare Frog 0.9.5 and Wolf CMS 0.5.5. However, large changes have already gone into the (at this time) up and coming Wolf CMS 0.6.0 version.

We would like to encourage you to make up your own mind! As with any software project, you should probably take a number of items into account when making a decision on migration:

• What are each project's goals? (do they match what you might expect?)
• What is each project's roadmap? (do they match with features you might want?)
• What kind of documentation is there available for each project?
• What kind of support and communications options are there?
• How do you rate each project's survivability? In other words:
  • do you think the projects will still exist a year from now? and..
  • how often do you think there will be new releases/updates/security fixes?

Also see our small but quickly growing end user documentation and the Wolf CMS administration guide.

There are some general tips you may want to follow in migrating from Frog to Wolf CMS. Please be aware though that these tips and this document cannot take into account any customizations you may have done on the Frog core or plugins code.

• Always make a full backup of both the database and filesystem.
• Turn off any non-core plugins before starting to migrate.

This is a suggested migration scenario. Please be aware that we cannot take any responsibility for any possible data loss that may occur. Also please be aware that this scenario does not take into account any possible customizations you may have done to the database structure, Frog core code or Frog plugins.

1. Make a backup of your entire database.
2. Make a backup of your entire Frog installation's directory.

1. Turn off any non-core plugins in Frog's administration area.
2. Delete your entire Frog installation. Make sure you have a complete(!) backup
3. Rename the database if desired/possible/necessary.
4. Install Wolf CMS from scratch and point it to the old database and the old tables.
5. Copy back the old ”/public” directory from your backup.
6. Update the settings in config.php and .htaccess if necessary. Use your backups as reference material.
7. Try to login to Wolf CMS.
8. Turn each non-core plugin on again one by one. Test each plugin before turning on the next one.

Does it support nice/clean URLs?

Yes. Wolf CMS 0.5.5 is a straight fork from Frog 0.9.5 with minimal changes, so it supports clean URLs. (Like in Frog, you just have to enable it in ”.htaccess” file and config.php)

Wolf CMS creates nice/clean looking URLs like:

• http://www.domain.tld/about.html
• http://www.domain.tld/products/

See the relevant wiki entry for more details.

Can you add/remove/update what other CMSes call 'content elements' or 'blocks'?

You can achieve similar functionality with “page parts”. The “content elements” or “blocks” are more like ”snippets” in Wolf - small (or even large) bits of code/content which can be called on any page, but edited in one single place. There are a couple of snippets created and in use by default in Wolf CMS, so that gives you an idea of how they work.

Can we rename the admin folder?

Yes, after renaming your admin folder you need to alter the name used by Wolf CMS in config.php.

Are Frog 0.9.5 databases compatible with Wolf CMS 0.5.5?

Wolf CMS 0.5.5 is completely compatible with Frog 0.9.5. It is a direct fork, and the changes do not affect the db structure at all.

For a full list of what's new in Wolf CMS 0.5.5, see this blog post.