Forum Replies Created
FilipilicKeymasterAugust 26, 2019 at 10:13 amPost count: 7
Avada, nor it’s plugins, violate GDPR law in any way. What it does is that it provides tools necessary for user to make their site GDPR compliant, but ultimately it’s up to a user to make sure that content used on their site is aligned with GDPR.
For upcoming releases we’ll look into adjusting content filtering so that spacial case is handled as well, but until then you can use [embed] or [fusion_youtube] shortcode inside text widget in order for Privacy consent to be displayed.
BestFilipilicKeymasterApril 19, 2019 at 4:02 pmPost count: 7
If you would like to insert Fusion Slider into every page you should replace
<?php avada_sliders_container(); ?>with following code:
<div id="sliders-container"> <?php echo do_shortcode( '[fusion_fusionslider name="slider-shortcode"/]' ); ?> </div>
Where slider-shortcode should be value of slider’s shortcode field: http://prntscr.com/ne8jiv
I hope this helps! 🙂FilipilicKeymasterMarch 19, 2019 at 5:23 pmPost count: 7
I’m sorry to hear that you’re having issues during update process, but I’m not sure how it can be related to Avada opening database connections.
Avada, Fusion Builder and Fusion Core don’t open any new database connections, but use connection which WordPress opens when it loads. Besides being needless to open new connection, since one is already available, that is also strictly forbidden by coding standards which we strictly follow.
During update process Avada interacts with the database (to update version number and sometimes to migrate Theme Options to new format), but that is done using WordPress’
update_optionfunction which is used by WordPress itself on any page load.
I would advise that you try disabling other (3rd party) plugins before the update process as well. Note that after Avada is updated it will clear caches so depending on your setup it could be that server takes heavy load while cache is rebuilt. Also, you might want to check how many connections are active at the moment. It might be that some other plugin or application on your server is opening connections for some reason.
BestFilipilicKeymasterFebruary 15, 2019 at 2:52 pmPost count: 7
Thank you for your suggestion, adding icon picker in Theme Options panel is something that is perfectly reasonable request and it would indeed improve usability of Social Links section, but unfortunately it is not simple as it might look. Icon picker control has it’s own dependencies and adding it to a repeater control with subfields is a bit more involved. Also, that would require color picker and maybe some other subfield to be added as well in order to make option complete after icon addition.
Adding text input which would allow icon code to be entered might look like an easy solution, but it wouldn’t work really. Except that is not user friendly Font Awesome 5 added icon subsets (styles), which require that an icon subset is also specified and only icon code would result in empty space being displayed. Except that this approach would require color picker (and possibly other subfields) as well.
As for that part in which you mentioned image shared in the Facebook, I’m not sure if I understood it correctly. Image which is shared on the Facebook is set using Open Graph meta tags. Open Graph tags can be enabled in Theme Options Panel (Advanced -> Theme Features section), but also many social and SEO plugins can add them as well.
Once those tags are on enabled Facebook will use image which is specified by the og:image tag and not any other image from the page which technically could be icon, although it is probably too small (Facebook has dimension limits).FilipilicKeymasterJanuary 31, 2019 at 3:53 pmPost count: 7
Can you check if Font Awesome subsets are added correctly in the Theme Options -> Advanced -> Theme Features section: http://prntscr.com/mdnewp ?FilipilicKeymasterDecember 26, 2018 at 9:18 amPost count: 7
Your issue is most probably caused by you not running latest Avada version.
Latest Avada version is 5.7.2 and it’s strongly advised that you upgrade since it ensures compatibility with WordPress 5.
Please follow this link for more information: https://theme-fusion.com/wordpress-5-0-avada-and-you-all-that-you-need-to-know/FilipilicKeymasterJuly 16, 2018 at 1:47 pmPost count: 7
Error is most likely caused by memory limit being set too low.
I would suggest that you check our blog post about possible reasons for exact same issue and the ways to fix it: https://theme-fusion.com/how-to-fix-500-internal-server-error-wordpress/