Forum Replies Created

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • in reply to: Instagram Widget Issue #1228761

    Seconding the issue. Getting the same error message and the site is super simple, so there are no weird configs.

    The fix page Jasmer links above says you can get results using a hashtag instead of username, but we need the “follow me” on Instagram to function, too.

    Please advise. Thanks!

    Hi, Rikard,

    I ran the updates and so far it looks pretty good, but I’m seriously knocking on wood. I’ve only seen one incident of that error recently, but since the sites have very little traffic, I’m not sure if it is fixed or if the error event just wasn’t triggered. What, exactly, is the process going on when the error below happens? What does helper-assets.php do at line 342?

    PHP Warning: Invalid argument supplied for foreach() in /home/XX/public_html/YY/wp-content/themes/enfold/includes/helper-assets.php on line 342

    Will do.

    I was wondering if those various errors listed in the original post could lead to resource drain / site timeout situations.

    This reply has been marked as private.
    in reply to: Not getting pagination buttons #1215069

    BINGO! Works now – even with the slider on the page.

    Thanks!

    in reply to: Blocking on GTMetrix #1214150

    Hi, Rikard,

    Any additional thoughts on the issue above?

    As I mentioned, Enfold is the one thing common to the sites that are bogging down. Are there calls or bits of code particular to Enfold that could be causing these timeouts?

    Also, as mentioned above, how do “blocked” results in GTMetrix relate to the operation of Enfold?

    Thanks!

    in reply to: Not getting pagination buttons #1214149

    Hi, Mike!

    Thanks for taking a look… The two issues:

    1) The mobile view is inconsistent. That page still shows up as a tiny desktop (sidebar on side) on my Android (3 different browsers) and on an iPhone. However, I ran the page through an online emulator and it looks OK there. Any thoughts on why there would be inconsistent results?

    2) The pagination button issue isn’t fixed by getting rid of the slider. I created a duplicate page that had nothing but the blog in the body and it still has no pagination buttons.

    in reply to: Not getting pagination buttons #1212795

    Please see below…

    Note second (related?) issue

    in reply to: Pagination #1212423

    There may be more than one (or a better) way to do this, but I’m dealing with the same thing right now for a site.

    If you’re using the Advanced Layout Editor…

    In the page editor, go to the page that has your Blog and click on the Blog element itself. It’ll then have three tabs: Content, Styling, Advanced. Click on STYLING. On that tab, there’s a simple PAGINATION section that will let you choose how many blog posts to show and whether to paginate.

    Hope that gets you at least closer to a solution.

    Thank you, both!


    @Guenni007
    do you know if the “un-optimization” is a one-time thing or on every serving of the image? If I ran the account images through something like a WP-Optimize plugin AFTER upload (which sends it out to reSmush.it), will they stay optimized or will Enfold try to re-un-optimize them?

    Do you have other plugins installed? I’ve seen Yoast SEO and Wordfence trigger phantom “update plugin” notifications in WordPress. There may be others. The Yoast SEO one can be fixed with a small plugin called Hide SEO Bloat that not only removes the phantom notification, but also strips out a bunch of clutter.

    I’ve also seen that notification if a plugin simply has it’s own little notice window active in its settings or similar pages.

    in reply to: Blocking on GTMetrix #1211609

    Hi, Rikard,

    Giving the Delete old CSS/JS button a try. I will try disabling the security plugins, but I’ve got another pair of higher-trafficked, greater content sites (same host company, same plan, different account) that don’t use Enfold and they’ve used those plugins (and more, like the backup, etc) for some time without the same issues. I’m playing detective and seeing “what’s different & the same between the two accounts” to narrow things down. Those plugins are common to all sites. Wht isn’t common is Enfold. Not saying it is bad code. Maybe it is a bad setting, which is why I gave you the logins. There’s got to be a reason why GTMetrix waterfall is showing 65+ entries with “blocked” time of up to 2 full seconds. I’m also getting a boatload of I/O & PMEM faults shown in the cPanel Resources report. And these only happen when someone tries to log into one of the admin panels (or tries to switch between admin panel sections). I even tried disabling the various stats plugins, but I think they’re more the victims (they display slowly) than the culprits. Could there be other calls or bits of code (similar to the admin-ajax.php issue some people have?) that are causing this? Could Enfold want something from the server or browser that they don’t want to give, so it is timing out?

    And about my original question… Can you OR ANYONE enlighten me about the “blocked” result in a GTMetrix waterfall chart? That’s what leads me to believe that one of the players in the game (Enfold, the browser, the hosting server) might not be playing nice with the others.

    • This reply was modified 4 years, 7 months ago by amz. Reason: Added discovery about page behavior on mobile
    in reply to: Blocking on GTMetrix #1211354
    This reply has been marked as private.
    in reply to: Enfold "Band" and digital music downloads #1138136

    Thank you! This is why I love Kreisi & you folks. I went ahead and bought Enfold for this project because I figured you’d come through with a good answer. I’ve built Enfold sites before from scratch, but this’ll be my first time using one of the existing demo templates (“Band”). My dad has a tiny classical record label and this site is my gift to him. Any tips or tricks for building a Band site from demo data would be appreciated. Again, THANK YOU!

    Are you saying to:
    1. Run the update again to 3.6.1
    2. Have it crash and throw the fatal error.
    3. Go into FTP and rename the directory to “enfold2.”
    4. Log into WP-Admin (since the “enfold” theme doesn’t exist after rename)
    5. Go back into FTP and rename “enfold2” to “enfold.”
    6. Go to WP-Admin and activate the “enfold” theme

    Is that correct?

    When I did something similar to that on my own, all it would do is give me the fatal error again. As I mentioned, I watched the update closely and the UPDATE breaks. It does not complete. WordPress shows an error in the update status. When you try to do anything after that, the blockquoted fatal error shows as plain text on a blank screen.

Viewing 15 posts - 1 through 15 (of 15 total)