-
Search Results
-
In reply to: distortions since 2.5.1
Hi Ismael,
I am doing my best, but since it is not working properly it is a difficult task. ;-)
I have setup a new post for you, named ‘test‘. The code I have in there is this (header – testimonial – 2 dividers – header – divider – testimonial – 2 dividers – header):
[av_heading heading='Overpopulation is not a myth' tag='h5' color='meta-heading' custom_font='' style='' size='' subheading_active='' subheading_size='15' padding='10'][/av_heading]
… some Testimonial …
[av_hr class='invisible' height='50' shadow='no-shadow' position='center']
[av_hr class='invisible' height='200' shadow='no-shadow' position=‚center'] ##==> ‘200’ shouldn’t be necessary
[av_heading heading='The real question of overpopulation on planet Earth' tag='h5' color='meta-heading' custom_font='' style='' size='' subheading_active='' subheading_size='15' padding=’10'][/av_heading] ##==> this header is not visible at all
[av_hr class='invisible' height='200' shadow='no-shadow' position=‚center'] ## ==> ‘200’ shouldn’t be necessary
… some Testimonial …
[av_hr class='invisible' height='200' shadow='no-shadow' position=‚center'] ##==> ‘200’ shouldn’t be necessary
[av_hr class='short' height='80' shadow='no-shadow' position=‚center'] ##==> ’80’ shouldn’t be necessary
[av_heading heading='Interesting Stuff' tag='h3' color='meta-heading' custom_font='' style='blockquote modern-quote modern-centered' size='' subheading_active='subheading_below' subheading_size='14' padding='10']
Unique ideas, interesting correlations and findings from interdisciplinary fields will find their way into this section.
[/av_heading]Only with this extra-spacing I get a result that on a screen is somehow acceptable. However, the header in the middle [The real question of overpopulation…] is still not visible. A screenshot how it looks like can be found here: http://futuretalks.net/?p=582
If I add even more spacing, like 50 + 400 instead of 50 + 200 in the first two dividers, it happens that the missing header now does appear. – However with big spaces inbetween, and it doesn’t look great. A screenshot can be found here: http://futuretalks.net/?p=583And I am not even how ridiculous it looks on a tablet.
*****
I have noticed on several posts by now, that Enfold seems to have an issue with the combination of Testimonials, Dividers and Headers.Do you understand the issue now? Can that be helped?
Thanks for your support.
~ Katrinhi again kriesi,
– created a custom post type for recipes (with types plugin)
– copied and changed single.php and loop.php to my child theme
– later i want to integrate some custom fields to build a new layoutwhat i try to do now is to change the html to output schema.org relevant tags, what seems to happen (for example) here:
echo "<article class='".implode(" ", get_post_class('post-entry post-entry-type-'.$post_format . " " . $post_class . " ".$with_slider))."' ".avia_markup_helper(array('context' => 'entry','echo'=>false)).">";within the loop.php
may you help me to get this working?
greez
reneHey davidzack!
Are you using the blog grid layout? You can add this on functions.php to sort the order of blog posts:
add_filter('avia_post_slide_query','avia_order_by_random', 10, 2); function avia_order_by_random($query, $params) { $query['orderby'] = 'title'; $query['order'] = 'ASC'; return $query; }Regards,
IsmaelI’m using my blog as an events calendar, so I’ve used ACF to add a date picker right below the post title. I’ve updated the loop-index to display posts by that date, rather than publish date.
I’m wondering if it’s possible to do the same thing with the Blog Posts widget in the layout builder. That block seems to take the formatting edits from loop-index, but it’s still sorting by the publish date.
Thanks
In reply to: Enfold Feature Requests
@Richard Olpin +1 for your requests. Custom boxes would also help me a lot … or at least it would be helpful to be able to add custom css fields to layout elements (as requested before). But custom boxes (with option for background-color, background-image, border … ) would be even better.
And another request – I don´t know if it has been asked before. It would be nice to have a “process element” like seen here or here. I know I could use the iconlist element, but I prefer to have a horizontal display of each step. Thanks.In reply to: Open link in Lightbox/iframe
Hi Campleiter!
You can’t link the entire/slide image to an lightbox iframe popup. However you can select “Slide Link?” – “No Link” and then insert your iframe link into the slide title or description field (both fields support html code). The link must look like
<a href="http://www.google.com?iframe=true&width=100%&height=100%" rel="prettyPhoto[iframes]" title="Google.com opened at 100%">Google.com</a>and replace http://www.google.com with your url and the title and link text with your custom text. Note that you can not use the slide itself as a link if you add a link to the title/description field . otherwise you would add a link to a link and that’s not a valid html code.
Regards,
PeterIn reply to: Email "Contact" Form
Hey!
Nearly all input fields are styled with general css rules and it shouldn’t be a lot of work to implement a third party contact form. I installed Formidable on my website and it looks like the default contact form with just a few custom css rules.
Cheers!
PeterIn reply to: Custom Menu
Thank you so much!! That really helped a lot.
My the way, is there anywhere that the user can log into the system without going to /wp-admin/ or /login/?
I’d like to create a field that the user already have the text fields and password fields to log into the website without going to any of those url just like the search button!!!
In reply to: Add custom field to portfolio item
Hi epresley!
You can use custom fields in different ways and I don’t think it will be added on the theme anytime sooner. Maybe you can try these plugins:
http://wordpress.org/plugins/advanced-custom-fields/
http://wordpress.org/plugins/custom-field-suite/
Regards,
IsmaelHow do I add a custom field to an Enfold portfolio item? I searched in the WP screen options but can’t find how to enable it. Custom fields are enabled in ordinary WP posts.
If such an option doesn’t exist are you considering adding custom fields into an Enfold portfolio item?Hello, I have a custom form to allow users to post from the front end to a custom post type (pending).
The form function perfectly well on other themes (I have tested on other themes I have written). The form also works fine if I include the enfold header but comment out the include for the footer. Similarly, the form works if I comment out the header but include the footer. So whats the problem….well, when both header and footer are included the form does not post.
Any ideas as to what in the theme could be prevent normal functionality?
Here is my form:
<div class="entry-content-wrapper clearfix" style="border: solid 0px black"> <form class="avia_ajax_form" method="POST" form id="new_post" name="new_post" method="post" action="" enctype="multipart/form-data"> <fieldset style="border: 0px;"> <p id="IGN" class="form_element_half"> <label for="offender_ign" placeholder="IGN">Offender IGN <abbr title="required" class="required">*</abbr></label> <input id="offender_ign" type="text" value="" tabindex="5" name="offender_ign" class="text_input is_empty"> </p> <p id="type_of_offence" class="form_element_half_2 form_element_half"> <!--<label for="cat">Type:</label> <?php wp_dropdown_categories( 'tab_index=10&taxonomy=portfolio_entries&hide_empty=0' ); ?> --> <label for="type_of_offence">Type of Offence</label> <select id="type_of_offence" class="select " name="category"> <?php // ======= Custom post types category drop down ======== $taxonomy = 'portfolio_entries'; $terms = get_terms($taxonomy); // Get all terms of a taxonomy if ( $terms && !is_wp_error( $terms ) ) : foreach ( $terms as $term ) { echo '<option value="' . get_term_link($term->slug, $taxonomy) . '">' . $term->name . '</option>'; } endif; ?> </select> </p> <p id="element_description"> <label for="description" class="textare_label hidden textare_label_avia_description">Description</label> <textarea id="description" rows="7" cols="40" class="text_area " name="description"></textarea> </p> <p id="element_image_upload"> <label for="image_upload">Image Upload</label> <input id="image_upload" type="file" value="" class="text_input" name="image"> </p> <p id="element_tags"> <label for="post_tags">Tags <small>(Comma Separated List)</small></label> <input id="post_tags" type="text" value="" class="text_input " name="post_tags"> </p> <p id="hidden_submit"> <input type="hidden" name="form" value="1"> <!-- on click, do wordpress action new_post --> <input type="submit" class="button" name="submit" value="Submit"> </p> <!-- ensure post is coming from site and not elsewhere --> <input type="hidden" name="action" value="new_post" /> <?php wp_nonce_field( 'new-post' ); ?> </fieldset> </form> </div>The form functions:
<?php if( 'POST' == $_SERVER['REQUEST_METHOD'] && !empty( $_POST['action'] ) && $_POST['action'] == "new_post") { // Do some minor form validation to make sure there is content if (isset ($_POST['offender_ign'])) { $title = $_POST['offender_ign']; } else { echo 'Please enter the In Game Name (IGN) of the offender'; } if (isset ($_POST['description'])) { $description = $_POST['description']; } else { echo 'Please enter some notes about the hate speech'; } $tags = $_POST['post_tags']; // ADD THE FORM INPUT TO $new_post ARRAY $new_post = array( 'post_title' => $title, 'post_content' => $description, 'post_category' => array($_POST['category']), // Usable for custom taxonomies too 'tags_input' => array($tags), 'post_status' => 'pending', // Choose: publish, preview, future, draft, etc. 'post_type' => 'portfolio' //'post',page' or use a custom post type if you want to ); //SAVE THE POST $pid = wp_insert_post($new_post); //SET OUR TAGS UP PROPERLY wp_set_post_tags($pid, $_POST['post_tags']); // Image handling if ($_FILES) { foreach ($_FILES as $file => $array) { $newupload = insert_attachment($file,$pid); // $newupload returns the attachment id of the file that // was just uploaded. Do whatever you want with that now. } } //REDIRECT ON SAVE $link = "/success"; wp_redirect( $link ); } // END THE IF STATEMENT THAT STARTED THE WHOLE FORM //POST THE POST YO do_action('wp_insert_post', 'wp_insert_post'); ?>Hi, I would like a little help in making some final changes for the website http://hbjcapital.wpengine.com/ (hosted on WPengine)
1. I would like to have each post in the grid layout to have a light grey background so that it appears distinct, just like you see in the featured post below the layer slider.
2. When the user clicks on “customer login” in the top right in the thin blue bar, a pop-up should display just like the search function pop-up, which will have fields for username and password. The field should then pass the data to the same fields on soft.hbjcapital.net and upon validation, open the userportal at soft.hbjcapital.net in a new tab. I do not like how its opening in the frame now.
3. Also, how do i hide a featured post from appearing in the grid layout below it, as you can see the featured post also appears as the 1st entry in the grid.
Please have these answered soon. Thanks :)
Hi, on this page: http://www.familybudgeting.org.nz/members/order-form I have a resource order form, with drop down boxes using the Gravity Forms “enhanced user interface”. (See question 3, “Your budgeting service”)
In these drop down fields (and only these) the width is being set to extremely narrow.
I’ve tried overruling it with custom CSS but can’t work it out; it seems to be generated by javascript? This makes me think the Gravity Forms javascript is conflicting with the Enfold javascript – or something.
Clearly I’m not sure if it’s an Enfold issue or something else, but any help would be appreciated.
Cheers,
Mike
In reply to: Targeting Rows in Avia Layout Builder for Markup
Thanks Devin. I was able to use a combination of color sections and custom class fields using the link you posted to get the desired effect. The only minor issue I am having is finding enough elements to wrap a text block in a design that has a top background, a middle background, and a bottom background. I’m trying to insert another div within the body of the text block and absolute position it, but am having minimal luck.
#sub_slider .je_block_bottom { background: url("images/bg_get_estimate_bottom.png") no-repeat scroll center bottom rgba(0, 0, 0, 0); bottom: -45px; color: #967C68; min-height: 55px; padding: 10px 5px 5px 30px; position: absolute; width: 100%; }The text block I’m working on is called “Get An Estimate”
http://heartland.estlandpreview2.com/Hi,
I am using the post slider to display posts with a certain taxonomy and in each post there are a number of custom fields. I would like to be able to display one of these customer fields in the post slider output. I understand I will have to edit the query but am wondering how to do this without editing the theme files direct. I have a child theme set up and am using that for css and other edits, so any direction you could provide would be appreciated.
The custom field is called ‘cost’ and display a price for an event that I would like to be able to display
Thanks
Hi
I have written before, asking for help but you just gave me a link to a tutorial and closed my topic thread.
Believe me, I have tried for weeks to get it working but cannot. So it seems you dont help for customisations.
If you are not willing to assist can you please put me in touch with a developer who is willing to show me how to link a portfolio masonry display to a page instead of a post, all the while keeping the images in a relatively fixed size grid of 2 rows of 4 images all sized 220 x 146.
You seemed to say in previous thread that it was possible to link to a page but I had to use a css.
I have no skills with css in this regard, and the settings in your video tutorial, do not explain how to configure the right settings for my needs, I dont know which drop down fields to select, let alone know what css has to be added.My request is really quite simple: I want to create a grid with 2 x rows of 4 small images that stay small and do nothing except link to pages, in the fashion that is displayed in the Portfolio Masonry demo,
Each image should not pop up or expand but when mouse hovers, allow for text to show – as per masonry demo, and then it should provide link to internal pages.
Please look at this url http://www.atuawahine.com/wp/ … it is displaying two methods- at the top I have added a masonry gallery and I added 8 images with links to the required 8 pages. however, two things are badly wrong; the images are getting tiled repeating across page and there is no hover text.
Looking at my above URL, the display below the messed up gallery is just a basic 4 columns with images, which I was able to link it to a page. However, it does not show text on mouse over, either, and when I view this site in a mobile, its hopeless because no one will ever know what the image is there for, nor what it links to. We didnt want to split the gallery up with fixed text blocks, we just want the portfolio masonry demo! Is that not possible?
Thanks
GillianHello, kriesi-Team!
I have some issues with LayerSliderWP on a Multisite WordPress installation.
What i’ve done:
First i’ve created one site.
After that i’ve created 2 copies of this with MultilingualPress Pro Plugin from inpsyde (marketpress.com). Screenshot: http://goo.gl/ulCyDa
After the copies were created, LayerSlider WP doesn’t get sliders the origin site had. Okay, not a problem: i’ve exported Sliders and imported them into other 2 sites.Here are the screenshots:
Site 1: http://goo.gl/YADLDk
Site 2: http://goo.gl/FGaIuK
Site 3: http://goo.gl/y7RH03Each site has unique layerslider id’s.
- Issue
For example if i assign “(DE) Startseite (All-in-One)Slider” to Frontpage of Site 1 (with Avia Layout Builder – like this http://goo.gl/GrddBs), and after that i assign “(CN) Startseite (All-in-One)Slider” to Frontpage of Site 3 (like this http://goo.gl/gPo5WB). If i then revisit Frontpage of Site 1, i get this error: “[LayerSliderWP] Slider not found”.
In other word i don’t have a possibility to use more as 3 slider’s and i need 9 of them – for each Site 3 Sliders.
Can you please help me get rid off it?
P.S. i think it’s happening because the Layerslider isn’t Multisite-ready. Here i found an interesting article: http://marketpress.com/2013/how-to-update-custom-fields-in-a-multi-site/, which maybe can help you to change code of LayerSlider.
In reply to: Background-Color for avia layout element
Hi pelyon!
You can turn on custom css fields for all of the layout elements and then add a class with a background color: http://kriesi.at/documentation/enfold/turn-on-custom-css-field-for-all-alb-elements/
For example: add the class name custom-red-background to the new field and then this css to your Quick CSS:
.custom-red-background { background-color: #F00; }Regards,
DevinIn reply to: Text form fields in footer widgets styling issue
This is how it looks for me:
I added the code you provided, but it didn’t change the color. (It did change the alignment of the boxes though so I removed the lines about the width because I had already set these to a custom value.) I’m on a Mac, and it looks the same in Firefox, Safari, and Chrome. Also looks the same from my iPhone and iPad. (Apparently I only have access to Apple products for testing…) :/
In reply to: Text form fields in footer widgets styling issue
Hi sharonreiley!
I don’t see the difference between the fields except for the border. Please add this on your custom.css or Quick CSS:
#top .input-text, #top input[type="text"], #top input[type="input"], #top input[type="password"], #top input[type="email"], #top input[type="number"], #top input[type="url"], #top input[type="tel"], #top input[type="search"], #top textarea, #top select { -webkit-appearance: none; border: none; padding: 8px 6px; outline: none; font: 13px "HelveticaNeue", "Helvetica Neue", Helvetica, Arial, sans-serif; color: #777; margin: 0; width: 210px; max-width: 100%; display: block; margin-bottom: 20px; background: #fff; border-radius: 0px; }Best regards,
IsmaelTopic: Portfolio Grid – Taxonomie
Dear Team Kriesi,
When I’m implementing a portfolio grid to my site, I have the option to select my categories that I would like to show in the portfolio grid (section: “Which categories should be used for the portfolio?”). At the moment, I just have to possibility to select categories. Is it also possible to change from categories to my own setup taxonomy I’ve created.
I’m creating my taxonomy with the help of “WCK – Custom Fields and Custom Post Types Creator” plugin.Thanks and best regards,
SilberrotIn reply to: Enfold Feature Requests
First of all I have to say Enfold is the best theme I ever worked with. You do an awesome job!
While working with the theme I came over two issues causing me some headaches and a serious amount of time to solve. I think this issues can arise for a lot of customers and a future update should take this into account.
1. The form builder included in Enfold is great for some smaller contact or feedback forms. However if you need advanced features like file upload or special field conditions you need to use 3rd party plugins as recommended by the Kriesi Team. I tried a few but was not satisfied with the output. The main issue is the CSS declaration for any kind of form fields in Enfolds base.css. Finally i had to use a child theme, use a modified base.css which has to be loaded from a modified function.php. While this is possible it might be to difficult for many users. My suggestion: move the CSS definition for forms into a separate css file and introduce a checkbox in the theme options to disable loading of this css styles.
2. The team member element included with Enfold is nice but due to the fact it is only page oriented (versus a custom post type available globally) forced me to use a 3rd party solution. All the plugins I tested have one thing in common: they makes use of single page settings (single vs. page). Because Enfold does not have global settings for single.php any plugin using it will display the site with header (breadcrumbs, title) and sidebar. If you dont want that you have to write your own single-xxx.php file and put it into a child theme. This might be to complicated for most users as you have to even write your own loop code depending what design you want. And getting the right CSS classes gives you a hard time. My suggestion: Introduce a single setting (for individual posts) that differ from the ‘single blog post’ settings. There are many plugins out there which use the single-xxx.php to display content.
Keep on the fantastic work!
Regards
Michael
Hello!
This is the page: http://www.adw.cl/contacto/
I am using contact form from Enfold Theme and have a few questions:
1. I am not receiving the autorespond mail. I think maybe has to do with the hosting, so I contacted them and hope to have news tomorrow. I understand only having a Autorespond text, this is the expected behaviour, if not, please tell me.
2. Is it possible to have some ‘advanced’ html in the autorespond text? For example images and custom fields (like the name of the person who contacted). Or some predefined page?
3. Confirmation message style is not attractive, it’s just a text in a blank page. Is it possible to have a predefined html or load a page for the confirmation message?If the answer to one of the questions above is negative, do you recomend some plugin that can do that in an easy way to configure?
Thanks a lot!!
Regards
JoséEverything was working just fine when it suddenly stopped attaching properly images or setting as featured.
Actually there are the following certain symptoms:
-When creating a new post:
1.via the add Media button process i select and upload a new image with the thumbnail showing properly and when i press insert into post/insert gallery a blank media box appears in the post’s textbox.
2.when i try to set a new featured image (one that is newly uploaded or one of the old images) the bottom right ‘set featured image’ widget looks like no image is selected or set. I click “set as featured image” and the modal closes but the image never appears.
-When I try to browse my Media>Library any newly uploaded image is blank with no thumbnail available and no image file appearing when clicking view (via the ‘domain/?attachment_id=…’ link).
-When browsing my ftp server directory or typing the url ‘domain/wp-content/uploads/2013/3/image.jpg’ the images are appearing just fine.
-Any images that I upload I can see in the media browser but their thumbnails there aren’t cropped like normal, it’s a thumbnail of the entire image where normally (and previously uploaded images) it’s cropped. They also don’t have pixel dimensions listed like other images do.This is causing a major problem on a busy e-commerce site. I’ve seen others with the same issue who said it was fixed when they disabled the “Advanced Custom Fields” plugin, but I don’t have that plugin.
I did not make any changes to anything, no new plugins, no updates. It worked fine in one product listing, then I went to the next one and it stopped and now won’t work for any.
I’m wondering if the advanced custom fields plugin or something similar is integrated into the theme and could be causing this strange issue.
Hello,
I hoping for some guidance on using the “portfolio grid” function as a “related projects” element. Works beautifully except it includes the item that the page is about. For example, on the page link below, The Natai is the project but is also referenced as related. Any thoughts on how to remove portfolio items from showing up without removing the category. I’ve set up custom fields on the register-portfolio.php page in hopes there is something that could be done though that. Thanks so much for any assistance you can provide.
http://paulraffstudio.wpengine.com/portfolio-item/the-natai/ (hosted on WPengine)
Hi Ismael
Thanks for your early reply.
I did not set responsive layout.
The width of image looks correct, but the width of text does not correct.
[My custom CSS is below]
/*나눔고딕 웹폰트 적용*/
@import url(http://fonts.googleapis.com/earlyaccess/nanumgothic.css);
html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video, tr.pricing-row td, #top .portfolio-title, .callout .content-area, .avia-big-box .avia-innerbox, #top select, #lang_sel, .gm-style div {
font-family: ‘Nanum Gothic’, Open Sans, ‘HelveticaNeue’, ‘Helvetica Neue’, Helvetica, Arial, sans-serif;
}/*archive 등등의 폰트*/
#top .input-text, #top input[type=”text”], #top input[type=”input”], #top input[type=”password”], #top input[type=”email”], #top input[type=”number”], #top input[type=”url”], #top input[type=”tel”], #top input[type=”search”], #top input[type=”file”],#top textarea {
font-family: ‘Nanum Gothic’, Open Sans, ‘HelveticaNeue’, ‘Helvetica Neue’, Helvetica, Arial, sans-serif;
font-size: 12px;
}#top input[type=”submit”] {
text-transform: uppercase;
}/*body background-color*/
#main, .html_stretched #wrap_all {
background-color: #ffffff;
}/*헤더 좌우 그림자 안보이게*/
.boxed#top {
overflow: hidden;
}/* 헤더메인로고 사이즈 및 위치 */
.logo img {
padding: 0px 0px;
display: block;
width: auto;
height: auto;
max-height: 74px;
hack: fixes ie8 logo;
}/* 뉴스보기화면 좌측상단 특성이미지크기*/
.single-post .single-small.with-slider .small-preview {
width: 80px;
height: 80px;}/* 헤더높이와 메뉴위치*/
#header_main .container, .main_menu ul:first-child > li > a {
height: 90px !important;
line-height: 90px !important;
}
html.fixed_header #main {
padding-top: 120px;
}
.main_menu {
margin-right:-13px;
}/*헤더디자인 ————————————–*/
#header {
margin-bottom: -10px;
}.header_color .header_bg {
background: transparent url(http://interpeople.co.kr/wp/wp-content/uploads/2013/11/shadow_below.png) bottom center no-repeat scroll;
}#header_main {
border-width:0px;
padding-top: 5px;
padding-bottom: 10px;
}#header_meta {
background-color: transparent !important;
padding-bottom: 3px;
padding-top: 8px;
}#top .social_bookmarks {
height: 30px;
z-index: 150;
-webkit-backface-visibility: hidden;
margin: 0 0 0 -9px;
/*background-color: white;*/
border-radius: 3px;
}/*——————————————-*/
/*풀다운 서브메뉴 바탕색*/
.header_color .main_menu .menu ul li a {
background-color:#ffffff;
}/* 메인메뉴폰트*/
.main_menu ul:first-child > li > a {
display: block;
text-decoration: none;
padding: 0 13px;
font-weight: 600;
font-size: 16px;
}/*메뉴하단 선택바 위치*/
.avia-menu-fx {
bottom: -1px;
}/*메뉴하단 선택바 화살표*/
.avia-menu-fx .avia-arrow-wrap {
display: block;
}/*토글탑메뉴색상*/
#advanced_menu_toggle, #advanced_menu_hide {
background-color: #FFFFFF;
color: #333333;
border-color: #B4B4B4;
}/*탑메뉴바 검색없애기*/
#top #menu-item-search {
z-index: 100;
display: none;
}/*최상단 소셜 서브메뉴 높이와 색상*/
#header_meta {
border-width: 0px;
box-shadow: inset 0px 0px 0px 0px rgba(0, 0, 0, 0.2);
z-index: 400;
min-height: 32px;
background-color: #999999;
}
/*최상단 sub메뉴 우측공간*/
.sub_menu {
right: 0px;
}/*최상단 sub메뉴 폰트*/
.header_color .sub_menu>ul>li>a {
color: #333333;
font-size: 12px;
font-weight: normal;
}
.header_color .sub_menu ul:first-child > li.current-menu-item > a {
color: #333333;
font-weight: 800
}.mapp-layout {
margin: 0px;
padding: 0px;
}/*최상단 소셜 아이콘 안보이게*/
#top .social_bookmarks li a,
#top .social_bookmarks li {
display: none;
}
.responsive #header_meta .social_bookmarks li {
visibility: hidden;
}/*AJAX포트폴리오 제목 하단*/
.portfolio-preview-title {
margin-bottom: 30px;
}/*헤더 네비——————————-*/
/*헤더 네비 안보이게*/
#main .title_container {
display:none;
}/*헤더 네비 you are here 안보이게*/
.breadcrumb-title {
visibility: hidden;
}/*헤더 네비 Archive for category 안보이게*/
.title_container .main-title {
visibility: hidden;
}/*헤더 네비 높이*/
#top .title_container .container {
padding: 0px 0;
min-height: 36px;
}/*헤더 네비 위치*/
.title_container .breadcrumb {
top: 70%;
}
/*———————————————–*//*포스트 제목 밑의 카테고리와 작성자 안보이게*/
span.blog-author.minor-meta {
display: none;
}/*사용후기 제목*/
.main_color .first-quote {
color: #222222;
}
blockquote {
font-weight: 700;
}/*사용후기 페이지에서*/
.avia_button_icon {
color: #ffffff;
}
.avia_iconbox_title {
color: #ffffff;
}/*promobox margin*/
.av_promobox {
margin: 10px 0;
}/*레이어슬라이더 스톱버튼 위치*/
#top .ls-nav-start, #top .ls-nav-stop {
top: -50px;
}/*drop shadow—-text block—-폴리몰리메인———-*/
#pollimolli_submenu_1 .avia_textblock
{
position: relative;
width: 100%;
background: #fafafa;
-moz-border-radius: 0px;
border-radius: 0px;
padding: 1.3em;
color: rgba(0,0,0, .8);
text-shadow: 0 1px 0 #fff;
line-height: 1.3;
margin: 0px auto;
-webkit-perspective: 0;
box-shadow: 0px 2px 5px 0px rgba(0, 0, 0, 0.1);
}#pollimolli_submenu_1 .avia_textblock:before, #pollimolli_submenu_1 .avia_textblock:after
{
z-index: -1;
position: absolute;
content: “”;
bottom: 15px;
left: 10px;
width: 46%;
top: 80%;
max-width:300px;
background: rgba(0, 0, 0, 0.7);
-webkit-box-shadow: 0 15px 15px rgba(0,0,0, 0.7);
-moz-box-shadow: 0 15px 15px rgba(0, 0, 0, 0.7);
box-shadow: 0 15px 15px rgba(0, 0, 0, 0.7);
-webkit-transform: rotate(-3deg);
-moz-transform: rotate(-3deg);
-o-transform: rotate(-3deg);
-ms-transform: rotate(-3deg);
transform: rotate(-3deg);
}#pollimolli_submenu_1 .avia_textblock:after
{
-webkit-transform: rotate(3deg);
-moz-transform: rotate(3deg);
-o-transform: rotate(3deg);
-ms-transform: rotate(3deg);
transform: rotate(3deg);
right: 10px;
left: auto;
}/*—————————————–*/
/*drop shadow——-portfolio grid————————–*/
.grid-image
{
position: relative;
width: 100%;
background: #ffffff;
-moz-border-radius: 0px;
border-radius: 0px;
padding: 0em;
color: rgba(0,0,0, .8);
/!–text-shadow: 0 1px 0 #fff;–/
line-height: 1.3;
margin: 0px auto;
-webkit-perspective: 0;
box-shadow: 0px 2px 5px 0px rgba(0, 0, 0, 0.1);
}.grid-image:before, .grid-image:after
{
z-index: -1;
position: absolute;
content: “”;
bottom: 15px;
left: 10px;
width: 50%;
top: 80%;
max-width:300px;
background: rgba(0, 0, 0, 0.7);
-webkit-box-shadow: 0 15px 10px rgba(0,0,0, 0.5);
-moz-box-shadow: 0 15px 10px rgba(0, 0, 0, 0.5);
box-shadow: 0 15px 10px rgba(0, 0, 0, 0.5);
-webkit-transform: rotate(-3deg);
-moz-transform: rotate(-3deg);
-o-transform: rotate(-3deg);
-ms-transform: rotate(-3deg);
transform: rotate(-3deg);
}.grid-image:after
{
-webkit-transform: rotate(3deg);
-moz-transform: rotate(3deg);
-o-transform: rotate(3deg);
-ms-transform: rotate(3deg);
transform: rotate(3deg);
right: 10px;
left: auto;
}
/*————————————————–*//*shadow——-why폴리몰리———-*/
.page-id-4558 .avia_image{
box-shadow: 0px 2px 5px 0px rgba(0, 0, 0, 0.1);
}/* 포트폴리오 그리드 하단 에로우 및 배경*/
#av_section_1 .avia-arrow {
visibility: hidden;
}/* 포트폴리오 그리드 하단 제목 배경*/
.main_color .grid-content, .main_color .grid-entry-title, .grid-entry .main_color .avia-arrow {
background-color: transparent;
}/* 포트폴리오 타이틀 배경*/
.grid-entry .inner-entry {
background-color: transparent;
}/*————————————————————————————————–*/
/* 포트폴리오 그리드 하단 제목 폰트*/
.grid-entry-title .grid-entry-excerpt {
font-size: 12px;
margin: 0;
padding: 0;
font-weight: normal;
text-align: ;
}/* 포트폴리오 그리드 배열 및 그림자*/
.grid-entry .inner-entry {
margin-top: 10px;
margin-left: 10px;
margin-right: 10px;
margin-bottom: 10px;
box-shadow: 0px 0px 0px 0px rgba(0, 0, 0, 0.4);
position: relative;
}/* 포트폴리오 그리드 하단 패딩*/
.grid-content {
padding: 11px;
position: relative;
}/*카테고리 필터링————————————–*/
#js_sort_items a {
display: block;
float: left;
text-decoration: none;
background-color: #666666;
border-radius: 2px;
padding-left: 5px;
padding-right: 5px;
text-shadow: 0 0px 0 rgba(255, 255, 255, 0.1);}
/*카테고리 필터링 텍스트 색상*/
.alternate_color #js_sort_items a, .main_color #js_sort_items a {
color: #ffffff;
font-size: 12px;
font-weight: normal;
}/*카테고리 필터링 텍스트 색상_hover*/
.alternate_color #js_sort_items a:hover, .main_color #js_sort_items a:hover {
color: #e1e1e1;
}/*카테고리 필터링 텍스트 색상_active*/
.alternate_color #js_sort_items a.active_sort, .main_color #js_sort_items a.active_sort {
color: #ffffff;
background-color: #a81010;
}/*카테고리 필터링 슬러시 안보이게*/
#js_sort_items .text-sep {
padding: 0 1px;
visibility: hidden;
}
/*——————————————————–*//*pollimolli 페이지에서 글자가 사진 밑으로 안들어가게*/
.pollimolli_submenu_1 p {
overflow: hidden;
}/*pollimolli 페이지에서 */
#pollimolli_submenu_1 {
border-width:1px;
}/*pollimolli 메인페이지 서브메뉴—————————– */
#pollimolli_submenu_2 {
min-height: 50px;
text-align: center;
border-width:0px;
}#pollimolli_submenu_2 .entry-content a:hover {
opacity: 0.7;
}
/*——————————————————–*/.page-id-2554 .entry-content li {
margin-left: 0em;
padding: 30px 0;
}/*rss 위젯 이미지*/
.widget_rss .widgettitle img {
display: block;
float: left;
margin-right: 4px;
margin-top: 1px;
}
.rsswidget {
margin-top: 3px;
}
.rss-date, .widget_rss cite {
font-size: 10px;
}/*풋터 위젯 폰트*/
.footer_color .news-time {
color: #b3b3b3;
}
.footer_color .rss-date {
color: #b3b3b3;
}
.widgettitle {
letter-spacing: 0px;
}
#footer .widgettitle {
color: #ffffff;
}
.footer_color div .news-headline{
color: #dddddd;
font-weight: normal;
}
.footer_color .footer-social-name a{
color: #dddddd;
font-size:11px;
}/*
.footer_color {
background-color:#222222;
border-color:#444444;
}
.footer_color img{
border-color:#444444;
}
.socket_color {
background-color:#333333;
border-color:#444444;
}
*//*갤러리 메인이미지 패딩*/
#top div .avia-gallery .avia-gallery-big {
padding:0px
}
#top div .avia-gallery img {
padding:0.3em
}/*폴리몰리 제품 메뉴 슬라이더 텍스트*/
.ls-s-1 {
font-size: 12px;
font-weight: bold;
color: #222222;
}/*shareaholic page에서*/
.shareaholic-share-buttons-container ul.shareaholic-share-buttons {
overflow-x: visible !important;
overflow-y: visible !important;
}/*tab에서 스크롤 안보이게
.js_active .active_tab_content {
overflow:hidden;
}*//*폴리몰리 제품메뉴에서 hover효과*/
#layerslider_9 img:hover {
opacity:0.7;
}/*지플렉스 메인*/
.page-id-2565 td {
font-size:12px;
}
.page-id-2565 .avia-shadow {
box-shadow: inset 0 0px 0px rgba(0, 0, 0, 0.1);
}
#zflex_submenu_1 {
border:none;
}
#zflex_submenu_2{
min-height: 50px;
text-align: center;
border-width:0px;
}
#zflex_submenu_2 .entry-content a:hover {
opacity: 0.7;
}/*지플렉스 사용설명서*/
#flipbook-container-0 div.page-content.even div.container img.bg-img {
left: 0px !important;
}
#flipbook-container-0 div.page-content div.container img.bg-img {
margin-top: 0px !important;
}
#flipbook-container-0 div.page-content.last div.container img.bg-img {
left: 0px !important;
}
#flipbook-container-0 li{
vertical-align: bottom !important;
}
#flipbook-container-0 .container {
position: static;
}
#flipbook-container-0 .zoomed-shadow {
left: 45px !important;
top: 9px !important;
width: 820px !important;
height: 566px !important;
}/*mainmenu–KO———————————————————————————————*/
.main_menu ul:first-child > li > a {
display:block;
background:url(http://interpeople.co.kr/wp/wp-content/uploads/2013/09/logo_menu_bg_grey.png) no-repeat top;
}/*PolliMolli*/
#menu-item-6440 > a:hover,
#menu-item-6440.current-menu-item > a,
#menu-item-6440.current_page_item > a,
#menu-item-6440.active-parent-item > a,
#menu-item-6440.active-ancestor-item > a {
background:url(http://interpeople.co.kr/wp/wp-content/uploads/2013/09/logo_menu_pollimolli_blue.png) no-repeat top; display:block;
}/*zflex*/
#menu-item-6451 > a:hover,
#menu-item-6451.current-menu-item > a,
#menu-item-6451.current_page_item > a,
#menu-item-6451.active-parent-item > a,
#menu-item-6451.active-ancestor-item > a {
background:url(http://interpeople.co.kr/wp/wp-content/uploads/2013/10/logo_menu_zflex_black.png) no-repeat top; display:block;
}/*MINI*/
#menu-item-6455 > a:hover,
#menu-item-6455.current-menu-item > a,
#menu-item-6455.current_page_item > a,
#menu-item-6455.active-parent-item > a,
#menu-item-6455.active-ancestor-item > a {
background:url(http://interpeople.co.kr/wp/wp-content/uploads/2013/09/logo_menu_mini_color.png) no-repeat top; display:block;
}
/*————————————————————————————*//*mainmenu–EN———————————————————————————————*/
.main_menu ul:first-child > li > a {
display:block;
background:url(http://interpeople.co.kr/wp/wp-content/uploads/2013/09/logo_menu_bg_grey.png) no-repeat top;
}/*PolliMolli*/
#menu-item-5729 > a:hover,
#menu-item-5729.current-menu-item > a,
#menu-item-5729.current_page_item > a,
#menu-item-5729.active-parent-item > a,
#menu-item-5729.active-ancestor-item > a {
background:url(http://interpeople.co.kr/wp/wp-content/uploads/2013/09/logo_menu_pollimolli_blue.png) no-repeat top; display:block;
}/*zflex*/
#menu-item-5741 > a:hover,
#menu-item-5741.current-menu-item > a,
#menu-item-5741.current_page_item > a,
#menu-item-5741.active-parent-item > a,
#menu-item-5741.active-ancestor-item > a {
background:url(http://interpeople.co.kr/wp/wp-content/uploads/2013/10/logo_menu_zflex_black.png) no-repeat top; display:block;
}/*MINI*/
#menu-item-5745 > a:hover,
#menu-item-5745.current-menu-item > a,
#menu-item-5745.current_page_item > a,
#menu-item-5745.active-parent-item > a,
#menu-item-5745.active-ancestor-item > a {
background:url(http://interpeople.co.kr/wp/wp-content/uploads/2013/09/logo_menu_mini_color.png) no-repeat top; display:block;
}
/*————————————————————————————*//*메인메뉴의 드롭다운메뉴 폰트*/
.header_color .main_menu .menu ul li a {
color:#555555 ;
}/*메인메뉴의 폴리몰리 빈백컬렉션 sub-menu 안보이게_한국어*/
#menu-item-6461 .sub-menu {
display:none !important;
}/*메인메뉴의 폴리몰리 빈백컬렉션 sub-menu 안보이게_영어*/
#menu-item-6573 .sub-menu {
display:none !important;
}/*월별찾아보기*/
#top select {
font-size:11px !important;
line-height:15px !important;
}/*사이드보더*/
.content {
border-color: #e1e1e1;
}/*게시물페이지 메타이미지 안보이게*/
.template-single-blog .blog-meta {
display: none;
}
.big-preview.single-big {
display: none;
}/*사이드바 폭 조정*/
.inner_sidebar {
margin-left: 30px;
}
.content .entry-content-wrapper {
padding-right: 30px;
}#facebook-like-box-2 {
margin-left: -10px;
}
#facebook-like-box-2 .fb_iframe_widget span {
height: 627px !important;
width: 232px !important;
}
#facebook-like-box-2 .fb_iframe_widget iframe {
height: 627px !important;
width: 232px !important;
}
#facebook-like-box-3 {
margin-left: -10px;
}
#facebook-like-box-3 .fb_iframe_widget span {
height: 627px !important;
width: 232px !important;
}
#facebook-like-box-3 .fb_iframe_widget iframe {
height: 627px !important;
width: 232px !important;
}/*소식골라보기*/
#categories-2 {
font-size: 12px;
}/*회사소개*/
.page-id-1195 .av-special-heading {
margin-top:10px;
}
.page-id-1195 .togglecontainer {
margin-top:10px;
}/*회사소개 en*/
.page-id-5236 .av-special-heading {
margin-top:10px;
}
.page-id-5236 .togglecontainer {
margin-top:10px;
}
.page-id-5236 .togglecontainer pre {
padding:0px;
margin-bottom: 10px;
}/*shop메뉴 안보이게 할 때 메뉴바 우측의 장바구니위젯도 안보이게*/
.cart_dropdown {
display:none;
}/*Why폴리몰리 페이지 서브메뉴 제목*/
.page-id-4588 .template-page .entry-content-wrapper h2 {
text-transform: none;
letter-spacing: -1px;
}
/*빈백컬렉션 신장안내 문자*/
.iconbox .iconbox_content .iconbox_content_title {
letter-spacing: 0px;
text-transform: none;
}/*포트폴리오 신장안내*/
.template-page .entry-content-wrapper h1, .template-page .entry-content-wrapper h2 {
text-transform: none;
letter-spacing: -1px;
}/*iconlist title*/
.avia-icon-list .iconlist_title {
text-transform: none;
}/*contact en 입력란*/
.page-id-5247 #top .input-text, #top input[type=”text”], #top input[type=”input”], #top input[type=”password”], #top input[type=”email”], #top input[type=”number”], #top input[type=”url”], #top input[type=”tel”], #top input[type=”search”], #top textarea, #top select {
width:100%;
}
.page-id-5247 .av_two_third{
background-color: whitesmoke;
padding: 25px;
}/*contact ko 입력란*/
.page-id-2641 #top .input-text, #top input[type=”text”], #top input[type=”input”], #top input[type=”password”], #top input[type=”email”], #top input[type=”number”], #top input[type=”url”], #top input[type=”tel”], #top input[type=”search”], #top textarea, #top select {
width:100%;
}
.page-id-2641 .av_two_third{
background-color: whitesmoke;
padding: 25px;
}/*filling 페이지에서 비교테이블 편집페이지 디버그 코드에서 avia-heading-row 클래스를 epp와 eps로 수정후*/
.main_color .pricing-table li.epp {
background-color: #eb008b;
color: white;
font-weight: 800;
font-size: 13pt;
}
.main_color .pricing-table li.eps {
background-color: #999999;
color: white;
font-weight: 800;
font-size: 13pt;
}
.main_color .pricing-table li.epp-1 {
background-color: #eb008b;
color: white;
font-weight: normal;
font-size: 11pt;
}
.main_color .pricing-table li.eps-1 {
background-color: #999999;
color: white;
font-weight: normal;
font-size: 11pt;
}
/*——————————————————————————————-*/Hi,
I am using FormidablePRO for my forms which I really need to keep using it.
I was using Choices theme and you gave me the following code to fix some issues with the CSS:/* fix the formidable problem */ .flex_column .frm_form_fields br{display:none;} .ui-datepicker-month, .ui-datepicker-year{ min-width: 0 !important; padding: 0 !important; }I found the following code which solved me the breaklines:
#top .frm_forms label { display: inline; }But I still need more help to make this: http://d.pr/i/iwc5/5hTP676R to look like http://d.pr/i/10NO/3MwjJGUN
They are both the same form. The first on Enfold, the second on Choices with custom CSS.
I can send you the URL of the website in PM or by email.
Thank you.
In reply to: Alt text not appearing in source code
Peter,
Thank you so much for the code. It worked great. I edited the main file in the /enfold theme and not my child theme.
Can you put the masonry_entries.php page in the child theme and the site will still work? This will help with updating. I reckon I could just try it and see, but I seem to recall that I tried this with another core php file and it didn’t work. Only headers, footers, function.php seem to be recognized. I am not a newbie coder, but I am pretty new to WordPress. Picking it up pretty quickly though.On another note, you folks should really look at the lightbox script I’m using. I’ve used it for years and know the developer pretty well. It’s far superior to the lightbox you folks are using. There are over a hundred option settings built inside and the API has built in functions that help with many things like ajax refreshes and hosting up dynamic stuff inside pages. The support is fantastic and detailed. The only other site online that I’ve seen that has similar support is yours. FYI, I have no vested interest in the script.
For example, with your code, I’m now yanking the captions from the alt attribute in masonry, while serving up the title attribute with the mouseover option. So I can have a short caption on the thumb with a more detailed description in the lightbox window. A distinct advantage for using the alt attribute is that you don’t have the title displaying on mouseover which duplicates the mouseover effect built into masonry. It also avoids the title mouseovers built into most browsers and allows you to use javascript tooltips if you want. And, of course your alt descriptions can be very detailed which will help SEO.
I will probably look into your backend code some more in avia.js and in some of the php files to open up more flexibility by coding in a custom data- attribute that works with the lightbox script I use. By doing so, it will allow the insertion of all sorts of lightbox display options in the headers, footers and outside the lightbox as well — HTML, videos, dynamic content, you name it. If you can code it, it can be fed to the lightbox through the data- attribute that is specific to this script. I sure wished you had a customizable data- attribute built into the backend of the wordpress manager for < a > links. I will probably have to code it myself. I can probably do it, I just don’t know where to look for all the relevant code in all your php files. It could be a lengthy trial and error process. I chatted with the developer of your third party slider that you use and he likes the idea of a configurable data- attribute by the customer. He indicated he was going to look at it in a future version release. There are numerous benefits to having this if you are a true coder.
Anyway, these were some of the reasons I was asking for the alt attribute. You probably assumed most of the reason was for SEO.
On a separate note, where would I find the code that renders the alt and title form fields on the backend of WordPress where you update and modify a masonry element? What file is that in? I have found the code that inserts the lightbox attributes inside of avia.js.
Thanks again for your help. Your support in this forum is excellent. And I don’t say that lightly. I mean it.
Cheers,
DonIn reply to: Remove return breaks from shortcode [one_fourth]
Hey!
WordPress will parse your line breaks and turn them into break tags. So working with shortcodes tends to be a bit of a trick unless you only work in the text tab or disable wpautop( http://codex.wordpress.org/Function_Reference/wpautop).
One thing you may want to try, though it may not be suitable for clients, is using this function:
/*-----------------------------------------------------------------------------------*/ /* Instead of remove_filter('the_content', 'wpautop'); /* Removes wpautop from specified pages with a custom field: /* Name: autoformat Value: false /*-----------------------------------------------------------------------------------*/ function st_remove_wpautop($content) { global $post; // Get the keys and values of the custom fields: $rmwpautop = get_post_meta($post->ID, 'autoformat', true); // Remove the filter remove_filter('the_content', 'wpautop'); if ('false' === $rmwpautop) { } else { add_filter('the_content', 'wpautop'); } return $content; } // Hook into the Plugin API add_filter('the_content', 'st_remove_wpautop', 9);then when you add the custom field with the name wpautop and give it a value of false it will disable wpautop on that page specifically.
Otherwise using the advanced layout editor will allow you to add in the layouts without worrying about it.
Regards,
Devin
