Shoppers wanna shop, whenever and wherever. Two-thirds of smartphone users have made purchases online using their mobile devices, which means that your store should be optimized to sell across all devices. 

Volusion offers beautifully designed themes that you can customize to fit your brand’s unique aesthetic and selling needs. What’s more is that our newer themes use responsive design to adapt to any size screen. This way, your customer gets the same great user-experience across all devices they use to shop your store.

That said, if you’ve been a Volusion customer for a while (thank you!), you may be using a “legacy” (read: older) theme, which means you may run into some glitches when it comes to compatibility across smaller screens.📱

If you can’t upgrade to a new theme at this time, we still want you to be able to offer your shoppers the best user-experience possible. So here’s a handy guide to help you troubleshoot any Uh-ohs that might arise from mobile commerce on a legacy theme.

Uh-oh 1 😲 

I’ve enabled Mobile Commerce, but the mobile version of my store does not display when I access it on a compatible device.

By default, the homepage of both your desktop storefront and your mobile storefront is the /default.asp file. Some merchants choose to override the /default.asp file with the /default.htm file (at Design > File Editor) to create a special landing page or splash page

This configuration, however, is not compatible with Volusion Mobile Commerce. To resolve this issue, you must clear the /default.htm content so that the mobile storefront displays your /default.asp file.

Uh-oh 2 😟 

I uploaded a logo for the Mobile Storefront, but it looks distorted.

Your logo is ultra important for branding, so you want it to look good! The logo should be in .jpg, .gif, or .png format, with a recommended size of 200 x 100 pixels.

Larger images are scaled down to these dimensions, which may cause the logo to appear distorted depending on its original proportions. 

Smaller logos display at the original uploaded size, causing them to look quite tiny on the screen. For best results, upload your logo at the recommended size.

Uh-oh 3 😧

Nothing shows up when I view my site on a mobile device.

You don’t want your site playing hide-and-seek when shoppers visit it on a mobile device. 🌚 Check to see if you may have previously entered content into the /mobiledefault.htm file, which creates an intermediate splash page to introduce your mobile storefront. If there is any content at all in your /mobiledefault.htm file, this page will appear rather than your category list.

To ensure your customers can access the storefront category list after seeing the splash page, be sure you have manually added a link on the page that points to /mobile.aspx. For example: <a href="/mobile/default.aspx">Shop Our Mobile Site</a>

You can access the /mobiledefault.htm file by going to Design > File Editor in your Admin Area.

Uh-oh 4 😩

My mobiledefault.htm splash page is not appearing when I view my site on a mobile device.

If you splash page isn’t looking so splashy 💦  on a mobile device, you must include the following URL somewhere in the /mobiledefault.htm file: <a href="/mobile/default.aspx">Shop Our Mobile Site</a>

Replace "Shop Our Mobile Site" with your preferred text. You can also use HTML to attach the link to an image or button on your splash page.

Uh-oh 5 😫

My mobiledefault.htm splash page is not appearing when I click Preview from Design > Mobile.

When you are previewing the Mobile Storefront from a desktop computer, the mobiledefault.htm splash page is ignored. To view the splash page, visit your store's URL on a compatible mobile device or add the following path after your  store’s domain name in the URL bar: /v/vspfiles/mobiletemplate/mobiledefault.htm.

Uh-oh 6 😠

I don't recognize what I'm seeing; it's just one list of categories.

Your Mobile Storefront likes to keep it simple in legacy themes and presents a streamlined version of your category list. It removes any categories that contain products, and displays them alphabetically or by category Display Order (if specified). If you have hard-coded categories or use nonstandard methods for associating categories and products, this may result in duplication of categories.

For more info on category display, check out our main Volusion Mobile Commerce article.

Uh-oh 7 😕

Product pages that should show multiple child products are showing up as a single product, priced at $0.00.

This is one of those times that might really get you thinking about switching to a responsive design. This issue may be occurring because you have products set up using Multi-Child Add To Cart. This capability is not available with Mobile Commerce. Unfortunately, there’s no easy fix for this except to update to a responsive design theme.

To learn more about product display, check out our main article on Volusion Mobile Commerce.

Uh-oh 8 😢

I'm getting a screen filled with long, complex error messages.

Error messages ⚠️ are scary, for you and your shoppers. 😱 If this message appears somewhere in the first few lines ...

“Conversion failed when converting the varchar value 'x' to data type int.” (x can be any character in this example)

… you have entered an unexpected value in a field, either by importing data via CSV or by entering data in table view. Check any data you have recently have entered this way. 

Uh-oh 9 😵

I receive a pink-shaded Error 500 when accessing my mobile store.

Pink, what a lovely shade! 🎀  But not for an error message. Make sure you have a default currency configured for your store under Settings > Currency.

Summary

While you can continue to use your legacy theme with these troubleshooting tips, it’s worth considering making a switch to a new responsive design. Just think of all the potential headaches you’ll be saving yourself and how much better the shopping experience will be for your customers. Embrace it as an opportunity for a creative refresh and to capture shoppers’ eyes in the modern ecommerce world. So whatcha waiting for? Get with the now. 😀

Did this answer your question?