Installing WordPress is not difficult. Most web hosts offer easy “1-click” installation options. It only takes a few minutes to install. If you prefer not to do it yourself, I install WordPress, themes, and plugins for a small fee.
You can create custom sites without touching PHP at all by using a fully-customizable theme. Depending on the design you are creating, you might need to write some CSS just like you do with BlockBuilder 2.
If you prefer to use a theme “out-of-the-box,” some themes (especially freebies) do not allow very much customization so you might have to write some CSS or get into the PHP to get the look and feel you want.
You can keep your page names with the .html extensions when converting your SBI site to WordPress.
If you have a new or small site, I recommend changing the page names to the WordPress format. However, you will need to create a 301 redirect for every URL that changes so you don’t lose traffic.
You can change the URL format for large sites but you need to write a custom 301 redirect to redirect all of the .html pages to the WordPress version. This can be a complex process, especially if some of your page names are changing.
A 301 redirect is a line of code in a special file that tells the internet where to find a file if it has been moved. Redirects allow you to change the URL of a page (or website) but not lose your traffic or page rank in the process. In WordPress, they are created using either a plugin or manually altering the .htaccess file through your cPanel. You can also edit the .htaccess file directly, but this is an advanced skill. If you do it incorrectly you can break your site.
By default, all WordPress content-related tables are dropped and recreated as part of the migration process, wiping out all the existing data, and thus, avoiding conflicts with any sample data entered by before the migration.
The same process cannot be employed when migrating users. Otherwise the migration would remove the admin user information entered when installing WordPress and you wouldn’t be able to log in your own site. This is why, the .sql script containing the users migration data adds the new users but respects the existing admin user in the WordPress site.
Nevertheless, the script assumes that the admin user (id = 1) is the only existing WordPress user. If there are other users please remove them before importing the file. Alternatively, you could provide us with a copy of your WordPress database and we could configure the migration to make sure it respects all existing content.
A big difference of WordPress wrt others CMSs like Drupal is the fact that WordPress does not allow users to upload/change their profile picture. The reason being that the profile picture of a user is not managed by WordPress itself. Instead, WordPress relies on the Gravatar (global avatar) service to retrieve and show the picture corresponding to a given user.
The benefit of gravatars is that you can share the same profile picture among most of the blogs, forums, … where you participate. The disadvantage is that you need to register in Gravatar and upload your picture to see it in your WordPress.
This is the reason why user migration from Drupal, Joomla and others to WordPress will not migrate the profile picture of each user to WordPress. If the migrated user is already registered in Gravatar (based on the email information) his/her picture will immediately appear in WordPress. If not, s/he will need to register and upload the picture there.
Of course, if migrating user pictures is a must for you, there are WordPress plug-ins that provide an alternative functionality. We can help you choose one and study the additional migration features you’ll need to use/initialize it.
If no custom menu is defined, the default WordPress behaviour is to show all pages as menu items. Obviously, specially if your site has plenty of pages, this default approach may not work for you.
To remove this WordPress menu and create your own just go to Appearance->Menus and add your own menu.
If you requested the Content Migration Service, you just got a .sql file with your new WordPress data ready to be imported. To make sure everything goes smoothly please follow these steps:1 – If you are using redirection rules] Install the redirection plug-in. Do not change any configuration option, just install it and activate it. After, set the permalink variable for the site to in Settings Permalinks2 – If your migration includes a forum] Install the bbPress plug-in. Do not change any configuration option, just install it and activate it.

3 – Import the .sql file in the database that your WordPress site is using (some further instructions on this). IMPORTANT: remember that, unless explicitly agreed beforehand, importing the file will wipe out the existing information in your WordPress content-related tables. The rest of the tables will be respected (check with us if you have questions regarding which exact tables will be affected). If you contracted the user migration feature remember that all users except for the user with id=1 (i.e. the user created when installing wordpress) will be removed (read more on this). If you are surprised to see all pages appearing as menu items, read this. Remember that creating a backup of your database before applying any sql script on it (ours or any other) is always a good practice.

4 – Copy and paste all image files from the “/sites/default/files” folder (or the folder you’re using to store the media files, we can help you to locate the exact folder) in your Drupal site to the wp-content/uploads folder in WordPress. Respect the same subdirectory structure if any, i.e. a Drupal image file in “/sites/default/files/sub/X.png” should be moved to wp-content/uploads/sub/X.png

leave a comment

Your email address will not be published.