Forum Replies Created
-
AuthorPosts
-
@simonac to get the option to give a css class to almost every container this is the code (best in a child-theme functions.php) :
add_theme_support('avia_template_builder_custom_css');
than you can give a class to simple slider as well.
http://www.guenterweber.com/entwurf/wp06/trial-and-error/so here is my answer on Yigit.
before 3.02 the grid shortcode is called layout_row.php in the avia shortcodes folder.
Now its called grid_row.php
because i’m updating always via ftp i did not delete the old folder – i overwrite it – thats my fault.
And this is the reason why i got two grid rows in my template builder.here is a report of the file you mentioned.
https://www.virustotal.com/de/file/8ed540b16a53778483effd85d0b1e1298fdbb1e417119a496d87ab70e4754592/analysis/0/55 Scanners found a malware in it.
but maybe your file is hacked so try to upload it to virustotal.com and scan yourself
if you just want to display it only on a special Site than you have to put in quick css something like this:
.page-id-306 h1.av-special-heading-tag { color: #fff !important; }
it changes every special heading on the site with the id 306
no link nor screenshot – its hard to help.
October 7, 2014 at 10:08 am in reply to: Updated theme with FTP – layer slider not working properly #331445btw. i’m a participant as you so i can not see your replies
October 6, 2014 at 8:05 pm in reply to: How to make the blog posts feature images link to the post and no the image #331130i can not understand that because if you chose in Enfold options for blog-style the “Multi-Author-Blog”
than the image is linked to the single posthttp://www.guenterweber.com/entwurf/wp05/category/allgemein/
October 6, 2014 at 7:43 pm in reply to: Updated theme with FTP – layer slider not working properly #331115nö – das war nur fehlertolleranter
schöne Grüße nach Österreichthere was a bigger fault tolerance
October 6, 2014 at 7:07 pm in reply to: Updated theme with FTP – layer slider not working properly #331096do you get the linebreak in this way: ?
And btw:
In HTML, the <br> tag has no end tag.
In XHTML, the <br> tag must be properly closed, like this: <br />.
Again a great job!
The Version Two is still one of the best themes ever – and you may have all good reasons to rest on your success.
But a better Team – like yours will never do that.
My compliments.And now i have to explore the steady progress.
hey ignaziolaci
Your site is very nice ! my compliments i like those via transform rotated (:before and :after) white “bar”i got it!
forum options are nested : and this was the errorThis reply has been marked as private.This reply has been marked as private.This reply has been marked as private.thanks – for that info
can be closed nowAnd by the way – your customer doesn’t use IE 8 ?
is this for the new version of enfold an Yoast SEO obsolte? :
for functions.php
add_action('init','avia_remove_yoast_filter'); function avia_remove_yoast_filter() { remove_filter('wpseo_pre_analysis_post_content','avia_wpseo_pre_analysis_post_content_fix', 10, 1); remove_filter('wpseo_video_index_content','avia_wpseo_video_content_fix', 10, 2); }
September 10, 2014 at 11:28 am in reply to: WordPress 4.0 update causes Avia Layout Builder not to work 2 #316418you are on Version 2.9.2 of Enfold ?
This version will work proper on WP4
when will this error message be shown?
I got MacOSX Mavericks and i have never seen this message.Edit: i’m a fool – for my customer i updated to 2.92 (WP4.0 compatible) but my test environment on my server is 2.91 so forget everything.
Enfold works on 4.0 WPdear alengio – thanks this solves for me the problem that the enfold options can not be seen in total:
but with your code the toggle button on top (show all) works now!
and Sitecreation and Frontsite Changings work for me.But the bold (strong does not work in code mode) so it is a bit confusing:
so change on line 948 of wp-content/themes/enfold/framework/js/avia_colorpicker.js the inner quotes to double quotes:
from:
.filter('a[rel=' + hash + ']');
to:
.filter('a[rel="' + hash + '"]');
- This reply was modified 10 years, 2 months ago by Guenni007.
I guess Kriesi is still in work with that problem.
my advice is to get rid of the autoupdate function of WordPress by adding this to wp-config.php:define( 'AUTOMATIC_UPDATER_DISABLED', true );
i was lucky to test WP4 first to a Testenvironment and recognized the errors there first.
Thanks too!
i can not controll now if it will work on ipad.
this might be checked.here we go:
.html_header_top.html_bottom_nav_header #header_main { padding-top: 37px; z-index: 3; } #header_main_alternate { position: absolute; top: 30px; z-index: 4; width: 100% }
header-layout is “display in top-bar at the right” but i think this is not so important weather right or left
oh i see you like the social icons too.
i will have a look to get it.choose in Theme Options: Logo center, Menu below than put in Quick.css:
.html_header_top.html_bottom_nav_header #header_main { padding-top: 30px; z-index: 3; } #header_main_alternate { position: absolute; top: 0; z-index: 4; width: 100% }
if you like the navigation not centered :
.html_header_top.html_logo_center .main_menu ul:first-child { display: inline-block; max-width: 1210px; width: 100% }
if you got max width 1030px take that.
look here: http://wordpress-webdesign.org/testumgebung/
- This reply was modified 10 years, 3 months ago by Guenni007.
I never required an issue like that but because of an existing thread – which has answers of Mods i want a little clarification concerning to that old thread.
So the original Thread is closed now but the mentioned method was nice to have.
But the code there corrected by youvar childElement = document.getElementsByClassName("fixedtab")[0]; var parentElement = document.getElementsByClassName("main_color")[0];
is playing with the parentElement which leeds to some bugs.
See the example http://wordpress-webdesign.org/testumgebung/fixiertes-element/ by scrolling down.But you have all my appreciation if you don’t like to get into that code to deep.
And the thread here could be closed too.Thanks
and by the way : if you like to have a site that validates at w3c you have to create two menues and set the one to main menu and the second to footer menu even if they have the same entries, because otherwise you got to objects with the same id (this does not validate on w3c)
-
AuthorPosts