Forum Replies Created
-
AuthorPosts
-
OK. I remembered the “Screen Options” tab and reactivated the “Layout” palette. Looks OK now.
Thanks.
—Michael
Hi:
The error after the update was showing because someone had activated the “show errors” in the server. That’s fixed, but the failed update is still an issue.
Thanks.
— Michael
I was able to restore the CSS settings. No need to follow-up.
Thanks.
— Michael
September 27, 2018 at 7:04 pm in reply to: Phone Number/small info text responsive behavior #1015460Magnificent!
Thank you.
— Michael
Yes. I’m good.
I updated it successfully via FTP.
Thanks.
— Michael
I have done the suggested exactly. The update did not work for me. Here is the error message:
“An error occurred while updating Enfold: Download failed. A valid URL was not provided.”
I suppose I can upodate via FTP, I have a child theme.
— Michael
I have found another soution. Right now, it’s good.
Thank you for your response!
— Michael
Here is the page I am replacing in the new site. It will give an idea of what titles should be like, two lines, and if you click them will show the amount of copy. The copy part works perfectly in the Ajax portfilio, just not the title text.
May 5, 2018 at 5:25 pm in reply to: LayerSlider transition not working in Chrome after 4.3 update #952140That’s very interesting—good information.
Thank you for looking into it.
— Michael
May 4, 2018 at 4:03 pm in reply to: LayerSlider transition not working in Chrome after 4.3 update #951744It is only on the older Mac OS—10.11.6. All others seem to work, including the older versions.:
Mac OS 10/11.6
Chrome Version 66.0.3359.139 (Official Build) (64-bit)Thanks.
— Michael
May 2, 2018 at 9:45 pm in reply to: LayerSlider transition not working in Chrome after 4.3 update #950317I don’t quite know what you’re referring to as “customization.” We develop websites and don’t need a freelancer—and were only looking to have the theme work as it should standardly as there has never been any trouble over the years like this.
I will try the update, thanks.
I have identified the issue only occurs on older MAC OS’s. This is the system where the problem is:
Mac OS 10/11.6
Chrome Version 66.0.3359.139 (Official Build) (64-bit)It did work in Chrome on a more updated system below:
Mac OS 10/13.4
Chrome Version 66.0.3359.139 (Official Build) (64-bit)So it looks like the issue is with a specific Mac OS as above.
April 29, 2018 at 12:21 am in reply to: LayerSlider transition not working in Chrome after 4.3 update #948484Can I get on an alert list for when this issue is handled?
Do you know at what version this issue first started? It was within the last 2-years, before that all was compatible as my older sites still run flawlessly.
Also, is it possible in Enfold to set a different home page in Chrome? Or, have it direct to a duplicate site that is made without those incompatibilities?
Do you know of any slider plugins that are compatible with Enfold and Chrome?
Thank you.
— Michael Blair
April 27, 2018 at 8:27 pm in reply to: LayerSlider transition not working in Chrome after 4.3 update #948148I have just verified this is a Chrome for Mac only issue.
April 26, 2018 at 10:48 pm in reply to: LayerSlider transition not working in Chrome after 4.3 update #947506OK. On further testing, I have found an older version of Enfold and LayerSlider that still works perfectly in Chrome:
LayerSlider: 5.6.8
Enfold: 3.7.1In some update either in Enfold or LayerSlider an incompatibility occurred. It has worked perfectly for a long time, so I am hopeful you guys can trace it down and get it working again. It is an essential function in Enfold for me and I have developed a lot of sites with Enfold using the LayerSlider.
Thank you.
— Michael
April 26, 2018 at 10:39 pm in reply to: LayerSlider transition not working in Chrome after 4.3 update #947500I have checked to see if LayerSlider on its own is compatible with Chrome, and it is. See this link:
Enfold is not compatible with LayerSlider on Chrome. See this link:
Please let me know if this is something you can address and fix or if I should look for another slider, test all and redevelop all website pages with sliders. I have five client websites with extensive use of LayerSlider that I will have to go back and redevelop—a lot of work for no pay.
Let me know.
April 26, 2018 at 10:23 pm in reply to: LayerSlider transition not working in Chrome after 4.3 update #947490I have tested this on an older install, and there are issues there as well—just different. All are major issues. I have concluded LayerSLider in Enfold is incompatible with Chrome. (Version 66.0.3359.117 (Official Build) (64-bit)
I tested on:
LayeSlider 6.6.8
Enfold 4.2.6LayeSlider 6.7.1
Enfold 4.3So the issue may have nothing to do with the 4.3 upgrade, but is a LayerSlider and Enfold incompatibility on Chrome.
If this is an issue you cannot fix, please let me know if there are any fully compatible sliders with Enfold and Chrome.
Thank you.
— Michael
April 26, 2018 at 8:52 pm in reply to: LayerSlider transition not working in Chrome after 4.3 update #947460All the LayerSlider transitions are not working after the 4.3 update. This breaks the majority of the pages site wide.
I will give you a chance to look at it, then if it cannot be fixed I will delete the entire site and restore from backup of the earlier Enfold version. I can see you are busy with 4.3 issues, so please let me know if this can be handled.
Thanks.
Yes, it appears to be a Safari issue from a recent update. When I test out in Chrome it all works fine.
Thank you.
April 20, 2018 at 7:05 pm in reply to: Unwanted elements at the bottom of pages for whioch there is no code #944723Thank you very much for taking a look. I have relayed your response to WPL.
— Michael
I tried it in the functions.php file and it does not work at all. I will set it up as a child theme, and vet all the plugins to see if there is a conflict.
Thanks.
It is in the “Snippits” interface, a plugin for adding code outside the theme functions file—so it will not be overwritten with updates. Please see the “Snippits” menu in the left sidebar underneath “Plugins.” CLick “All snippits” and then edit the only one you will see.
Thanks.
Now the script doesn’t work. After clearing everything, closing and reboting the browser—it does not load with the first slide open. However, if I refresh the screen it does on the second load. So the script isn’t working as it should.
I tried it in the functions.php file and it does not work at all. I am using a plugin, Snippets, where it is now active. This plugin has worked flawlesly for me on many sites incliding complex ecommerce integrations.
If you can have a look to see if it is an easy fix that would be great. See my admin login info above.
Thanks.
This is a nice piece of code, thanks. I changed it so it opens at the first slide.
// custom script
function add_custom_script(){
?>
<script>
(function($){
setTimeout(function() {
$(“.aviaccordion-slide-1”).trigger(‘mouseenter’);
}, 1000);
})(jQuery);
</script>
<?php
}
add_action(‘wp_footer’, ‘add_custom_script’);However, it does not resume the normal autorotation of the accordian slider after an interval. And, eventually it opens and closes slides 2 and 3, and sometimes 4 in random order and for random durations—sometimes. In other words, it seems to affect the autorotate so it does not work and affects some slides randomly so they open and close. The “mouseenter” does work fine to manually rotate the slides.
Is thre any way to run the script as you have it leaving the fist slide open for a certain interval, say 10 seconds, and then put that script to sleep and rectivate the built-in auto-rotate script so the autorotation again works?
Ideally, the first slide would load in an open position, hold that way for 10-seconds, then the autorotation would resume normally with the interval set in the accordian slider control settings.
Let me know.
Thanks for the help.
I am interested in doing this as well.
- This reply was modified 7 years, 3 months ago by blaircomm.
I have managed to figure out the CSS that makes it all work on both Android and iPhone. Something changed on some update somewhere since all this was not needed before. It may be a little heavy, but it seems to work across devices just fine. I didn’t want you to have to look into it if it’s now working. Thanks.
/* ---- KEEP MOBILE MENU VISIBLE SCROLL ---- */ #advanced_menu_toggle, #advanced_menu_hide { position: fixed !important; right: 3% !important; top: 5% !important; } @media only screen and (max-width: 900px) { #wrap_all {overflow: hidden !important; /*needed for mobile menu scrolling */} } @media only screen and (max-width:767px) { .responsive #top #wrap_all #header { position: fixed !important; } .responsive #top #main { padding-top: 80px !important; } } @media only screen and (max-width: 767px) { #top #menu-item-search { display: none; } } @media only screen and (max-width: 767px) { .main_menu{ right: -5px !important;} } @media only screen and (max-width: 767px) { #top .social_bookmarks { display: none !important; }} /* ---- END KEEP MOBILE MENU VISIBLE SCROLL ---- */
OK. I have had a chance to test out a dev site with all plugins disabled. The same sitution occurs on both Android and iPhones.
I have made a temp user for you to access the site and see if you can understand this behavior. (See private content.)
There are no alterations to Enfold other than the plugins installed. No code changes at all. All plugins were disabled and the non-scrolling behavior on smartphones was the same.
I hope you can gain some insight into this so we can fix it.
Thank you.
— Michael
Hi:
Thank you for your response. The custom CSS makes no difference in or out. I have set up a dev site and will test all the plugins—though I hate doing it. Meanwhile, here is some ofher data:
– The menu problem is on both Android and iPhones—but in smartphone size only.
– Tablets work fine over 765 px. At 765 the menu changes and no longer sticks to the top with scrolling, plus loses the transparancy option and the shrinking action. iPad Air for example works fine. It is completely a smartphone issue below 765 px.
– In the “HEADER” section under the Enfold menu, these dialogs show that the “sticky header” is ignored on smartphones:Sticky Header
If checked the header will stick to the top of your site if user scrolls down (ignored on smartphones)
Shrinking Header
If checked the sticky header will shrink once the user scrolls down (ignored on smartphones + tablets)Both these are checked. Perhaps this code is preventing the custom CSS from working by overriding on smartphones below 765px? Can this be the case?
Again, tablet sizes work fine, but smartphone sizes do not. And the social icons dissappear, clearly there is code defining a different menu for smartphones below 765px. For some reason the custom CSS is not overriding this.
/* —- KEEP MOBILE MENU VISIBLE SCROLL —- */
#advanced_menu_toggle, #advanced_menu_hide {
position: fixed !important;
right: 3% !important;
top: 5% !important;
}@media only screen and (max-width: 900px) {
#wrap_all {overflow: hidden !important; /*needed for mobile menu scrolling */}
}/* —- END KEEP MOBILE MENU VISIBLE SCROLL —- */
I will let you know if I find anything in the plugins—and I can give you access to the dev site if you like.
Thanks.
— Michael
- This reply was modified 7 years, 4 months ago by blaircomm.
November 14, 2016 at 10:25 pm in reply to: Columns not responsive soon enough and content overlapping on tablets. #712193This works perfectly! Thanks for your help.
– Michael
This is now working. Thank you very much.
– Michael
-
AuthorPosts