Forum Replies Created
-
Posts
-
Hey @Yigit, just FYI, we just updated the file as there was one text missing. The download link is unchanged.
Best,
JanHi @yigit,
we just translated all the relevant privacy texts to German. Find the new files here and please add them to the next release:
http://www.mediafire.com/file/7vc19jvkz597wrn/enfold-4.6.3.1-privacy-de_DE.zip
We also made the translation of “privacy policy” consistent. There were three translations:
– Datenschutzerklärung
– Datenschutzbestimmung
– DatenschutzrichtlinieWe changed all of them to “Datenschutzrichtlinie”
Best regards,
JanHi @Jordan_s, as this is the fix for a bug, it would be quite nice, if you would simply ship it with the next Enfold patch ;-)
Best,
JanMight be similar to what I faced. Did you checked, that the font file names suffix (regular, italic, etc.) match what Enfold expects? We had an issue with the italic regular font file is named for the 400 weight is “regularitalic” but enfold only checks for “italic”.
See here for a fix:
Best regards,
Jan
As I only saw the hacky CSS solution, I thought it would be valuable to share the solution to *really* disable those links and not only hide them.
Just put this code in a custom Plugin (don’t hurt to create those one php file) or the functions.php of your child theme:if (!function_exists('custom_disable_avia_post_nav')) { add_filter('avia_post_nav_entries', 'custom_disable_avia_post_nav', 10, 2); function custom_disable_avia_post_nav( $entries, $settings ) { return array(); } }Hi Yigit,
thank you.
And to get this straight: I don’t really bother if you do some transformation with IDs or any other fields from the backend. But it should be the same in the avia editor as on the final rendered page :-).Jan
Hi Rikard,
one, two or many dashes is as valid as it could be… Don’t know why you believe anything else…
Why the double dash: https://csswizardry.com/2013/01/mindbemding-getting-your-head-round-bem-syntax/
BEM, as I wrote.
Please fix, best regards,
Jan
Hi Andy,
thanks for getting back to me.
I disagree with this being a Feature Request. It is kind of a severe bug for a11y as I wrote. So I would kindly ask you to flag this as a styling bug regarding the a11y guidelines and recommendations.See:
https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html
http://oregonstate.edu/accessibility/focus
https://www.nngroup.com/articles/keyboard-accessibility/I could continue…
Thanks,
Jan
