Forum Replies Created
-
AuthorPosts
-
October 21, 2020 at 8:09 pm in reply to: AVIA Layout Builder blocks won't load after WordPress update #1254763
THIS SOLVED IT FOR ME TOO
I’m using 3.3.2 Enfold and a child theme with only a couple CSS overrides and this is happening to me with WP 4.3.1
Seems to be a regression of a bug Spet 2014
February 4, 2014 at 11:30 pm in reply to: Header navigation (main menu) disappears on mobile devices #219695HEY I FREAKING FIGURED IT OUT:
Javascript error that was only triggered in iOS Webkit.
I believe it’s still true that Chrome and Safari on iOS are Webkit-based, even though Chrome went to it’s own base some time ago on other platforms.
So in my case, I had some jQuery javascript which was causing only an error on iOS webkit browsers. The desktop browsers must be more forgiving. The bad code was a selector. I had
$('head link[id^=pau').appendTo('head'); // note the missing close bracket in the attribute selector
Shoulda been
$('head link[id^=pau]').appendTo('head'); //happy
So the only way for me to debug it was by following these instructions to enable web inspector for Safari on iOS: http://stackoverflow.com/questions/11262236/ios-remote-debugging/12607124#12607124
I’d start by making sure any site with this issue has no JS errors ON THE DEVICE, since that’s going to impact the slideshow and nav.
- This reply was modified 10 years, 9 months ago by jrevillini. Reason: adding formatting
February 4, 2014 at 11:11 pm in reply to: Header navigation (main menu) disappears on mobile devices #219688Same here – no change. Is there a plugin for chrome for iPhone to inspect the element and see what styles are operative?
February 4, 2014 at 7:04 pm in reply to: Header navigation (main menu) disappears on mobile devices #219570FYI tried adding it to custom.css since I found an @media thing ready to go. Change took, but no diff on mobile: https://medcruiters.us/wp-content/themes/enfold/css/custom.css?ver=1
February 4, 2014 at 7:00 pm in reply to: Header navigation (main menu) disappears on mobile devices #219567Added that, but if you look at the CSS generated, the @media block is showing up after some other css in the same HTML block. I thought that @ directives need to be at the top to have an effect. or maybe that’s just @import. i don’t know, but either way, it didn’t affect it on my mobile device. Here’s the CSS that was generated, yet I only pasted what you sent me into the box. the above stuff is coming from somewhere else.
<style type="text/css" media="screen"> html { margin-top: 32px !important; } * html body { margin-top: 32px !important; } @media screen and ( max-width: 782px ) { html { margin-top: 46px !important; } * html body { margin-top: 46px !important; } } </style>
February 4, 2014 at 6:25 pm in reply to: Header navigation (main menu) disappears on mobile devices #219538oh, and for me, i have not modified the stock field value regarding responsive. i also am not doing anything with zoom level in either safari or chrome for the iphone 4s with iOS 7, yet i am missing header nav and slideshow.
WP 3.8.1
Enfold 2.4.5February 4, 2014 at 6:22 pm in reply to: Header navigation (main menu) disappears on mobile devices #219537I’ll post mine, as I have the same issue: http://medcruiters.us
November 21, 2013 at 9:30 pm in reply to: masonry blog element not working unless a regular blog post element added #191631Thanks so much for the fix for the theme, even though the issue is really in the plugin. I had a feeling it was the plugin, because another plugin that does exactly the same works fine with your theme.
November 19, 2013 at 10:31 pm in reply to: contact form does not send to default email (or i am misunderstanding something) #190734very cool. yes, i misunderstood the label. I thought that if i entered nothing (hey, I’m lazy), then it would use the default email of the system. i think adding a check that it’s filled out is a great solution.
November 18, 2013 at 6:21 pm in reply to: contact form does not send to default email (or i am misunderstanding something) #190213OK found it.
File: /wp-content/themes/enfold/framework/php/class-form-generator.php
Line: 665That’s where you use wp_mail to send mail from the form using ajax.
If I create a contact form and enter nothing in the place for the email recipient, the value in $send_to_email is empty.
I used this line to debug, directly before the wp_mail call:file_put_contents( '/xxxx/xxxx/tmp/ajaxmail.log', @file_get_contents( '/xxxx/xxxx/tmp/ajaxmail.log' ) . "$send_to_mail | $subject | $message | $header \n\n" );
$send_to_mail was blank.
So I also output values for $this->form_params[‘myemail’], $new_post[‘myemail’], $to, and $copy – all were blanks.
And you’re saying that on your test environment, you can leave the recipient blank when configureing the contact form and it picks up the default email address and uses it? Maybe somebody fixed something along the way. But I think this is reproducible using the stable release on themeforest.
November 18, 2013 at 5:44 pm in reply to: contact form does not send to default email (or i am misunderstanding something) #190188Can you tell me where you wp_mail() and i’ll check the values right before send?
November 18, 2013 at 5:20 pm in reply to: contact form does not send to default email (or i am misunderstanding something) #190165They look identical to me and i can reproduce the issue. Is there an easy way to debug? I’ll do the debugging and find out if it’s a plugin conflict.
Aha! Now that I look at that selection, I do see that all the options are subsets of some taxonomy.
As I think about what it would take to develop this dialog/shortcode/query/display code for this element, I think I understand the programming decision to use taxonomies. It makes the logic for everything else simpler.
Maybe in future iterations, it could be made a little more flexible by allowing selection of either multiple post types or multiple taxonomies, or both, but I realize what an undertaking it would be to make the UI intuitive. Maybe it is best left as is.
I think adding some notes to the documentation that address this scenario specifically would eliminate some support requests. Here’s what I’d put in a callout box or something. Feel free to use:
NOTE: A masonry layout element displays posts for selected taxonomy terms. Custom post types must have associated taxonomies in order to be configured to display within this type of layout.
Thank again!
November 15, 2013 at 5:34 pm in reply to: masonry blog element not working unless a regular blog post element added #189306This reply has been marked as private.November 15, 2013 at 5:30 pm in reply to: masonry blog element not working unless a regular blog post element added #189301Right now, Google Analytics for WordPress is disabled and I’ve installed and activated Google Analyticator, but you can log in and toggle those to see the issue. I messed around with the settings in GAfW to try to find some that would work, but didn’t find anything that made them coexist in peace. I’ve cloned the News page to a couple new drafts for testing. After you’ve logged in, you can use that to see the issue. I’ll send creds in a private post.
Works with GAfW Activated: http://workoutplanr.com/news-works/
Not Working with GAfW Activated: http://workoutplanr.com/news-not-working/If you figure out where the conflict is and you think it should be handled by the plugin developer, I started a thread here: http://wordpress.org/support/topic/conflicts-with-masonry-blog-in-enfold-theme
Devin:
that fullwidth masonry element already supports custom post types by default from the advanced layout builderI don’t see a way to select a custom post type in the masonry element dialog. I’m running the latest Enfold. The first field gives me these options: Category, Post Tag, Post Format, Portfolio Entries. And incidentally, I’m creating a page and using the advanced layout editor to add this element.
Do I need to do something in code or in the theme options to give me CPTs in the selection options for masonry? And what if I want to do the same for the Blog Grid layout?
Thanks!
- This reply was modified 11 years ago by jrevillini. Reason: added quote to which I was reponding
November 12, 2013 at 4:10 pm in reply to: masonry blog element not working unless a regular blog post element added #187319If I disable the Google Analytics for WordPress (http://yoast.com/wordpress/google-analytics/) plugin, the issue is resolved. I thought it might be a javascript issue, but I see nothing in the console about it. This leads me to believe it’s a PHP issue.
-
AuthorPosts