Forum Replies Created
-
Posts
-
I not a coder but this seems to be related to the Instagram widget? I no longer use that widget on my site.
* Now we check that all directories belong to a cache entry
*/
$cache_dirs = scandir( $this->upload_folders[‘instagram_dir’] );
$cache_dirs = array_diff( $cache_dirs, array( ‘.’, ‘..’ ) );As workaround, you can download Smart Slider…. free version works great for videos. I’m using Pro now but was very happy with the free, and it works great with Enfold.
(I have no connection with Smart Slider besides being a user)
Very strange. I have been running Enfold on WP Engine for 2 years now with no problems or conflicts and did not need to modify wp-config.php. I wonder if something became corrupted during install? Wp Engine is great, glad they were able to sort it out!
Kriesi, can you also include Ismael’s fix for the minor 404 bug in the next update? Several of us are worried about soft 404 errors in Google console if we don’t get it sorted soon.
I just had to revert to the standard Google font (Open Sans)… the uploaded seems to default to a heavier font (next to the uploaded font it says 300, 400, 600 etc)… Is there a way to set which weight to use on the uploaded fonts?
That worked like a charm for me and the Google font is now in the fonts drop down menu. By doing this I was able to turn on “load google fonts in footer” with no impact to user experience, but helps my page speed score. No longer loading Google fonts at all. Thanks for the tutorial!
Best
RobHi David, what version of Enfold are you on now?
The reason I ask is the support forum has been filled with people who had their sites go down when they went from 4.2x to 4.3x or 4.4x because of the aformentioned issue around old files being left behind or partially overwritten.
Once you get to 4.3 you can resume dashboard updates, but the update from 4.2 to 4.3 or 4.4 is likely to fail in the dashboard… at least it did in mine.
I don’t want to jinx it, but 4.4 is running fine on my site right now. Most of the issues stem from people updating within the dashboard instead of deleting the enfold theme folder and installing a fresh copy.
Hope yours gets sorted out.
Best,
RobI am using WP Engine (they are great!) and it’s working fine with Enfold 4.4. All the performance features are turned on, and I’m using Fast Velocity Minify plugin in addition.
I ran into the same issues pushing from staging to production. If you are updating from 4.2 to 4.3 or 4.2 to 4.4, the push from staging to production won’t work, because it leaves the old files from 4.2 and those files conflict with 4.4
Once you get to 4.3 and above, you can go with the standard push from staging to production process… but if you’re running lower than 4.3, you need to do it manually. Yigit helped me with it because my site went HTTP 500 white screen when I pushed from staging to production. but I think what you need to do is DELETE the enfold folder on your production site and manually FTP copy over the latest Enfold theme there after you push from staging to production.
Hope this helps!
RobThanks much… I agree, I never thought it was critical (unlike the 404 fix, which IS critical… ha ha) but thought you should know it’s showing that error.
Thanks!!
RobThis fix is NOT in the GDPR update (4.4)… please confirm this is going to be in the next update in 1-2 weeks? I am concerned this bug will result in Google Search Console “soft 404 errors” increasing.
Thanks
RobIt’s already set to that… :(
Maybe some of the custom css added over the years is overriding?
Pasting in private content…. Thanks!
See other thread… Ismael released a patch that fixes it:
https://kriesi.at/support/topic/error-error-404-page/#post-960200
Ismael, yes that code DOES fix the 404 bug. I echo the question above… will this fix be in the GDPR update?
Thanks for fixing this so quickly!
Rob
When I de-activate Yoast, the bug goes away. De-activating Yoast is not an option, however, so devs need to figure out how Enfold and Yoast can get along better… :)
Definitely Yoast… I disabled Yoast on my production site and 404 pages work beautifully…. re-activate Yoast and the bug (conflict?) comes back….
I think I figured it out… if I disable Yoast plugin, the 404 functionality works fine…. so conflict….
The plot thickens…. but if you go to this url, no custom 404…
https://kriesi.at/themes/yigit/yigit/yigit/yigit/yigit
Bug seems to be impacted by number of sub-directories?
You have login credentials for staging site so feel free to go in and play around…
Thanks,
RobHi,
The above page is not a plugin generated page…. you can see the same bug on the original poster’s website or at
http://www.thomashenthorne.com/yigit/yigit/yigit/yigiti/
That link should go to a 404 and it goes to our latest blog article…
This is definitely an Enfold bug…. are you guys not able to replicate it on your sites?
Best
RobYes, maps load, but Enfold appears to be using an older version that needs to be updated. At some point if it’s not updated, maps will stop loading I assume.
Best
RobActually it is not a valid link. It should go to a 404 page but instead goes to the latest blog article… as does any 404 with deep embed (www.thomashenthorne.com/basilis/basilis )
Please escalate this to the developers to fix with this weeks’ GDPR release.
Thanks
Ro
bHere’s an example of the error in action…
http://www.thomashenthorne.com/hello/enfold/test/
404 error page works for:
http://www.thomashenthorne.com/hello/
but once you add another path to the url it re-directs to the first blog page…. happening on every Enfold site I’ve tried that’s running the latest version.
Yup, it’s a bug, we are all running into it… (there are other threads on this). So far Enfold team has not posted a patch.
