Forum Replies Created
-
Posts
-
I’ve got a new error this morning, seems to be the way Jetpack and Enfold are talking to each other? Error in private content…thanks!
(pls note I have a header.php in child theme, just in case that is causing issue)
Thanks!
RobHi Basilis,
I have read the above 4 times and I am so sorry I do not understand what you are saying.
I don’t think the fix for the above errors are included in the next Enfold version… the fix for the other php errors I was receiving are included in next version but these are completely different php errors hence new ticket….
Thanks!
RobYes, that appeared to fix it…thanks!! So whatever Gunter did on the staging side to the enfold theme folders fixed it. Can that be incorporated in the next theme update so the errors don’t return?
Thanks much for your help!!!
RobHi Nikko,
Thanks for jumping in!
I am running php 7.0 and latest version of WP and Enfold.
Re other thread (which you can close) where you said:
Hi Rob,Can you try to use the Enfold theme modified by Gunter from the stage site and use it on your live site?
Let us know if this helps.Best regards,
NikkoYes, I can copy that over… I wasn’t aware he had modified theme, I thought he had just changed the file so it matched the current theme file. Did he do a patch on the theme on staging? Whatever he did fixed the errors there….
Thanks,
RobPS I prefer not to provide login credentials for production site unless it’s absolutely essential — I cannot have that site go down for even a minute, and cannot have plugins disabled and re-enabled which is usually the first step. Prefer to get this fixed on staging side and then push patch to production, so I’ll try above suggestion to see if that helps. Thanks for understanding! Rob
Since the errors are fixed on my staging site where you did the work, I just copied the file over to my production site.. I should know tomorrow if this fixes it. I think it will. Somehow the file may have not gotten updated in the last update… I usually don’t update via FTP but instead use the wordpress functionality since it seems much faster / less downtime to do it that way?
Thanks!
RobHi Gunter! Thanks for continuing to look into this! There is some good news to report!
To answer your question, I updated the theme just about when it came out… I think within a day.
Lots of new errors in the server log on the production site, including some pretty scary warnings about the database. I’ll post them in private content. I also notice the staging site is running slower than normal, but not sure if that’s just “internet weather.” The GOOD NEWS is that the staging site error log is empty!!! Staging site content is very old so any fixes there I would need to make manually to production site.
Please have a look at private content and advise your recommended next steps.
Thanks and best,
RobHi Gunter, no worries, since this is not impacting front end I don’t consider this urgent but would like to get it fixed. Hope you are someplace nice for vacation.
Do you think it’s a folders permissions issue? Seems like if it were, it would impact a lot more than this one line of code re the pesky Instagram widget? What do you suggest as next steps?
Thanks,
RobHi gunter!
Thanks for checking. Yes, I did clear my server cache… and on the staging site above, there is no server cache.
Is it possible I have a corrupted file? I have not pasted Yigit’s code above as I was thinking you guys could SFTP into the staging site (credentials above in private content) and make mods to see if errors go away, then I could make same changes on production side.
Thanks,
RobHi Yigit,
I’m not sure why the editor in the backend no longer works… is it just my installation or is that a change WordPress made?
SFTP credentials in private content so you can make the mods if you don’t mind and then make changes if we need to further modify….
Best and thanks!
RobEllen, I would suggest you just install the plugin called “Instagram Feed” by Smash Balloon… it works great and is free.
Very easy to set up.
Best,
RobIsmael can you guys put this into production asap? I don’t want to continue to patch Enfold for a bug that’s been around more than a month now. Seems like it would be easy to include in a mini-release and push it within a week?
It is disappointing to see that the patch for the bug was not included in this week’s update. This has happened repeatedly, where a patch is published on the forum and it takes several versions of Enfold before it is finally included in the production version.
Clearly you guys need to look at your bug tracking / resolution system. We are looking at more than a month Enfold has had a bug with the custom 404 page now, which causes soft 404 errors on Google search console.
To update from 4.2.x to 4.3 or 4.4 requires update via FTP, unfortunately, or site will indeed crash as you have experienced. Be sure you delete the old Enfold folder before updating the new theme.
Hi Ismael,
Sounds like that change would change the entire site, not just that page… now that #1 is fixed, I don’t need #2 as much… I just thought if there were an easy link to the burger menu I could set up the slider button with that.
Thanks for your help!
RobI have also noticed this slowing down my site. Is this something that Enfold requires? The article above indicates some themes use font awesome. Does Enfold?
Many threads on this… update header.php in your child theme folder and lightbox will start working again.
:)
Hi Ismael!
Thank you for your reply!
1. I just figured it out… when the css didn’t change it, I tried to think why it is re-loading the page… it is doing that because the link in the “MENU” button on home page was going to anchor using http instead of https… I just converted to https in the past week or two. So when I changed link to https, it works again… yay!
2. As you can see, I am sort of “faking” the menu by having user click menu or hamburger photo and then page scrolls down to menu. I was wondering if there’s a way I could have the hamburger photo be a link that actually launches the hamburger menu? Now that #1 is working this is not critical, but I thought I would ask since it is a bit of a cheat design in the way I have done it.
Thanks!!
RobThank you! I found the widget in an old unused sidebar, deleted it, and it seems like the errors have stopped.
Thanks Günter!
RobYigit, when deleting a folder to install the theme, is there a fast way to do it? In Filezilla it takes a long time to delete the Enfold folder which means my site is down longer than ideal. Should I just rename the folder, then install Enfold to the old folder location, then delete the old enfold folder? I’ve been wondering about this for some time.
Thanks,
RobIf you are updating from 4.2x to 4.4, you need to update via FTP, and delete the Enfold theme folders first (don’t overwrite, as it mixes files)
Good luck!
