Forum Replies Created
-
Posts
-
I also checked the LayerSlider system status and it shows version 6.2.2 with a message to “update to latest version (6.4.0), as we are constantly working on new features, improvements and bug fixes.” Enfold has been updated to the latest version, and as it is built in shouldn’t LayerSlider be as well?
Scratch that last message… we created a new slider and added one slide with 12 layers containing images and links. Now we can’t add anything further without getting the same error message as before. We’ve already had hosting increase the allotted uploads capability. The debug log is still displaying the error “PHP Notice: Undefined offset: 2 in /home/studiodel/public_html/ds/wp-content/themes/enfold/framework/php/function-set-avia-backend.php on line 433”.
Any other suggestions?Thank you for your reply, Andy. We’ve determined that one of the sliders is corrupted. Not sure why. We are able to edit other sliders and create new ones, but can’t do anything to the one that is throwing the error. There are 25 slides in the one slider. Do you know if there is a way to display the layerslider code on the screen so we can troubleshoot it further, or at least so we can copy/paste the slide details into a new slider? I know it’s possible to display the Avia Layout Builder code and am hoping it is possible with layerslider, too. We’ll whittle the slides into smaller, more manageable sliders (less slides), but it would be helpful to not have to recreate it all over again. I’ve tried exporting/importing the slider but it gets the same error.
I have a website that was super slow on the backend and throwing the same layerslider errors and warnings in Wordfence and Dashboard home as described by others in this thread. I disabled the unused layerslider in the child theme’s function file and the backend has already shown improvement in speed.
I have one other site that is showing similar problems, but it is actually using layerslider. I’m reluctant to upgrade other sites using an older version of Enfold until the layerslider issue is resolved. Is there an ETA on when this bug will be fixed?
Please disregard the last message. The minify css cache was enabled and that was preventing the modified css from showing. Thanks for your help–it’s appreciated.
We want the post dates to appear below the titles, but they don’t seem to be showing. We had previously hidden the post data using the theme css, but now that we’ve removed it the dates aren’t appearing for us. Link to a blog post is included in private content.
Thanks, Yigit. I’ve provided a link to the website in question and a link to a screenshot of the font awesome YouTube icon we’d like to use (instead of the Enfold default).
Oops, never mind! I think I found a solution on the Enfold forums about it. Sorry to have bothered you.
Love this theme!I don’t know what the problem was, but I deleted the icon with the mail that links to “sign up for project news” and added it in again. That fixed the issue, so perhaps there was a malformed tag or something.
Thanks for listening to my issue. Copying and pasting it to you actually help me visualize and zoom in on the problem area.
Have a good day!
No iframes, I’ve attached the script for you to see and noted in BOLD letters the start and end of where I think the problem may lie. But it has been working for almost a year, so I don’t understand why now and what it is that is causing the problem. Any thoughts?
Thanks!
Thanks for your reply. I’ve uploaded a screenshot of the mobile home page in portrait view which is correct. I’ve also uploaded a screenshot of the about page in landscape view which is incorrect. In general, I’d only like a watermark to show on the home page and to position itself correctly behind the text itself in both portrait and landscape view. Any suggestions?
Thank you for your response. It appears the site is using a security plugin that is setting 403 and 301s. I’ll delve into this further.
Got it! Thanks for your help. We love this theme and your support is outstanding. Thanks so much for everything.
Sorry. I did that because I was trying to correct. See now. That does look better, but still not quite right. Suggestions?
Thanks that worked great! Only problem is it pushes the nav bar down a lot. Any suggestions for correcting it?
