Fixing Problems

If your page looks strange when you published it online, but seems to be right when previewing it in RapidWeaver’s Preview Pane, you should Clear the Publishing Cache and reupload your site. To clear the publishing cache, select the related menu entry from the File menu.
If you are using RW 4.X, use the menu command Republish All Files from the File menu.

Sometimes the code you added to your page is not valid HTML. To validate your code, you can use the W3C HTML Validator at http://validator.w3.org.
1) Type the URL to the validator in the browser location field (I also recommend to add a bookmark to this page, as you should test your site on a regular basis)
2) Type in the URL of the page you want to validate
3) Click on the Check button
After a while you should see an output of the problems. You can ignore the warnings, but should correct any Errors you receive.

Test, if your pages show OK in other themes – best with the themes shipped with RapidWeaver.
If the page looks right in other themes but not with one you purchased here, you should send me a bug report.

I have tested all themes with many third-party plugins available. Most of them work without any problem. But you may find a plugin that doesn’t work with some themes (mainly the Sphere and POP theme).
Following is a description how you could make them work with other plugins that break the themes:
I have created a theme named "CAEmpty" which you can use to fix the problem described above. This theme can be freely downloaded from my site at Richardet Design (http://www.richardet-design.com/material/kostenlos.html). The theme CAEmpty creates pages containing only content – no header, footer or navbar.
1) Create your 3rd-party plugin page and choose the theme "CA Empty" from the drop-down menu Page-Specific Theme. Note that you should choose the same background color as is used in the main site with the main theme. Now chose the General Settings tab and make sure you disable the Show in Menu feature.
2) To include this page in the site create a new page which will be the container for the page you created in step 1. Choose iFrame from as the Page Style. Click the Setup button of the iFrame page and write the correct link to the page created in step 1. As this will vary from each site I can’t tell you what exactly you will have to write. Check the Folder and File Name entries in the General Setup section of the 3-rd party plugin page you created in step 1
Note that you may also use a blocks page to include your iframe. That way you can position it where you want on the page. To do this you have to write the iframe HTML code in a HTML container in blocks. Here is an example code snippet to show you the syntac:

<iframe src="../page3/page3.html" frameborder="0" width="600" height="400" />

Make sure you match the width and height with your block on the blocks page. Also the content of the src attribute depends on the URL your dummy plugin is uploaded.

I also created a small screencast on this step. If you want you can have a look on it in my screencasts section.

Even I have tested all my themes for IE7 (IE8 will follow) compatibility, it is possible I haven’t found all bugs yet. But before you ask for a support ticket, please make sure the following site preferences are set:

Make sure you disabled the XML declaration check box in the site inspector. Adding a XML declaration can break IE/Win.

If the XML declaration fix does not help, try setting the Output for your site to Default.

If none of the steps above fixes the problems and you think you found a bug in my theme, please contact me at support@rapid-ideas.com

Some themes uses the mootools framework, which also some 3rd-party plugins are using. The problem is that many plugins use different versions of the framework and so will break either the theme or the plugin. As the development will be toward V 1.2 of the framework, I started to also migrate my themes to that version. But there are still many plugins using the old V 1.1 and so you will have to use a different theme version to make them work. As soon as the migration perion to V 1.2 is over I will remove the old theme version. Until then you will have to use both.
Note also that I won’t further develop the older theme version as it takes too much time to support several versions at the same time. So, whenever possible you should use the newer version (which are now suffixed by "MT1.2"). Whenever a page doesn’t seem to work, you should set the page specific theme to the old theme version in the page inspector -> styles tab.