Forum Replies Created
-
Posts
-
As has been mentioned a few times in this thread now it’s great that you now have a change log but it would be even better if you kept it up to date.
My site is showing an update to 4.3.2 is available but I’ve no idea what the update contains so am hesitant to update in case it breaks any of my custom code.
Your changelog shows the lastest update as 4.3.1
I no longer have them Ismael. I just copied the content to a new identical page and then deleted the old one.
Ultimate Member seems to make the pages in such a way that they identify as posts. I’ve looked in the database and the post type is definitely set to page but Enfold still identifies them as posts.
Strange.
Delete the cache folder that is in your wp-content folder.
If you go back to using W3 it will just recreate it so don’t worry.
Hey paullindqvist
Mine turned out to be W3 Total Cache. If you have that enabled try disabling it and see if that makes a difference.
Hi,
I have this on 7 sites that I have running Enfold, 200+ non Enfold sites don’t do it.
I too have had this for months and months.
Hi,
Not a lot of point having a changelog if you don’t update it!
The changelog is now several versions behind……
Andy, you’re misunderstanding him.
AK-MUC is not saying he’s found a bug, he’s saying that the implementation is not very good.
I understand his point, it’s not very intuitive to have to tab through loads of tabs on mobile to navigate a strip.
Not working for me either. Created a test area and imported the 2017 demo and that is all messed up too (compared to your own 2017 demo)
Ok, I think we’ll have to agree to disagree. It’s not that I don’t like the theme – I do, it’s just that this doesn’t feel like a major release. Making a new demo is great but doesn’t mean you increment the release version surely? Setting lots of things up for the future is great but again, doesn’t justify a whole version move. I suspect that most people when they saw 4.0 was out leapt to the Themeforest page to see what incredible new things were available and were very disappointed.
As to only seeing one small bug in a third party plugin on old servers have you seen your threads?!
Many users could not access the admin screen
The editor is displaying multiple labels over the same spot making them unreadable
Many people are getting 500 server errors
Media library is filling with unwanted images from your demo without being imported – delete them and they reappear.
Sites not score way less on page speed tests than before – not sure why?
New back end preview on right just displays nothing on all but one of my installationsThe fact you had to rush out 4.0.1 shortly after release shows you’re aware of bugs surely?
Anyway, I’m not here to moan, as I said, I like Enfold and have purchased it several times, I just think 4.0 indicated a bigger release than what we had,
Hi Yiigit,
So basically you’re saying the same thing I did. It wasn’t a 4.0 release (which would indicate lots of new shiny things!)
If you read the changeling it’s bug fix after bug fix. There are a few small changes but on the whole is evolutionary not revolutionary.
It’s a point upgrade at best.
The National Photographic Society run our entire site on Enfold
The latest version of Enfold is 2015 November 17th – Version 3.4.3
This is definitely Yoast, it’s all over the forums, it’s breaking back end editors in Enfold theme, The 7, Avada etc etc.
I’m posting this in case it helps anyone else having this problem.
The problem was sort of WooCommerce (in this case) but could have been caused by other things too as the problem was the wp_options table had too many rows in.
We had thousands of products in our WooCommerce installation and there is a know bug in WordPress that when logged into the back end it causes an out of memory area (no matter how much RAM you have – we have 32GB) as it has a hard limit of 256MB built into the admin area.
If you have too many rows in wp_options it causes an out of memory error which is not displayed on screen unless you have error reporting turned on so most people won’t see it.
Our solution was to export the WooCommerce shop and put it on a subdomain in it’s own WordPress installation and then cleanse our wp_options table (there was all sorts of rubbish in there from previous plugins too) and then Enfold starting working again.
Hope this helps someone else with this error.
Short and sweet answer from them, they are not interested in making it work with individual themes, instead suggesting I contact the theme author.
Right,
Just tried that with fresh copy downloaded from ThemeForest and it still doesn’t work. Also downloaded a fresh copy of WooCommerce from their site and wiped the old plugin directory and uploaded the fresh one too.
As I said in an earlier post – disable WooCommerce and the site works just fine.
Hi Andy,
I’ll try this during a period of low traffic to my site.
I’ve been using Enfold for years but this just recently started to happen.
Right – getting closer – it now seems that the error disappears if I disable WooCommerce (but was working with WooCommerce for months before!)
I disabled it before but it had been cached so was still throwing the error.
I have a large shop on WooCommerce so don’t want to disable it, can this be debugged anywhere?
Hi
I tried that – waiting until it was 3AM here and then deactivated every plugin on the site and it still happens.
Rod
Hi
Any site (including your own restaurant demo) has this behaviour.
I am on a local development server so have no link I can give you but you can do it yourself :-
-
Create a page
Drag on fullscreen slider
Click and select fade images
Load 3 images (or more)
Preview pageThe last slide will “jump” to the first slide without fading.
