Forum Replies Created
-
Posts
-
Google requires that you set up API credentials now before you can integrate with their mapping API. Enfold has a Google Services tab in Theme Options where you can place your credentials once you’ve created them through Google. There are instructions here:
https://developers.google.com/maps/documentation/javascript/get-api-key#key
This is almost certainly a web hosting or email hosting issue or a plugin configuration issue. I use Enfold and the WP SMTP plugin on many many sites without issues. When you say you have the WP SMTP plugin installed and set up correctly, do you mean that you’ve added the name of an SMTP server, a username and password, a port, TLS/SSL, etc? When you send a test message does it get delivered? If not, what is the error message/output from the WP SMTP plugin?
I think you’re trying to solve the wrong problem. :-) The problem appears to be due to your site not having SSL set up on it. If you use the following link the anchor works fine.
Have you tried something like the function suggested here: http://www.wpbeginner.com/wp-tutorials/how-to-add-additional-file-types-to-be-uploaded-in-wordpress/
Hi. Go to Theme Options > Footer > Copyright and add [nolink] to the end of the content there. That will remove the credit.
Looking at the site in Chrome, it appears that the letter spacing on LAKESIDE is causing the problem. The buttons center in that area but LAKESIDE is so wide that it makes the area wider than the window. If you remove the letter spacing from LAKESIDE, you’ll see that the buttons actually are centered on the screen. In Chrome, anyway.
I’m using Chrome. I was just able to reproduce it. I hit the link in Private Content and it worked fine. Then I scrolled up past the section, then scrolled down past the section. Then I put my cursor in the address bar and hit enter. It scrolled so the top of the section was at the top of the window but hidden by the header.
When I tried opening the link in Firefox, the section was scrolled to the top of the window and hidden by the header on the first load of the page. When I refreshed the page, it worked properly where the whole section was visible under the header.
Thanks for the suggestion. I changed it to a more conservative 7 days and that took care of it. Again: Thanks!
I’m using the exact same rules as you listed in your pastie.org link and gtmetix.com complains that BWP Minify files don’t have expires headers on them. Any idea why?
I’ll give this a shot. There’s no way to override the magnific settings? I really don’t want to disconnect anything from the theme update process.
Yes. That did nothing. It only works with videos that are embedded using oEmbed. Not with ones that are linked to from images. See the video player image on the front page of the site in Private Content. It’s working now but only because I hacked the file.
Thanks for your quick reply!
Fair enough. Could you give me a nudge in the right direction? I imagine chaining two together would involve some JavaScript magic?
Thanks!
Hi there. I have solved this issue! Out of desperation I blew away the entire Enfold theme directory and reloaded a clean version and the title and other meta information are back. I have no idea what the issue was but at least it’s working. Thanks for your help!
Hi there.
SEO > Title & Meta appears to be properly configured. In fact most sites just use the default settings and are not configured further. I made a chance to one site and saved the changes to see if that would solve the issue but it didn’t.
I searched all code on the site and the filter
avf_title_tagis only used in the Enfold theme source code.Hi, all. After tinkering around with this issue, I put together some code that let’s you add the Google API code via the Theme Options. The first function adds a field called “Google API Key” to the Theme Options tab. The second function pulls that value and uses it in the underlying HTML. Just copy these into the functions.php file for your theme or (hopefully) child theme.
Kriesi’s solution will probably be better in the long run but in case anyone is interested…
// add some theme options add_filter('avf_option_page_data_init', 'pwm_utilities_avf_option_page_data_init', 10, 1); function pwm_utilities_avf_option_page_data_init($avia_elements){ $new_elements[] = array( "slug" => "avia", "name" => __("Google API Key", 'avia_framework'), "desc" => __("", 'avia_framework'), "id" => "google_api_key", "type" => "text", "label" => __("", 'avia_framework')); $avia_elements = array_merge( $avia_elements, $new_elements ); return $avia_elements; } // add google maps api script with key (only if the key has been entered). add_action('wp_footer', 'gmaps_workaround'); function gmaps_workaround(){ $google_api_key = avia_get_option('google_api_key'); if( $google_api_key ): echo '<!--Google Maps JavaScript API -->'; echo '<script src="https://maps.googleapis.com/maps/api/js?key=' . $google_api_key . '" type="text/javascript"></script>'; endif; }This CSS is incorrect. The correct version is below. Thanks for the starting point, though!
@media only screen and (max-width: 767px) { .responsive .logo a { display: inline-block; vertical-align: middle; } .responsive .logo { position: relative; display: block; width: 100%; text-align: center; } }Just so I’m clear, there’s no way to do this without modifying a core theme file? Or at least overriding it in a child theme?
I know this is probably best added as a feature request but is there any way to compare a child theme and its parent and identify outdated files in the child theme?
After chasing my tail a bit with reinstalling themes and deactivating plugins, this turns out to be problem with avia.js. It isn’t set up to treat the WooCommerce and Instagram images as their own galleries. It treat other groups of images as distinct galleries but not these two. On line 900 of avia.js, you need to add values to the “groups” parameter for “.av-instagram-pics” as I’ve done below. This resolves the problem for me.
groups : ['.av-instagram-pics','.avia-slideshow', '.avia-gallery', '.portfolio-preview-image', '.portfolio-preview-content', '.isotope', '.post-entry', '.sidebar', '#main', '.main_menu'],You could also argue that there should be a value for “#footer” too to separate the footer content from the main content of the page. Just using “#main” is too broad (in my opinion) when you’ve called out other specific content areas like “.sidebar” and “.post-entry”.
I suppose you’re going to say that this is a feature request (although I’d classify this as a bug report). Let me know if I have to submit fixing this as a feature request.
I disabled all plugins except WooCommerce and switched from my child theme to the full Enfold theme and still have this exact same issue.
