Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have read through the documentation at http://fusiondrupalthemes.com and believe I have followed all the instructions correctly.
The screenshot at http://fusiondrupalthemes.com/support/theme-developers/responsive-features shows options for selecting different layouts for desktop / tablet / mobile devices.
I cannot find this same set of options on any of the fusion themes.
How do I get access to the responsive features?
Thanks
Comment | File | Size | Author |
---|---|---|---|
#2 | Before fusion grid tool_1.png | 72.87 KB | Anonymous (not verified) |
#2 | with fusion grid tool_1.png | 90 KB | Anonymous (not verified) |
#2 | skin edit_1.png | 39.72 KB | Anonymous (not verified) |
#2 | appearance settings.png | 28.07 KB | Anonymous (not verified) |
Comments
Comment #1
esmerel CreditAttribution: esmerel commentedAre any of your screens the same? Do you have the tabs for it or anything like that? Just trying to confirm your install is set up right.
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedI have the same condition reported.
The tablet and mobile device layouts do not appear on the theme setting page when fusion grid tools is enabled.
Also, the blocks and their skins are correct when fusion grid tools is not enabled, but when it is enabled the blocks all expand to the full page width.
I know the system should work because it is ok in my test system on my wampserver installation, but it does not work properly on the full site on HostGator.
Can you please give my some advice on what could be my problem?
Comment #3
Anonymous (not verified) CreditAttribution: Anonymous commentedI discovered that the responsive features show up if the fusion based theme is enabled, but not set as default. When set as default, the tablet and mobile layouts do not show up.
Comment #4
chirhotec CreditAttribution: chirhotec commentedEDIT:
Okay, I'm pretty the issue I was having is the same exact as this one, and was skirted by temporarily selecting a different theme as the default as suggested in the previous comment.