Tagged: ,

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • July 13, 2019 at 2:27 am #1118240
    shrinkray

    Hello,
    I must configure settings to keep the Main Alternate menu for all mobile sizes. I’ve got Mega Menu product in place of Enfold menu and I essentially want it to appear for all sizes. Because the customer has many menu items, we drop into the mobile view very early. But then by the time the site viewed on mobile, the alternate menu has been disabled by Enfold. Please assist.

    Thanks!
    Greg

    July 13, 2019 at 12:13 pm #1118283
    Victoria

    Hey shrinkray,

    Here is the code you can put in Enfold > General Styling > Quick Css,  if it does not work, put into themes/enfold/css/custom.css

    
@media only screen and (max-width: 990px) {
  .responsive #header_main_alternate {
      display: block;
  }
}

    If you need further assistance please let us know.

    Best regards,
    Victoria

    July 13, 2019 at 12:13 pm #1118284
    Victoria

    Hey shrinkray,

    Here is the code you can put in Enfold > General Styling > Quick Css,  if it does not work, put into themes/enfold/css/custom.css

    
@media only screen and (max-width: 990px) {
  .responsive #header_main_alternate {
      display: block;
  }
}

    If you need further assistance please let us know.

    Best regards,
    Victoria

    July 15, 2019 at 2:58 pm #1118788
    shrinkray

    Thank you Victoria!
    Why did I forget display: block;!

    If this is not the appropriate place for this question I’ll repost elsewhere. For all my career, no one wants us to edit the core of something. Indeed there is info encouraging child-themes setup for Enfold. However, for most responses in the forum, editing the custom.css on the Enfold theme path is referred. Why is there not a recommendation to setup a custom.css file in my child-theme? When people update themes they will lose custom updates added by others. I took this project over from someone else and she had custom CSS in core. Shouldn’t that behavior be discouraged?

    Many thanks and for your patience on my questions.
    Shrinkray ;)

    July 15, 2019 at 3:55 pm #1118826
    Jordan Shannon

    Hi,

    Custom.css and quick css updates are recommended specifically for the fact that those customizations will be safe in the event that their are updates, especially those written in quick css.

    Best regards,
    Jordan Shannon

    July 15, 2019 at 8:33 pm #1118927
    shrinkray

    Hello Jordan,
    While Quick CSS is safe, for an update, I did not believe that custom.css in the Enfold path was also safe. That info was a surprise. I have viewed forum posts suggesting changes to JS files. Wouldn’t it be better for these changes to appear in a child override? My child theme is built with a bundler with a hashed JS and CSS, so I am not worried about cache for changes.

    Still since the theme has a button that would allow someone to reset the theme, I don’t like keeping settings like that in core nor in the interface. I have a unique situation to be sure; I just want to know what practices are recommended by Enfold dev team. It is important to me.

    I do not wish to offend; it is my desire to use and recommend best practices.
    Kind regards,
    Shrinkray

    July 15, 2019 at 8:57 pm #1118947
    Victoria

    Hi Shrinkray,

    There is a styles.css file where the css can be placed and it will work the same as the custom.css added by you there, and yes, you’re right, we’ve seen cases when clients reset their theme options by mistake.

    Glad you got it working for you! :)

    If you need further assistance please let us know.

    Best regards,
    Victoria

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.