Forum Replies Created
-
Posts
-
Thanks biwales ! Makes sense now. ;) Until this is fixed that’s a good trick to know… as long as I have only one page with a submenu, which is not the case. ^^;
That’s quite weird. Anyway, this menu seems to work. I’ll investigate a bit further. ;)
Thanks for your support. ;)
Good day to you,
Fred
Thanks Josue for your really quick reply !
Ok, I updated and added a submenu on this page : http://agi.to/a-propos/. Right now, the submenu is showing my “Footer menu” (it’s the name I gave but it is situated in the socket to be exact) but I selected another menu in the element options.
Hope this will help.
Fred
Hi to the team !
Finally tracked down the culprit : Google Analytics for WordPress ! Deleted it and added the analytics code to Enfold panel. ;)
SOLVED
Hi to the team !
Does anybody have any idea about this issue ? I compared plugins, functions.php and settings between my staging environment and the main site and I really don’t see why logged out user can’t see portfolio items with a layer slider.
Any help or hint would be much appreciated !
Fred ;)
PS : disabling all plugins doesn’t solve th problem either…
Great ! Thanks Ismael, that should do the trick !
Thank you to both of you for your quick support.
Good day to the whole team !
Fred
Hi David,
Thank you for your reply. Like I said in my first message, I already fixed the padding-top issue thanks to Gingerstu (see link in my first message). About that, I wouldn’t recommend the fix you provide, since it will affect all pages and mess up the header everywhere else (for people using a sticky header at least).
For my second issue, I am really sorry but I don’t understand how changing the height of a full screen (hence 100% height) slider would solve the problem. Anyway, it’s not a big deal and I can use the workaround (adding extra color sections to manually force a full-screen result) that I was using before the “minimum 100% of the browser height” feature was added to color sections.
Still, I kind of have the feeling that this “Ghost Header” is a collateral damage due to the new (and great !) “fade-in sticky header” that is not “compatible” with the Blank Template (no header). If that’s really the case, I thought it would be a good idea to notify the team for the next update. ;)
Thank you for your time,
Fred
Thank you for the tip. I’m going to try this right now ! I also really love the addition of this print.css !!! Great job… as usual !
I have an other issue though : the next and previous links’ arrows (right and left) appear on every printed page, hidding part of the content. I tried to print out this page (as a pdf) : agi.to/metadonnees-et-ressources-pedagogiques/
I guess that hiding those elements in print.css should do the trick but I prefer to report it here anyway for future releases.
Regards to the team,
Fred
Hi all !
Enjoying the last update right now, with the French translation : great job, thanks ! However, the problem that I talked about in that thread is still valid. At least now, the sentence is translated in French but it’s not my translation. That string is still located only in the default Textdomain and I can’t generate a .mo file. Would it be possible to have it added to the avia_framework Textdomain like all the other strings ?
Thanks in advance !
Fred
Great Peter !
Since I don’t need this function right away, I might even just wait for the next version and the shortcodes integration for the menu. ;)
Thanks a lot !
Fred
Hi Ismael, Hi picnmix,
I was using the same code (<span class=”avia-font-entypo-fontello”>insert icon here</span>) to use icons in my main menu but it doesn’t work anymore (with neither 2.3 or 2.3.1). My other icons are working fine though. Don’t know if that’s the case but I feel like the class for the icons or the css method have changed… I tried using : data-av_iconfont=”entypo-fontello” data-av_icon=”” aria-hidden=”true” combinations without success either…
Any thoughts ?
Fred
Hi all !
First post here : support and users’ questions are so great I always find an answer to my problem ! Great work !!
I’m currently making some custom translations specific to my website and I stumbled upon the same problem as stated in this thread : https://kriesi.at/support/topic/some-strings-are-not-localized-with-po-mo/ Since there has been a few updates to Enfold since that time, I was just wondering if this fix was scheduled for a future release.
If I may add, I’m using the Codestyling Localization plugin as recommended and it appears that the “unlocalized” 2 strings are not in the avia_framework Textdomain like all the other strings, but in the default Textdomain (see screenshot below). Don’t know if that helps…
Thanks again for the great support !
Fred
Hi jh100, Hi Ismael,
I kind of had the same issue and stumbled upon this thread. It was definitely not a parent > child relationship issue for me and I solved it by adding this to my quick CSS :
.header_color .main_menu ul:first-child > li.active-parent-item > a > .avia-menu-fx {opacity: 1;
visibility: visible;
}
.header_color .main_menu ul:first-child > li.active-parent-item > a > .avia-menu-fx > .avia-arrow-wrap {
display: block;
}
Don’t know if it’s he best solution but it works for me (not for blog posts though but I guess it’s because they’re not really children of the maine blog page). Hope it helps !
Fred
