Forum Replies Created
-
Posts
-
Finding plugins for this are not the question (yes, Google is handy), but these do not tell which play well with Enfold’s frameworks, which was why I came here. I was really hoping to avoid having to install dozens of menu plugins just to figure out which were compatible with Enfold.
I am going put it out there again. We need a good and maintained list of compatible plugins. Yes, there are a lot, but for many of us, we have lots of licenses of Enfold and need a good place for reference.
Found a really odd caching issue with Firefox. eventually had to nullify what was previously put in quick css with !important code. Not sure why, but we have a temporary solution. That might need someone to look at.
I had to remove te background image, so I could show the page. I will re-create this on another testing page later today.
I need to find a resolution where I can have a color area with an overlay and have it stretch from top of the color area to the bottom, without and breaking. I have done this on other projects without issue with Enfold and not sure why it does not work here. There is very little custom css, and none that should affect this.
I need the space in there, as it puts space between the image and the bottom of the color area stack. I have the same space at the top of the stack, but it does not affect the background there. I need the spacing in the image I just uploaded, without the break in the background image / overlay. I initially tried it with the padding, but that resulted in the same problem. I don’t recall having this problem on any other projects in the past.
No, the header line is as designed and implemented in css. What is not working, even with the update to 4.1 is when you apply a background image to a color area. I can do it with a background image, or an overlay texture (Enfold-driven). Look at the dark gray stack (color area). The pattern does not go all the way down to the bottom of the color area. I tried it manually using a background image without overlay and got nearly the same result. Screenshot link attached in private area.
We are seeing strange issues with color areas as well in the latest updates. Not sure if they are related, but wanted to chime in.
That works, thank you very much!
I still have a strange issue with the color areas below, but maybe that needs to go in a separate ticket.
Okay, clicked on save, but for some reason it returned an error as I jumped tabs to preview.
I am really curious though on the settings. The settings say it should have been at the top, without any css.
Actually, I do not have a caching plugin installed. Extremely basic site with just Enfold being the one thing added.
One note, this plug-in instantly breaks with Enfold, as it tried to insert itself as a replacement for any editor interface.
I just figured it out. Someone had somehow put in a WordPress Editor plugin. It was disabling the editor interface. I have no idea who installed this. I am really sorry for the trouble.
-jason
As a side note, the slider appears to also have issues with some installations of Enfold 3.8.5 as well. That was part of what we were in the middle of determining and realizing without our own testing. In instances of it breaking overnight for those running 3.8.5, it seems to have switched the way the images load to require https, and then the browser throws an error on the transaction (on certain browsers) and you get a broken slider as well.
Does LayerSlider perform micro-updates at any point, aside from normal updates through the theme install/update mechanism?
Thank you Yigit and Vinay for chiming in. It is appreciated.
I agree that the issue is not one of desire to close tickets, but a necessity due to the technology/process. This has happened many, many times in the past and it has cost customers and your team on all levels. I would like to ask you to consider that while this forum worked in the beginning, it is not conducive to a large community and ticket system rolled up into one solution. We need a way to communicate without it making it impossible for you to manage the issues at hand. I think it would also allow everyone to better see how an active community can actually reduce your ticket load significantly. It also gives the opportunity to do more fact-finding and user-case scenario building for future development, gives people a better avenue to show their Enfold creations and also ways to customize and take things to the next level and inspire others to do the same.
I guess what it boils down to is that most of the frustration stems from people that are as passionate as your team about Enfold, but finding a hard time when their passion hits a technological brick wall. In many ways, it is a huge sign of success for your team and what you built with Enfold, but now it is time for a new tool to take it to the next level.
If it were related solely to the theme update, it would not explain why some of our sites that were still running 3.8.5 all broke overnight. I think this is indeed related to LayerSlider, which was probably updated when you updated your Enfold parent theme. I am wondering if LayerSlider is using some sort of microupdate feed that updated all of the sliders with a bug. It would explain how both of us could have same or similar issues, yet be on different theme versions. I am guessing Kriesi’s team is waiting for any answer from LayerSlider as well.
Is it trying to pull images from https? That is what broke for us. All previously created sliders started making the imagery load via https, while rest of the page loads in regular. When I recreated the slides from scratch with imagery from the library, it went back to loading standard, rather than https.
Is your’s trying to pull the images from https?
Are you running latest Enfold? We are still on 3.8.5 with WP 4.7.2. Seems to have happened overnight, yet cannot figure out what changed overnight. Turned off all the plug-ins that have background updates (WordFence, JetPack) temporarily, but does not solve the issue. It is almost like it was timed somehow, since so many are experiencing it.
Update: We ended up rebuilding one of our sliders and found that it worked. Not sure what the underlying cause it, but it would appear we do have a workaround, albeit a time-consuming one. Please share if anyone uncovers the root cause of this bug.
I can say that it is breaking, even without the update. For us, LayerSlider seems to have switched to wanting images via ssl, which throws a browser error and a broken image icon for some.
Need to know how widespread this is, as we have a ton of licenses and sites running Enfold.
Sweet! I will look forward to installing and testing tonight or tomorrow. Lots to look forward to from the change log.
-jasonWe saw a break like this for a plug-in not too long ago. Did 4.0 start requiring a newer version of php by chance? That was what undid the other plug-in.
Thank you very much for this! The site we were going to use this for is using a different solution at the moment, but I am eager to try this on our testing site within the next week or so. Thank you for developing this.
It would be really cool to put this in the code snippets section, as it could be helpful to many developers
Thanks again!.
Also, we have disabled almost all plug-ins one-by-one to makes sure none of them are the cause. All WordPress components are up to date, with exception of the newest Enfold. We were just waiting to make sure there were no immediate issues and have a chance to test for compatibility on our testing site first. So at this point, it seems to be narrowed down to WordPress and.or Enfold.
After further testing (trying to disprove other theories), we can confirm it seems to be level-based. Admins always get access to the bar, whereas logging in under any other user level redirects the user to the home page, sans the admin bar. We have tested this in various browsers (Chrome on Mac and Windows, Safari on Mac and iOS, Windows Edge, Windows IE).
