Forum Replies Created

Viewing 30 posts - 1 through 30 (of 186 total)
  • Author
    Posts
  • Sorry for the delay. I think I sourced it to the Admin css stack for Enfold. It seems if I turn off Trebuchet MS from the font stack, everything works as expected. But, for some reason, having it on results in the tofu text. I verified that both machines tested on had Trebuchet MS loaded on them, so wondering if there is a specific version it is looking for. It seems to have the most problems with Chrome, but will occasionally show on Safari.

    Is there a way to have Enfold default to the system font first in the font stack? Yes, Microsoft made it cross platform and available, but setting it to system with sans serif fallback should theoretically allow it to work on nearly anything.

    This is probably the most basic site we would ever have, as it is a staging development site. We don’t have even a quarter of the functionality added in yet. Other than disabling Comments and Temporary Login, there is only one other plugin, GeoDirectory, and we have disabled that several time, trying to diagnose this. This site does not really get any more basic. I will say that we generally would be on an earlier version (6.5.x or 6.7.x) of WordPress, but wanted to start this with nearly everything current. php is 8.1x

    It is just the Enfold stuff, so turning off Enfold would yield me nothing to see.

    This reply has been marked as private.
    This reply has been marked as private.

    Sorry, missed another example of it rendering incorrectly in the editor, but correctly in the preview.

    https://oc.homebutton.us/wp-content/uploads/2025/08/Screenshot-2025-08-18-at-10.38.59-AM.png

    You had me look at the DB charset variable, but when looking at the WP Constants charset, it shows just straight UTF8. Probably makes not difference, but thought I would put it out there in case the difference does apply.

    The DB character set is as you posted.

    The greeking or tofuing is mostly with Enfold elements, so switching it does not really allow me to test like for like, as AVIA/ALB is not loading.

    https://oc.homebutton.us/wp-content/uploads/2025/08/Screenshot-2025-08-18-at-10.27.21-AM.png
    https://oc.homebutton.us/wp-content/uploads/2025/08/Screenshot-2025-08-18-at-10.27.41-AM.png
    https://oc.homebutton.us/wp-content/uploads/2025/08/Screenshot-2025-08-18-at-10.28.20-AM.png

    in reply to: ACF with Accordion element? #1484789

    Thank you, Mike!

    So, I think my dilemma would be how to make this repeatable, as I am trying to build these programmatically. Maybe I need to digest your response more, but am not immediately seeing how at the moment. Give me a day or so to go back through and experiment, but wanted to say Thank You for posting this while I do figure it out.

    in reply to: Adjust field choice in blog post grid view element #1484243

    Good day, Ismael!

    Thank you very much for the time and sharing this. I will try it, but am wondering if there would be some way to close the blog element and adapt it, so it can be used as a regular element (with specific changes. The primary reason is in the desire to build a framework for community sites going forward, where this would be a common need, and having an actual element means that adapting another that might be used would not limit that element’s capabilities in various use cases. Hopefully that makes sense.

    It has been a long time since I looked at adapting an ALB element, and know that a ton has probably changed. Is something like this possible today? Or, are there mechanisms coming down the road that might enable this to be an easier adaptation?

    If adapting this is possible, could you recommend a good starting point? I do use child themes be default, so wondering if it could just be a function of calling a customized element from within, or would it mean having to adapt the core theme files?

    in reply to: Version 7.0 – Strange search button text display #1478799
    This reply has been marked as private.
    in reply to: Version 7.0 – Strange search button text display #1478474

    That fixed it. I will get you temp login later today.

    in reply to: Version 7.0 – Strange search button text display #1478408

    Done.

    in reply to: Version 7.0 – Strange search button text display #1478403

    Unfortunately, the css you offered does not seem to affect it. I have it in the QuickCSS along with the Search element turned on, if you would like to see the results.

    in reply to: Version 7.0 – Strange search button text display #1478402

    I just turned it back on, and am including a link to a screenshot of the bug below.

    in reply to: Version 7.0 – Strange search button text display #1478401

    I had to turn search off because we were getting too many calls. I can turn it on again, if you want to see it.

    in reply to: Version 7.0 – Strange search button text display #1478365
    This reply has been marked as private.
    in reply to: Supporting Enfold with own plugin #1478364

    I am really hoping that editing archive pages is on the radar for features, considering we now have access to CPTs.

    in reply to: Version 7.0 – Strange search button text display #1478157

    Are there any temporary solutions you can see, beyond just hiding the whole search?

    in reply to: Version 7.0 – Strange search button text display #1478062

    code below:

    in reply to: Easy way to use ACF to drive EasySlider? #1470443
    This reply has been marked as private.
    in reply to: Easy way to use ACF to drive EasySlider? #1470031

    Oops, forgot to include more information that would help getting to it. (below)

    in reply to: Easy way to use ACF to drive EasySlider? #1470030

    Good day all!

    I got to play around with this briefly a week or so ago, but was not able to get it working and after trying a few different things, am still not getting it to work properly.

    I kept getting No slides available, the response if it does not get a slideshow id. After messing around with pulling other parameters, I noticed it would pull the number 3 when I queries using dynamic data for the “av_acf_slideshow_ids” which happens to be the number of slides I have assigned to that records repeater field. So, I think we are really close to it working, but my attempts to adjust it did not work. So, I am hoping you might take a quick look at it (link and creds provided below).

    -jason

    in reply to: Update on ACF support #1452604

    It is going to be worth it and probably the best thing to happen to Enfold since it came onto the market! Really, really excited to unlock a whole new way of managing and displaying content in a more meaningful, sustainable and organized way!

    Thank you Team Kriesi for finally making this possible! It has been a long time, but think this will unlock a sorts of new use cases for Enfold.

    -jason

    in reply to: Update on ACF support #1435481

    Good day, Günter!

    I just wanted to check in and see how progress was going. Any updates?

    -jason

    in reply to: Update on ACF support #1425633

    Hi team Kriesi,

    I hate to continue to be a persistent pest, but I continue to be asked about it and don’t have any answer to give anyone. Any timeline yet? With that functionality being actively advertised, used and showcased on many other themes/builders/frameworks, it is really hard to not be looking to other frameworks to achieve this functionality.
    -jason

    in reply to: Still fighting with managing default image sizes. #1418400

    Guenni,

    So, I am trying to do this step-by-step, removing the default Enfold-based image sizes first. I kept the bulk of your framework, but made a few little changes. I applied the code below to my child themes functions file, and then did a full regeneration of the images, and removed any images that did not have sizes anymore.

    // Start Removing Image Sizes - Rev 20230907-3 //
    
    // Remove or unregister unused WordPress Image Sizes (via Enfold)
    
    // Disable loads of Enfold & WP image sizes upon upload
    // do image sizes manually, double-size with high compression for retina screens
    // use Photoshop to set exact double size and quality between Q30 and Q40
    add_action('init', 'remove_enfold_image_sizes');
    function remove_enfold_image_sizes() {
      remove_image_size('square');
      remove_image_size('featured');
      remove_image_size('featured_large');
      remove_image_size('portfolio');
      remove_image_size('portfolio_small');
      remove_image_size('gallery');
      remove_image_size('magazine');
      remove_image_size('masonry');
      remove_image_size('entry_without_sidebar');
      remove_image_size('entry_with_sidebar');
      remove_image_size('shop_thumbnail');
      remove_image_size('shop_catalog');
      remove_image_size('shop_single'); 
      remove_image_size('shop_gallery_thumbnail');
    }
    // Remove unneeded WP image sizes
    add_filter( 'intermediate_image_sizes_advanced', 'prefix_remove_default_images' );
    // Remove default image sizes here. 
    function prefix_remove_default_images( $sizes ) {
    // do NOT remove small and medium sizes, they are used in backend Media Library!
    // unset( $sizes['small']); // 150px
    // unset( $sizes['medium']); // 300px
     unset( $sizes['large']); // 1024px
     unset( $sizes['medium_large']); // 768px
     unset( $sizes['1536*1536']); // 1536x1536px
     unset( $sizes['2048*2048']); // 2048x2048px
     return $sizes;
    }
    
    // Moduly Image Sizes
    add_image_size('Moduly-Square', 1080, 1080, false);
    add_image_size('Moduly-Horizontal', 1920, 1080, false);
    

    This is the result (on Performance Tab > Responsive Images Overview section), after the above adjustments.
    I do see the couple added image sizes, but unless I am a complete idiot, it still looks like the image sizes above are still being injected.

    Images aspect ratio: 1 : 1
    36*36 – Widget (added by theme)
    108*108 – thumbnail (WP default size)
    180*180 – Square (added by theme)
    540*540 – medium (WP default size)
    705*705 – Masonry (added by theme)
    1080*1080 – large (WP default size)
    1080*1080 – Moduly-Square (added by a plugin)
    1500*1500 – Fullscreen Sections/Sliders (added by theme)
    1536*1536 – 1536×1536 (WP default size)
    2048*2048 – 2048×2048 (WP default size)
    Images aspect ratio: 52 : 37
    260*185 – Portfolio small (added by theme)
    Images aspect ratio: 99 : 80
    495*400 – Portfolio (added by theme)
    845*684 – Gallery (added by theme)
    Images aspect ratio: 142 : 75
    710*375 – Magazine (added by theme)
    Images keeping original aspect ratio
    768*0 – medium_large (WP default size)
    Images aspect ratio: 845 : 321
    845*321 – Entry with Sidebar (added by theme)
    Images aspect ratio: 1210 : 423
    1210*423 – Entry without Sidebar (added by theme)
    Images aspect ratio: 150 : 43
    1500*430 – Featured Thin (added by theme)
    Images aspect ratio: 50 : 21
    1500*630 – Featured Large (added by theme)
    Images aspect ratio: 16 : 9
    1920*1080 – Moduly-Horizontal (added by a plugin)

    Guenni,

    I feel like an idiot on this, because it seems like I am doing it right, but am just not getting it to do what it would appear it should be doing. Any ideas where I have gone wrong?

    in reply to: Still fighting with managing default image sizes. #1418396

    Wow! Thank you Guenni! Lots to look over here, but thank you very much for this help!

    in reply to: WordPress Templates Drop-Down not visible #1417844

    Okay, so I think I might have figured it out, and hopefully this can be of benefit to others as well.

    I ran across this article from WordPress:

    To sum it up, the template files need to be in the Child Theme directory, using the WordPress/Enfold default templates as basis starting points.

    But, you need to add the following lines at the top (right below the first if switch that follows the open php tag.

    /*
    Template Name: Full-width layout (Rename to appropriate template name)
    Template Post Type: post, page, (insert your new cpts here)
    */

    Remainder of template follows, but that will finally add the Post Attributes meta box to the right side of the screen.

    Can something similar/related-to to this be added to the Enfold Docs?

    in reply to: WordPress Templates Drop-Down not visible #1417841

    Good day, Ismael.
    I generally turn off the block editor, as it confuses people and I would rather have them learn Avia through the Classic editor, so they gain the benefits of Enfold.

    Is the Block editor the only way we are able to switch templates at all?

    in reply to: Update on ACF support #1417646
    This reply has been marked as private.
Viewing 30 posts - 1 through 30 (of 186 total)