Forum Replies Created
-
Posts
-
Yigit, thanks for the response. I have moved to updating via FTP most of the time anyway since the last major update, so it sounds like all I need to do is regular process (rename Enfold to Enfold old, upload new Enfold theme folder, delete Enfold old.) Then I need to go into the API and update? Or is that update only for auto theme updating?
Sorry, jet lagged!
Thanks
robThis is astounding.
An update that requires this amount of workaround should be rolled back or fixed with 4.5.1. I don’t think it’s fair to push this back on Envato — the bottom line is they are the vendor you use to sell Enfold, and their change has broken the Enfold update process.
I have read this whole thread and I’m unclear — is it OK to just update via FTP, or is there something that will still be broken with the Envato API key?
Thanks
RobGuys… come on… just release an update! Can you imagine if iPhone sent us a bunch of code to install instead of just rolling updates every few weeks? This has been going on for months with no official patch pushed…. Is Kriesi on a beach somewhere sipping a margarita?!? :)
Best
RobThanks Gunter, please keep us posted. It seems like we are way overdue for this patch update.
Best,
RobThat would be great… I know it’s summer, guys, come but on, it’s just a little patch from months ago! Push it! :)
Best,
RobThe 404 page error is still in the production version of Enfold. When is this going to be fixed? It’s been months….
(as a reminder, to replicate go to https://www.thomashenthorne.com/dkdkd/dkdkdk/dkdkdk and instead of the custom 404 page you see a blog article).
Thanks
RobThat is going to be a tough upgrade. I would suggest you push it to a staging site, then upload the theme files via FTP, then make sure everything is working. If you update from the 3.x series to the 4.x series with the WordPress panel upgrade, your site will go down. Also if you have a child theme header.php file, it will need to be updated with the code from the 4.x series.
Hope this helps. Good luck!
You are running into the “strangest technical issues” each week because you are using one of the worst hosting providers out there. Believe me, I was in your shoes, and each week it seemed like something else had gone wrong on the site. I would check the site each morning and hold my breath, wondering if it would load or throw some strange error.
Since I switched, I have had zero problems with my provider. Strange problems like you’re experiencing are a hallmark of Go Daddy so I would strongly encourage you to switch to a better provider. Hope this helps. Best, Rob
Do you have Go Daddy? If so, I would change hosting providers. We had issues like this constantly when we were with GD… the others are just a little bit more in cost but so much more stable.
Great, it worked, thanks! I always hate to add to functions.php unless I absolutely have to.
Thanks again,
RobI’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,
Rob
