• What happened to "assets" in RapidWeaver 5?
    The Assets feature in RW4 has been improved and renamed to Sitewide Resources in RW5. We've written a detailed blog post that explains the differences between "assets" and "resources", along with an example of what changes need to be made in any RW4 code snippets:

    RapidWeaver 5 - From Assets to Resources

    Return to FAQ List
  • Mobilize doesn't seem to be working with RW5. Is something broken?
    Mobilize works great with RW5 and with all 3rd party themes, and there's nothing you need to do if you're using a Mobilize page to redirect visitors to your site.

    That being said, if you are adding redirect functionality to a non-Mobilize page in your site, then you may need to adjust the code that Mobilize generates for you. Currently, it will be something like this:

    <?php

    include("assets/Mobilize.php");
    $detect = new Mobilize();

    if($detect->isMobile()) {
    header( 'Location: http://mobile.yourwebsite.com' );
    }

    //This page is set to ignore all desktop-class web browsers.

    ?>

    Note the line with "include", and that it is looking for the Mobilize.php file is a folder called "assets". RW5 has changed how it handles page assets - they are now located in a single, sitewide "resources" folder at the root of your website. This means the path to the Mobilize.php file will need to be changed, and here's how to do so (make sure you've updated RapidWeaver to at least version 5.0.2):

    1. Locate this line of code:

    include("assets/Mobilize.php");

    2. Change it to this:

    include("%resource(Mobilize.php)%");

    3. If your Mobilize.php file is located inside a folder of your site resources, for example "files", then you will need to include the name of that folder as well, like so:

    include("%resource(files/Mobilize.php)%");

    For more information about the difference between RW4 and RW5 regarding page assets and sitewide resources, see this post on our blog.

    Return to FAQ List
  • Qube v1.0 & Phelix v1.7 - How do I remove the iPhone version?
    ***PLEASE NOTE: Qube v1.4 does not require these steps. For Qube v1.4 just uncheck the "Include iPhone Support" option in the Advanced Site Options section. Nothing else needs to be done.

    To completely remove the iPhone version for these themes, a few things need to be done:

    1. Uncheck the box next to "Include iPhone Support" in theme options (located under the Styles tab in the Page Inspector).
    2. Remove a meta tag in the template index.html file. Here is how to do so (be sure to backup your theme and data first):

    - Right-click on the theme from within RapidWeaver and select "Reveal Theme Contents in Finder..."
    - In the Finder window that displays, open the index.html file in a good text editor (the free TextWrangler from Bare Bones Software is a good choice).
    - Remove the meta tag on line 5 or line 6, which looks like this:

    <meta name = "viewport" content = "width=device-width; initial-scale=1.0; maximum-scale=1.0;" />

    3. Change the DOCTYPE of the template index.html file. By default, the DOCTYPE is this:

    <!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.2//EN" "http://www.openmobilealliance.org/tech/DTD/xhtml-mobile12.dtd">

    Change it so the new DOCTYPE is this:

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    4. Finally, to prevent the iPhone from resizing images and performing other iPhone-specific functions, you'll need to "comment out" some code. This will "hide" that code so that the iPhone won't see it.

    For Qube v1.0 - On lines 25-27 of the template index.html file, add two forward slashes (//) like this:

    //iPhoneMenu();
    //mobileImageResize();
    //$fz(".zoom").fancyZoom({width: 250});

    For Phelix v1.7 - On lines 29-32 of the template index.html file, add two forward slashes(//) like this:

    //$fz("a.zoom").fancyZoom({width:250});
    //mobileMenu();
    //mobileSidebar();
    //mobileImageResize();

    5. Save and close the file, then re-publish your site.
    This will remove the mobile version, so that iPhone visitors to your website see the full desktop version.

    Return to FAQ List
  • Mobilize - Will it work with MobileMe?
    Apple has decided not to allow/support PHP on MobileMe, and this means Mobilize will not work for websites that are hosted on MobileMe. You'll need to use a different web hosting service that supports PHP in order for Mobilize to work properly. If you're looking for reliable, cheap web hosting with PHP support feel free to consider our web hosting plans.

    Return to FAQ List
  • Mobilize - Will Mobilize automatically make my site look good on cell phones?
    Not exactly. Mobilize is a "gatekeeper" or "traffic cop" type of plugin. It checks when people visit your website to see if they are using a cell phone or mobile device. If they are, Mobilize will send them to your mobile website.

    Keep in mind, Mobilize will not alter or change the theme you are using, or how your website looks.

    Return to FAQ List
  • Mobilize - Do I need to create a separate mobile website for Mobilize?
    Yes, we highly recommend that you make a separate website for cell phones and other mobile devices with small screens. This will make sure visitors using those types of devices will have the best browsing experience possible. Our MobileFusion and SmartDock Mobile themes were created specifically for use with iPhones, cell phones, and similar devices.

    If you've ever accessed a major website (like YouTube) from a cell phone, you'll notice that it's quite different from the site you see when visiting from a desktop computer. It's easier to navigate and loads quickly, with less graphics than the regular site. This is the kind of browsing experience you want your mobile visitors to have, and the best way to do that with RapidWeaver is to create a separate mobile website.

    Return to FAQ List
  • Mobilize - I've purchased a copy, now how do I activate it?
    After your transaction was completed, a custom license file was automatically generated and emailed to you. (If you can't find that email, be sure to check your spam folder). You'll need to drag and drop your license file into Mobilize to activate it. Here are directions on how to do so:

    1. Open a Mobilize page in RapidWeaver, and then open the Page Inspector.
    2. Make sure you've selected the "Page" tab in the Page Inspector.
    3. Drag and drop your license file into the text field indicated by the Page Inspector.
    4. Click Activate, and Mobilize will register your copy and remove all the restrictions.

    Return to FAQ List
  • Mobilize - I've tried to add my license file, and it's not working. Help!
    The first thing to check is whether your license file includes spaces in the name of the file itself (or in the path to the file), for example
    "First Name.mobilize". Currently, the Mobilize plugin can't process spaces in the file name (or in the path to the file).

    If there is a space in the file name of your license file, just edit it to remove the space. Then, be sure to move the license file directly to your Desktop. At that point, drag and drop the license file into RapidWeaver, and it should work fine.

    Though it doesn't happen often, there's also a possibility that your email client could be altering the license file, which would prevent it from being properly read by Mobilize. To get around this, we suggest forwarding the email with your license file to another email address (gmail or something similar, Apple's Mail program will also work fine with Mobilize license files), then download the file to your Mac from there and add it to Mobilize.

    Return to FAQ List
  • I can't change the sidebar menu colors in Glide v2.0 - Help!
    This problem only happens if you choose to have the sidebar menu display 2nd or 3rd level menu items under the "Sidebar Menu Advanced Options" section in the Styles tab of the Page Inspector. When we added these theme options we overlooked that we would also need to adjust how the color options worked so that you could properly control the sidebar menu colors.

    The good news is this is easy enough to fix! Here are directions on how to do so:

    1. First backup your data, and your copy of Glide. Don't skip this step!
    2. Download this zip file, and then open it.
    3. Inside you'll find three files. We'll be adding these three files to the Glide theme.
    4. Now open RapidWeaver's Theme Drawer and select Glide v2.0, then right-click on it and choose "Reveal Theme Contents in Finder".
    5. In the new Finder window that opens you should see a file called "colourtag.css" - Replace that file with the one in the zip file with the same name.
    6. Next, open the "css" folder, and you should see a folder called "sidebar".
    7. Open the "sidebar" folder, and inside you should see two files, one called "2ndLevelSidebarMenu.css" and another called "3rdLevelSidebarMenu.css" - Replace those two files with the ones in the zip file with the same names.

    That's it! Now just restart RapidWeaver and you should have full control over the colors in the sidebar menu.

    Return to FAQ List
  • ExtraContent Area 4 in Mirage v1.7 doesn't stretch the full width of the page in Firefox. What's the problem?
    *Please note: This is fixed in Mirage 2.0 - as such we recommend updating to the latest version of Mirage.

    This is a bug that was introduced when we fixed a different bug in version 1.4. Fortunately, it's easy to fix - to do so just add this custom css code to the Page Inspector --> Header --> CSS --> Custom CSS Field:

    #menuShadow {clear: both;}
    #menuShadow, #midContainer {top: -5px;}
    #bottomContainer {position: relative;top: -5px;}

    That will get ExtraContent Area 4 to display properly.

    Return to FAQ List
  • My CrossSlide or Cycle slideshow isn't working. Am I missing something?
    If CrossSlide or your Cycle slideshow isn't working it's usually because it can't find the images you want to display. This can be because the file name has been mistyped, or if an image hasn't been added to the Page Assets. Another common reason is when the folder for a page has been renamed. In the RapidWeaver Page Inspector, under the "General" tab, there is a field called "Folder" and one for "Filename". Changing the "Folder" field can change where Page Assets are stored.

    By default a page's assets are stored in a folder called "assets", but when adding a forward slash to the Folder field in RapidWeaver's Page Inspector, the assets are instead stored in a folder called "pageFilename_assets" where pageFilename is the name of your page as seen in the Filename field. For example, if you've changed the Filename to pictures.html and changed the Folder to something like "/vacation", then the page assets for the pictures.html page will be in a folder called "pictures_assets".

    You may also have noticed that the home page cannot have the Folder field renamed with a forward slash. However, when you rename the folder of other pages with just a forward slash "/", RapidWeaver renames the assets folder for the index.html page to be "index_assets".

    If you look at the CrossSlide code snippet, you'll notice that the script is looking for your page's assets images in a folder called "assets" - if you've changed the Folder in the Page Inspector so that it includes a forward slash "/", just change this value to "pageFilename_assets" (without the quotes) and CrossSlide should work properly. Note that you need to make similar changes for each page where you've changed the folder name to include a forward slash.

    The other possible problem is if you are wanting the images to be in motion (up, down, left, or right). In this case your images must be large enough to allow for that movement, so be sure they are larger than the space where you want them to be displayed, otherwise CrossSlide will not work.

    Return to FAQ List
  • In Mirage, there seems to be a lot of extra space at the bottom of the page. What's going on?
    ***If you're having this problem, it means you're using v1.4. Make sure to update to v2, as this issue is now fixed.

    The extra space below the footer is most likely from a small bit of javascript that we added that sets the height of the page when it's loaded - this is for pages without a lot of content to make sure that a user's background image has enough room to be displayed properly. This might be conflicting with other scripts on the page and incorrectly setting the height, so try removing it to see if that fixes your problem.

    To do so, you'll need to edit Mirage's template index.html file. Select Mirage in RWs theme drawer, right-click and select "Reveal Theme Contents in Finder...". In the next Finder window that opens, use a good text editor (I recommend TextWrangler from Bare Bones Software if you don't have one - it's free and works great) to open the index.html file.

    Scroll down and on line 41 you'll see this bit of code:

    bgheight();

    Simply add two forward slashes like so:

    //bgheight();

    This will cause that line to be ignored by the browser. Now save and close the file, then test to see if that fixes the issue.

    Return to FAQ List
  • I don't need the iPhone version of Phelix v1.0/Mirage v1.7/Glide/Unity. How do I remove it?
    To remove the iPhone version of Phelix v1.0/Mirage v1.7/Glide/Unity, three changes will need to be made - adding a different DOCTYPE to the template index.html file, editing a link tag to the styles.css stylesheet, and the removal of the iPhone.css link tags. As always, I recommend making a backup of your work before getting started.

    1. From RW's Theme Drawer right click on Mirage/Glide/Unity and select "Reveal Theme Contents in Finder".  In the next Finder window there should be an index.html file, go ahead and open it in a good text editor (the free TextWrangler from Bare Bones Software is a good choice).

    Right at the top you'll see this DOCTYPE:

    <!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.2//EN" "http://www.openmobilealliance.org/tech/DTD/xhtml-mobile12.dtd">

    This is a mobile specific one that tells the iPhone to display at native resolution. There are several different "desktop" DOCTYPEs to choose from, but I recommend replacing it with the following:

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    2. Next, around line 8 of the index.html file you'll see this line (you can skip this step if you're using Glide v1.7+, Mirage v1.7, Phelix v1.0+, or Unity 2.0):

    <link rel="stylesheet" type="text/css" media="screen and (min-device-width: 481px)" href="../../rw_common/themes/nimblehostv4/styles.css" />

    Change the media type to just "screen".

    3. Now look several lines down (around line 17, depending on the theme) for this link tag:

    <link rel="stylesheet" type="text/css" media="only screen and (max-device-width: 480px)" href="%pathto(iPhone.css)%" />

    Either comment it out (the <!-- --> tags), or delete it.

    <!-- < link rel="stylesheet" type="text/css" media="only screen and (max-device-width: 480px)" href="%pathto(iPhone.css)%" /> -->

    4. In order to prevent the sidebar from being hidden on the iPhone, you may also need to comment out or delete the following line from the block of javascript starting around line 33 (to comment out the line, add the two forward slashes highlighted in red below - this "hides" the line from browsers):

    //$fz("#zoomSidebar").fancyZoom();

    5. If you're using Phelix v1.0+, Mirage v1.7, or Glide v2.0+ then you'll also need to comment out or delete a line that automatically resizes images for the iPhone. This line should be located directly below the one above, and looks like this:

    //mobileImageResize();

    6. If you're using Glide v2.3, you may also need to remove a special meta tag designed for the iPhone/iPad. To do this follow Step 2 in the section above about removing iPhone support from Qube.

    That's it! Save and close the file, re-upload your site, and you're all set.

    Return to FAQ List
  • There's something wrong with the iPhone version - the text font is tiny, and the screen seems zoomed out. What's the deal?
    This can happen for a couple of reasons:

    1. You're using a domain name that is forwarded to your site, and "masking" the domain. Forwarding is okay, but masking a domain causes the iPhone version to display incorrectly. If you're not sure, see this question for more details on domain masking.

    2. The output setting in RapidWeaver's Page Inspector is incorrect. Under the "General" tab is an option called "Output". This should be set to "Default". If it's set to "Optimized" RapidWeaver will change the template page we've built for the theme which will cause this problem.

    Return to FAQ List
  • Can I change the color scheme of the iPhone version of your themes?
    It is possible, but requires manually editing one of the theme's core files. We're not able to provide iPhone-specific theme options because RapidWeaver doesn't have a framework in place for us to do so. We've asked the guys at Realmac Software about this, but they didn't give us a time frame on when this feature would be available - or even if it was something they were considering.

    We've started a poll in the RapidWeaver Forums where you can vote for this feature. Make sure to visit this poll and vote so that Realmac knows this is something you'd like them to add.

    Return to FAQ List
  • Do the iPhone version of your themes work with MobileMe?
    Yes! The only time the iPhone version won't display properly is when you have a domain name forwarded to your site and are "masking" the domain. For example, you have the domain:

    growbigtomatoes.com

    But your website is on MobileMe located at:

    web.me.com/bigTomatoes/

    In most cases, if you just forward the domain to your MobileMe website then when someone types in growbigtomatoes.com, they get sent to your MobileMe site, and the address bar of your browser shows this when he/she arrives:

    web.me.com/bigTomatoes/

    If the address bar of his/her browser shows growbigtomatoes.com, even though they are on your MobileMe site, then that means your domain is masked, and the iPhone version of our themes won't display properly.

    Return to FAQ List
  • A theme option isn't working. It displays incorrectly or not at all. What's going on?
    Usually this means that RapidWeaver, and usually your Mac, needs to be restarted. For whatever reason, RapidWeaver may have a hard time applying theme options if your Mac hasn't been restarted recently. The good news is this isn't a big problem, and there's usually nothing wrong with either the theme or RapidWeaver itself.

    Return to FAQ List
  • FancyZoom's rounded corners, shadow, and close button graphic don't show up in RapidWeaver. What's wrong?
    On all our FancyZoom enabled themes, we use a short bit of javascript to tell RapidWeaver where to locate these graphics when publishing your site. Due to how RapidWeaver builds a preview of your site, these graphics won't show up in the preview pane but will once your site is published.

    Return to FAQ List