Forum Replies Created
-
AuthorPosts
-
Can’t believe I totally forgot about this topic, sorry!!!
Well, better late than never I guess…
“Do you mean you want to send the user the data they filled out in the contact form? Can you please explain in more detail?”
Yes exactly – can there be an option for the autoresponder to send an email to the user that submitted the form, with a copy of their data that they entered, as well as a message from the site?
Eg:
The user sends form that says “Hi, can I get a price list?”
In return, they receive an email that says…
“You wrote: Hi, can I get a price list?
We are following up your enquiry now” (editable text in the contact form element)
Does that make sense?
April 30, 2021 at 7:53 pm in reply to: Using Responsive Images and Img Srcset with WordPress 4.4+ #1297626Can we get a list of elements currently NOT supported so we can make design decisions accordingly?
And also maybe a time-line of the ones being worked on next for support?
Hey, I saw that the new srcset for logo isn’t working due to this issue, but I think your next release includes a fix, right?
If so, this can be closed.
That fix from Guenni007 solved the problems I was having with this much anticipated feature on my PHP 7.4 install. Now it is working perfecting for me.
Hi guys,
Thank you again for your time on this.
I confirmed it still wasn’t working (not sure why it seemed to be for you) on multiple devices in different countries even.
But my developer discovered the root cause – the Analytics plugin CAOS has a setting “Capture outbound links?” which was enabled. There is a line in the code for this “window.location.href = link;” this was changing the URL of the browser.
Just though I’d report the fix here in case anyone has a similar issue in the future.
This can be closed, thank you.
P.S. Looking forward to the next release with the srcset updates! Any ETA yet?
Hi Ismael,
Thank you for your time on this.
I just checked the dev site and when logged in, yes it’s working. But when logged out, it is not. I cleared all caches, invalidation the CDN cache, and the problem persists when logged out. ( I haven’t changed any of the settings you disabled in the Litespeed plugin)
When logged out all files are loaded unminified and uncombined as I can see in the Chrome network panel. So I don’t think it is related to the CSS and JS settings directly, as the issue persists even with these settings disabled.
Can you please test it logged out and see?
Thanks again, I appreciate your help working through this.
- This reply was modified 3 years, 7 months ago by THP Studio.
Hi Ismael
Yes you can turn off the magnification settings.
However, I don’t think you can turn off the litespeed plugin entirely or the CDN won’t function properly – there’s a CDN tab in Litespeed that needs to be on (which it currently is) to work properly with the Google CDN and the Closte hosting setup. If you disable litespeed entirely you might get a false positive.
In my own testing from what I recall the issue remained with all other plugins deactivated other than Litespeed. So I think the answer is the issue remains when Google tracking was disabled, but please feel free to test that too.
Thank you for your help.
April 1, 2021 at 8:58 pm in reply to: Gallery Thumbnail Layout Issue on Chromium-based browsers #1291905Hi,
Thank you for that info.
This does seem to resolve the problem at least for me.
Please update me here with any more permanent solution in an upcoming release.
Regards.
Hi Yigit,
I’m afraid the CDN & Lightbox issues still exist :(
I think the reason we didn’t see them was we were logged in. But I applied those same changes to the live site (not the dev site), flushed all caches, and then tried it not logged in and the problem persists. So i’ve had to turn the CDN off again on the live site.
Can you please take another look on the dev site when you’re not logged into WordPress and you should see the issue.
The logins remain for you to use.
Thanks
- This reply was modified 3 years, 7 months ago by THP Studio.
No problem, thanks again.
Looking forward to the increased srcset support :)
Hi Yigit,
Excellent, thank you! It seems to have resolved the issue as far as I can tell.
Really appreciate your help, never would have though of the connection to that setting.
Any ETA on when the next Enfold release with the new srcset features will be released roughly?
Thanks again, always appreciate your helpful support.
Just thought I would add this seems to the the same (or related) issue I have also reported: https://kriesi.at/support/topic/gallery-thumbnail-layout-issue-on-chromium-based-browsers/
Hoping Enfold can work out the cause soon.
Hey Yigit,
The CDN is enabled on the dev site for you to checkout that CDN issue with the lightbox images. See an example URL below, but any gallery element will produce the same issue.
If you need login details you can use the ones below as well. Please let me know as soon as you don’t need them anymore (they’re also provided in this thread: https://kriesi.at/support/topic/gallery-thumbnail-layout-issue-on-chromium-based-browsers/ for another issue).
March 28, 2021 at 8:46 pm in reply to: Gallery Thumbnail Layout Issue on Chromium-based browsers #1290970Hey Rikard,
Details are below.
Please let me know as soon as you don’t require them anymore.
Thanks a lot
Tim
Hey that’s awesome thanks Yigit for reconsidering that.
I will let you know ASAP once we have the CDN up on the staging site for you to check out that lightbox issue.
Thanks again.
Hey Yigit,
Really appreciate the update.
Just on the point of the logo & srcset, I’m not sure of the reasoning that led you to not implement it, but one thing to consider is without srcset currently we need to load a logo double the normal size for retina screens. But for non-retina screens it’s loading a much bigger image than needed. So even though the logo files are admittedly relatively small, not having srcset prevents plugins that look for srcset in the code (such as a retina plugin) from being able to output a retina file. So we are forced to serve a larger file than necessary for all users. Just a thought.
As for the CDN, yes next week we will have a staging site ready for that particular client and we can turn on the CDN and provide you with a URL to view the problem. I’ll let you know when it’s live.
Thanks again.
I understand, thanks for the follow up. Hope it makes it into a future release in the not-too-distant future :)
Hi Gunter,
Just wanted to check if this was in the pipeline at all, or not? If not, I may have to look at custom coding it ourselves for some of our clients.
Thanks again.
One other related srcset request – can it also be implemented for the site’s logo please?
I see in the change log for the upcoming release you are already working on some of these – thank you so much! This is why I love using Enfold and keep buying more and more licenses – excellent support and you listen to our requests (also, I had to use Elementor the other day to fix a new clients site – THE WORST!! Please keep working on the ALB, it’s SO much better to use than Elementor!)
Hi Gunter,
Excellent support as always, thank you very much.
Regards.
Hi Yigit,
Another issue with the lightbox I wanted to raise, as discussed here: https://wordpress.org/support/topic/issue-with-lightbox-3/#post-14174307 ( thought it was Litespeed related, but seems it’s not).
You can’t test it live using those links at the moment, as we have the CDN turned off so its not broken.
But if we try and serve the images to the lightbox via the Google CDN (which changes the URL structure from /localsite/xxxxx to /cdnname/xxxxx then the lightbox fails to work properly – current page URL is replaced by the images actual URL.
In short, it seems the lightbox doesn’t like working with ‘external’ images (even if the entire site is run via a CDN), as mentioned by Litespeed support.
Can you please look into this fix as well?
- This reply was modified 3 years, 8 months ago by THP Studio.
Excellent, thanks a lot
Hey Yigit,
Thanks for the reply and confirming the lightbox isn’t creating srcset.
No I don’t want to display full size images, but it would be a nice improvement to have srcset enabled in the lightbox as well so that smaller sizes can be loaded as needed on mobile devices.
Thanks
Hi Gunter,
Brilliant, thank you. I think it would be a really nice win for your users.
Hi Rikard & Others,
Thanks for the reply.
I really agree with Gueni007 and BigBatT that the Advanced Layout Builder is one of the key unique selling points for Enfold. In fact, I just referred someone to use your theme over the weekend, and it was the ease of use of the layout builder as compared to Divi, Elementor etc that sold them on it. Obvisouly you have your reasons to integrate Elementor, but please, do not neglect your own ALB – it is the reason I love Enfold and as Gueni007 said, i find it WAY quicker to use than your competitors.
Anyway, I hope Kriesi can consider committing to a clear roadmap and regular updates on where the development is going. For instance, 2021 will be big on Core Web Vitals and it would be great to see any performance improvements that the team are working on (just as an example). Clear, regular, consistent updates would strengthen the confidence of your already loyal customer base (I just bought 6 new licenses over the weekend) and inspire excitement for the theme – leading to more sales, surely.
And while this thread: https://kriesi.at/support/topic/enfold-upcoming-fixes/ has been helpful, it hasn’t been updated in 22 days, so again doesn’t really help us stay up to date with the progress behind the scenes.
Regards
- This reply was modified 3 years, 11 months ago by THP Studio.
November 27, 2020 at 3:52 pm in reply to: Accessibility Tweak On Easy Slider (Possibly other elements) #1263542Great, thanks for the feedback Mike.
November 26, 2020 at 10:15 pm in reply to: Accessibility Tweak On Easy Slider (Possibly other elements) #1263375Hi Mike, any news on this one?
Thanks
November 4, 2020 at 3:32 pm in reply to: Logo has hard coded image sizes that are incorrect #1258300Hi Yigit,
Sorry, for some reason I never got notified of your reply, so I just saw it now.
Yes it is important to have the width and height attributes in there, but they shouldn’t be arbitrary ones. They should be coming from the logo size selected, surely.
This helps with things like content layout shift, which will be a ranking factor in a few months time.
Thanks
October 28, 2020 at 4:06 pm in reply to: Accessibility Tweak On Easy Slider (Possibly other elements) #1256410Great, thanks Mike, yes that is what I was suggesting.
I appreciate your help.
October 27, 2020 at 3:16 pm in reply to: Accessibility Tweak On Easy Slider (Possibly other elements) #1256096Hi Mark,
Ok I see where you’re coming from. However the same result is flagged on either mobile or desktop – it’s not mobile specific.
As for your thought of having these off for mobile, now that I look at it on my phone, I agree, these should be turned off for sure. However I can’t see a straightforward way of turning the controls off ONLY for mobile within the ALB element? I know I could duplicate the element and have one for mobile, one for desktop but that seems like a convoluted solution to the problem. Can we have an option within the slider elements to display controls on mobile on/off?
Finally, I think I should leave the name or title attributes up to you and your team to decide. I’m simply pointing out an issue that I was hoping could be corrected relatively easily.
Thanks for your help Mike, much appreciated.
P.S. While I have your attention, any chance of getting some more news/roadmap/blog post on the future of Enfold? I love the theme and have used it since around v2 I think and run it on all my clients sites, but it seems (from the outside at least) that development has stalled on it to a degree and it’s mostly maintenance and bug fixes happening lately. The last blog post about it was over a year ago. Would be very reassuring to know what is coming down the line.
-
AuthorPosts