Forum Replies Created
-
Posts
-
Thanks. I’ll just wait for 4.3.2 at this point. Too many mods / hacks to get basic functionality working again. I feel like every mod breaks something else, and I don’t want to end up with Frankensteined code that I have to go back and sort out.. I would rather stay on original release channel.
I assume developers will implement video fixes in the next update? I feel like I have been saying that since September 2017… :)Thanks
RobGuenni007 I have noticed on 4.3.1 sometimes the sliders appear fine and other times they don’t appear at all. It seems random… sometimes reloading page fixes it…. until it breaks again. Is this what you are seeing?
With further testing, I can also confirm that while this fixes the self-hosted videos (except disables controls so users can’t pause), it breaks the auto-play for Youtube hosted videos…..
I can confirm that the above code does get the self-hosted videos working, but controls are disabled so it’s impossible to pause them? Did I do something wrong?
Thanks
RobIs the fix above included in 4.3.1 or are we supposed to paste it even after updating to 4.3.1? Thanks
I fixed it…. based on this thread:
https://kriesi.at/support/topic/4-3-1-lightbox-not-working/
I realized that my child theme header.php needed to be updated with the new code since 4.2.6 from Gunter about the Lightbox… now lightboxes are working again!
Hope this helps someone else.
Thanks
RobSame problem. Solved it by adding LayerSlider element in Avia Layout Builder. The shortcode no longer works in 4.3.1.
4.3.1 did not fix the self-hosted video issue, and it adds an issue with Masonry where lightboxes no longer appear (separate thread opened for that issue since it’s major).
Link to logins in private content.Not my thread, but It works… and then after you add the element to a page, shortcodes work farther down on the same page.
Hi Ismael!
The video bug is still there… (see link in private content) on 4.3.1 and now there is a new bug in Masonry Element (see separate thread I and many others started).
But yes the 404 bug is fixed, which is very good news!
Best,
RobGood news – Yigit discovered that today’s Enfold update fixes the 404 errors on Optima Express… so original poster, you can update to 4.3 to fix the 404s. Please note that there is a new bug with the Masonry Element (clicked photos do not launch lightboxes) and the background video issue still exists. :(
Ryan, that shared folder has every version except 4.2.3… is that in there somewhere? I want to make sure I save 4.2.3 in my theme vault in case I ever get to update to 4.3. (Right now I can’t because it breaks my site’s functionality) Thanks Rob
Every single update since the middle of last year has had major bugs that have to be patched in the forums. This video bug has been around on and off since about that same time.
With respect — the coders need to focus on stabilization of this theme before they focus on optimization.
Thanks Mike. I went into Optima Express plugin on the staging site and un-registered the plugin then registered as a demo plugin so we can test / work on it there without it messing up the Optima Express on the production site. In short, feel free to do anything you want to on the staging site.
Thanks,
Rob@Mike, were you able to work on this some more? This is a critical issue that is going to affect all Enfold real estate sites that use Optima Express, which has 100,000 users at this point across all themes. I would hope that if the mods can’t tackle this that Kriesi would look at it. I am happy to make staging site / SFTP / whatever you need available to fix it.
Thanks
RobPS Does that iHomefinder site look familiar? It’s because they used ENFOLD to create their site… which, incidentally, is the main reason I went with Enfold in the first place was I figured if they used it for their own site, it would be 100% compatible with Optima Express.
:)
Interesting. Hoping that will help the mods, especially the part about PHP sessions.
This problem occurs on WP Engine in staging site as we discovered today, and the staging side is NOT cached so I no longer think it’s a WP Engine caching issue. Something about cookies / PHP sessions have changed with this new Enfold version and that’s not “playing well” with Optima Express.
I’m sure the team will figure it out for us!
Good question… I use the Facebook Jetpack widget and it does seem to work… shh, don’t tell Facebook! ;)
Yes based on repeated threads in the forum and my own experience with 4.3, loading only the used items is a recipe for disaster. At one point on the front end it wasn’t displaying the spaces and instead was displaying a message telling me that element wasn’t enabled… until I enabled all items.
I can work around that bug, and work around the video bug, but can’t work around the iHomefinder 404 bug unfortunately.Hi Mike,
– Object caching is disabled. Problem still occurs.
– Jetpack is installed. Problem occurs even if it’s disabled.
– Winner winner chicken dinner… problem DOES occur on staging site! Woo that’s good news, so we can fix it on staging site. I forgot to use a “non logged in browser” when i was checking it.
– Posting credentials to staging site in private content just in case you want to nose around there. Jetpack is deactivated there.
– Feel free to do anything you want in staging site… I can always push fresh copy from production.
– Let me know if you want SFTP credentials.Thanks!!
RobHi Vinay,
Yes, I set “Ross” to large because before I did that, the Ross button came in smaller because the city name is so short, the button became smaller. If you look on mobile you will see that each button, not just Ross, is responsive so they are all slightly different sizes.
How do I make them the same size on mobile (and I assume desktop will follow).
Mobile first design! :)
Thanks
RobAs an aside….
After the big Facebook scandal, Instagram now requires an API so sites can no longer “scrape” Instafeeds and republish them… I don’t think the current widget will work reliably until an Instagram login is added to it. The above plugin (and other Instafeed plugins) all require login first to your Instagram account.
