0
Welcome Guest! Login
0 items Join Now

Responsive Module Class Suffixes

    • jeco's Avatar
    • jeco
    • Newbie
    • Posts: 14
    • Thanks: 1
    • Web Director

    Responsive Module Class Suffixes

    Posted 7 years 4 months ago
    • Hi -

      We have used the responsive module class suffixes successfully especially for our ads utilizing AdAgency. We have certain modules (ads) that show only on mobile devices and certain ads that show only on desktops. Now, we'd like to use the {loadmodule} or {load position} code to place ads within articles. When we do this, we lose the class suffix rules and the modules show on all mobile or desktops. Is there a way to make it so that we can specify the responsive classes and they will still work when placed inside an article? Not sure the best way to handle this so we are open to suggestions.

      Basically,it is becoming standard procedure to have ads within articles (not just in a module position at the top or bottom) and we've found the {loadmodule} or {loadposition} is the best way to have our editors drop code in an article quickly and easily. Getting them to show up just on mobile or just on desktops is the issue we are having now. Thanks!

      docs.gantry.org/gantry4/advanced/responsive-grid-system
    • MrT's Avatar
    • MrT
    • Preeminent Rocketeer
    • Posts: 101084
    • Thanks: 13481
    • Web Designer/Developer

    Re: Responsive Module Class Suffixes

    Posted 7 years 4 months ago
    • loadpostion has an option to specify the "chrome" That is used to render the module so if you add this you can get module class suffixes to render (which otherwise won't) but probably the easiest thing to do is just wrap the {loadposition xxxx} in a div with the responsive support class on that instead (then it's more obvious). All that said, I would avoid embededd modules in articles altogether as it makes maintaining a site much harder and time consuming.

      Regards, Mark.
    • Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.

Time to create page: 0.036 seconds