Forum Replies Created
-
AuthorPosts
-
Hi,
Updating to 4.5.5 isn’t possible, it seems – our site is at 4.5.4, but it is saying no update is available. Why?March 22, 2019 at 10:25 am in reply to: CSS file merging and compression breaking CSS-links #1081781This reply has been marked as private.Hi!
Before we do this, though, have you been able to reproduce the issue on your test installs?March 13, 2019 at 11:02 pm in reply to: CSS file merging and compression breaking CSS-links #1078428Hi!
It’s the merged CSS file (/wp-content/uploads/dynamic_avia/avia-merged-styles-*ID*.css) that is generated when CSS file merging is active. The affected CSS is in the Quick CSS-field in the Enfold settings.Hi!
Thanks, I realised I was imprecise – I mean, specifically, that the fonts included in Enfold, like fontello, are missing a woff2-version, meaning that browsers that support woff2 still have to download the bigger size woff-file.Hi! Implementing WOFF2 will improve pageloading times for all your users, so it is definitely worth the time it might take to implement (which should not be much). Can you please consider this?
October 19, 2018 at 3:55 pm in reply to: 4.5 problem with fullwith sub menu – not clickable #1023972Actually, it seems this is the solution:
#top .av-submenu-container.av-sticky-submenu { z-index: 2; }
October 19, 2018 at 3:47 pm in reply to: 4.5 problem with fullwith sub menu – not clickable #1023970Hello,
The solution is to set
#top .sticky_placeholder { z-index: -1; }
Can you add this to an update, Enfold team? Very impractical that all sub menus has stopped working…
Hey John,
How far in the future? This significant change in functionality was released almost two months ago, I expect an update soon.
Hey, any news?
Hey Ismael,
Thanks for being understanding.
I am afraid setting the blog style to Modern Business changes more than just the categories, as you can see by comparing the links below.Modern Business has a different layout, is built differently, and will require lots of time tweaking CSS to make it look the same as the old version of Enfold with the business theme looked like.
I have a proposal for a solution – release a new update of Enfold featuring either an option in the settings, or a
add_theme_support('business_category')
feature for child themes, activating blog categories the way they used to be, allowing you to keep the changes you made for the majority of your users, but allowing customers who did not want this change to revert it without having to edit the main theme files.
What do you think about that?Victoria, I am still waiting to hear back from you.
Victoria, I will not make an edit to the main theme files as this will sooner or later break in an update of Enfold. Again, I’m asking you to revert this change, otherwise we won’t be able to continue buying Enfold licenses for our projects, if you suddenly make these changes you might deem small but for your users might be huge visual changes.
It’s obvious this wasn’t a change wanted by your users, both us and Poirot and more have expressed our views and wish for the categories to come back.Please change this as soon as possible and publish an update of the theme. We have bought multiple Enfold licenses, so you owe us this much.
Hey again,
Victoria, your answer is not OK. The elegant blog style is significantly different from the Business blog style, which we’re using on multiple sites running Enfold. I understand the need for updating some things in the theme with updates, but you cannot simply remove whole features form styles! You have got to solve this problem by reverting the Business style the way it was – with categories intact.
We are loyal customers of Enfold, and we are running enfold on multiple sites, so frankly, I’m disappointed in your answers so far.Hello Victoria,
That’s a pretty disappointing answer – you can’t simply change things like this for existing styles without telling users.
Hey Andy,
Please look at the difference between the live site and the staging site – the categories are gone on the staging site with the latest version of Enfold installed, it is not in the HTML nor is it shown on the frontend site.
Hey, I’ve added access info in the private content box.
Before updating:
https://cl.ly/3K0e1B0Q2v3G
After updating:
https://cl.ly/0m350E3i2N0SAs you can see, the element
<span class="blog-categories ...">
is totally gone in 4.0.2.This is the shortcode generating the blog posts element:
[av_blog blog_type='posts' categories='4,11,3,2,1' link='category' blog_style='blog-grid' columns='1' contents='excerpt' content_length='content' preview_mode='auto' image_size='no scaling' items='1' offset='0' paginate='no' conditional='' custom_class='content-bottom-left full-width']
I tried the most recent version.
When displaying blog posts in grid mode, the category of the blog posts are supposed to show up on the site. In 4.0.2, the categories aren’t being displayed.
If you still need screenshots to understand the problem, please ask again :)
I’ve got the same issue!
February 28, 2017 at 4:24 pm in reply to: Performance issue with LayerSlider (hidden assets loading and no lazyloading) #753024Hey,
Thanks! I just tried it out, and it does feature a somewhat patch – the images are still being loaded, but for the right screen size – not the largest size it can find, which is great news :)
February 21, 2017 at 5:17 pm in reply to: Performance issue with LayerSlider (hidden assets loading and no lazyloading) #750055Crimson-Guard, did you ever find a solution for this?
February 13, 2017 at 3:21 pm in reply to: "" in image title/description of featured image on single post #746448Here’s where the details are inserted:
https://cl.ly/3a4539222b3dThe error in your code is most likely somewhere in the /enfold/js/avia.js-file, on the lines 941-950:
image: { titleSrc: function(item){ var title = item.el.attr('title'); if(!title) title = item.el.find('img').attr('title'); if(!title) title = item.el.parent().next('.wp-caption-text').html(); if(typeof title == "undefined") return ""; return title; } },
When you’re doing
.html()
, you’re getting the raw html string – you should escape the input so it’s safe to use in a title-attribute, where it will then later be used in the lightbox – setting the title-attribute to a raw HTML-string is very bad, for obvious reasons.
What happens is, your code essentially messes up the HTML of the page, as shown in the screenshot, in cases where"
are in the image description/title.https://cl.ly/2I1Y3P0G2w3w
https://cl.ly/0y010M18032s- This reply was modified 7 years, 9 months ago by emilbroll.
February 10, 2017 at 2:26 pm in reply to: "" in image title/description of featured image on single post #745422Hey Rikard,
I’m sorry, it’s evident that I haven’t been able to explain the issue properly.
The issue is as follows:
On single blog posts, the featured image is displayed above the title and content of the post. If you click on the featured image, a lightbox/popup pops up, displaying the full image with an image caption being displayed. This caption is usually the title of the blog post, but if you have set the alt text/description/title/caption of the image in the media library of wordpress, that content is used instead.
So: this has nothing to do with the title-attribute of the image HTML element, it is an issue of how the alt/desc/title of the image is processed before being displayed in the lightbox. I haven’t studied the code responsible for this lightbox, but it pretty obviously isn’t dealing with ” the right way, that’s what I meant by there being something wrong with your code – ALL characters can be displayed on the web, telling users to “not use this or that character” is avoiding the real problem – that the code isn’t good enough.
February 9, 2017 at 11:09 am in reply to: "" in image title/description of featured image on single post #744742Hey, sorry to be blunt, but that is not a solution (and of course that’s what I have done temporarily until you fix it), that’s circumventing the actual problem – there’s a problem in your code, and you need to fix it.
- This reply was modified 7 years, 9 months ago by emilbroll.
You didn’t really answer my question the first time around either:
Can you explain your process of choosing which feature requests are implemented and the timing of this? There are currently eight (8) feature requests with over 100 votes, meaning users really really want you to implement them, so why aren’t you?
In total there are over 450 feature requests on that site, seemingly within a 12 month period, so 1/450 = 0.22% of feature requests have actually been implemented. That’s pretty disappointing, considering how many people use your theme on a day to day basis.
Hey! I’m pretty disappointed to see that none of the feature request have yet been addressed. Are you going to use the feature requests at all, or are you not actively developing the theme with the consideration of your users wishes in mind?
Hey Yigit, I’ve done that now – I did post a thread a while ago regarding just this – how you’ve had this feature request page now for over a year without completing more than a single request, so you sending me there to request features seems a bit of a waste on my part, since it seems you’re not taking any of the requests into consideration anyway. Enfold is a great theme, so I wish you could keep actively developing it with your users requests in mind…
Well, you’re not reading the full question perhaps, try with a file with the .svg extension and you’ll see what I mean.
Hey,
Unfortunately not, in Twenty Sixteen, the alt-text is fetched correctly, this must be an issue with Enfold.
See this post for how it’s supposed to be: https://kriesi.at/support/topic/alt-tag-and-title-tag-for-avia-images/ -
AuthorPosts