-
Posts
-
Hello everyone,
I’m an happy Enfold theme holder, and I can download its latest release whenever I want (via themeforest.net and also inside the site, via automatic theme updater). So how is that I cannot post to Enfold forums, because of that license being expired?
I’ve discovered a bunch of bugs that affect my site soon after the passage from 5.x to 6.x version, and I’d like to submit my evidences to the community, but I cannot (again: because of license expired on 2022).
If the license is expired, how is then possible that I can still download any last version, or upgrade from inside the site? This is kinda confusing.
Please advise. Regards, e.-Hey Enrico Baravoglia,
Thanks for your question, your product license to download an update from Theme Forest is lifetime, but a paid support license for the forum is only for six months or a year, based on what you chose at checkout.
Your support license ended 2022-09-04, to renew please login to your Theme Forest account and follow these steps
After you renew please login to the support forum and open a new thread with your question.Best regards,
MikeThanks Mike. Kinda odd that discovering bugs (because this is what we’re facing, soon after major update), and reporting them to the community, would be only possible after having paid for “support”. I’m not asking for support: I’m just asking that evident bugs are fixed, based on the evidence that we ourselves would go on to document in depth. We report bugs, and we should be paid for that? Shouldn’t it in fact be just the opposite? After all, we are working for you, thus helping you improve a commercial product (i.e.: purchased, i.e.: paid by us). Thanks for further replies, if any.
Cheers, e.-Hi,
I meant write for support you will need to renew your support license, using the contact form is not appropriate for support questions.Best regards,
MikeSo, dear Mike, we are all beta-testers, and we cannot report issues if not paying before being able to? If product license is perpetual, then I suppose to have a perpetual_and_working product. If the product I’ve paid for is not working in some of it’s functionalities (and this happens because of some version upgrade), then I suppose I can report the issues I face, just waiting for next commit to come, and to hopefully solve them all.
Again: should I pay to just report few bugs (with regards to a product I’m allowed to download to its latest release)?
I’m really curious about you reply. Thanks in advance, and best regards, e.-Hi,
Try disabling all of your plugins and any custom functions and clear your site and browser cache, if you still think that you have a bug that we can reproduce on our test sites then post it here and we will see if we can reproduce.Best regards,
MikeEven better: I will simulate the whole thing via to 2 identical sites, both virgin (no plugins at all, WP last release), and one being the clone of the other.
1st one will have the 5.x version of Enfold running, and the 2nd one will have Enfold last release.
Same code, same DB (schema/structure), same use case scenario. And you’ll see that 5.x version of Enfold will produce one output, whilst Enfold last release will parse a completely different one (unexpected, and breaking the standard page-layout), for the same URI/resource.
I’ll come back here within few days. Cheers, e.-Hi,
Try setting up two sites with the different versions and use the 2017 Demo on both, and then explain what the exact issue is and the steps that we can reproduce.
In order to report a bug we need to be able to reproduce so we can forward to the Dev Team.Best regards,
MikeHi Mike, I will surely follow your suggestions. See you here at the beginning of next week.
Cheers, e.-So we are referring to this: https://wordpress.org/documentation/article/embed-block/
That’s to say to how default WP “block editor” handles embeds, also with regards to a generic URI (an URI is embedded in terms of an IFRAME presenting the preview of URI’s content).
These are 2 virgin WP setups, one running under 6.5.5 WP, the other running under 6.6.2 (latest) WP version. Both cases theme is the standard “Twenty Twenty-Four” (v1.2).Output is just the same, meaning that soon after URI embed the subsequent “text after link” appears, without any white zone/area.
On the other hand here we have 2 different versions of Enfold (5.7.1 and 6.0.6) which behave in a different way;https://enfold-571.mydemo.it/blog/2024/10/19/hello-world/
https://enfold-606.mydemo.it/blog/2024/10/19/hello-world/In the 1st case (571) the “text after link” appears after a quite wide blank/white-area. That still is acceptable, but not correct.
In the 2nd case (606) the “text after link” appears after a huge and unaesthetic blank/white-area. And that might be a bug.
All those above mentioned 4 sites have no plugins at all.
Any idea? Thanks, e.-Hi,
Thanks for your patience, I couldn’t find a cause so I posted it to the Dev Team to review, we will write back when we hear back from the Dev Team, thanks for your patience.Best regards,
MikeThanks, Mike. As for now the viable workaround is just avoiding to qualify straight URIs (with underlying links) inside a paragraph. I’ll be waiting for any update, anyway. Cheers, e.-
Hi,
Thank you for the update.
How did you place the Embed block inside a Text Block element? The issue might be due the avia_small_fixes function in the wp-content\themes\enfold\js\avia.js file:
function avia_small_fixes(container) { if(!container) container = document; //make sure that iframes do resize correctly. uses css padding bottom iframe trick var win = jQuery(window), iframes = jQuery('.avia-iframe-wrap iframe:not(.avia-slideshow iframe):not( iframe.no_resize):not(.avia-video iframe)', container), adjust_iframes = function() { iframes.each(function(){ var iframe = jQuery(this), parent = iframe.parent(), proportions = 56.25; if(this.width && this.height) { proportions = (100/ this.width) * this.height; parent.css({"padding-bottom":proportions+"%"}); } }); }; adjust_iframes(); }Best regards,
IsmaelHow did you place the Embed block inside a Text Block element?
Well, I simply typed the involved URI, in a new line, at that was it. I did not actually use any Embed block: that IFRAME-embed was done automatically, and it’s the huge space underneath that URI that was our problem. It was a problem also with 5.x Enfold versions, but in last one it has to be taken into account.
Are you going to apply any fix in core-code? Thanks, e.-Hi,
Well, I simply typed the involved URI, in a new line, at that was it. I did not actually use any Embed block: that IFRAME-embed was done automatically,
The issue is that the Embed Block from the block or default editor is inside a Code Block element, which is why the script above is being applied. You cannot use an Embed Block inside a Code Block element by default. Did you switch from the Block Editor to the Advanced Layout Builder? You can only use one editor at a time; you cannot switch back and forth. We have forwarded the issue to our channel.
Best regards,
IsmaelYou cannot use an Embed Block inside a Code Block element by default.
So you should disable that function to be possibly applied via Enfold “Advanced Layout Builder”. If you allow people using it – again: we’re not talking about a “Embed Block” inside whatever other block could be – then you should be aware that even a single URI would automatically produce that IFRAME (this is WP standard behavior). We’re not talking about the moon, super sophisticated hacks, reverse engineering; we are referring to just adding a generic site’s address, and that’s it: the site preview is done behind the scenes (even at back-end level), and the problem arises when under such an iframe-rendered preview a huge-unaesthetic-blank space is added, disrupting overall site’s layout.
Did you switch from the Block Editor to the Advanced Layout Builder?
Nope, not at all: only and always used the “Advanced Layout Builder” (no way that I will ever use the standard WP “Block Editor”).
We have forwarded the issue to our channel.
This is super nice, thanks. All the best, e.-
Hey!
We have made the necessary adjustment to the avia_small_fixes function, and this should be included in the next patch.
Cheers!
Ismael
- The topic ‘License expired so no support available…’ is closed to new replies.