• Resolved teocuitatl

    (@teocuitatl)


    Hello Gutenverse team,

    I’m experiencing intermittent HTTP 500 errors, mainly on the first page load (frontend and admin-ajax), and I suspect it may be related to how Gutenverse generates assets (CSS/templates).

    Symptoms

    • First visit to homepage (/) often returns 500, refresh usually succeeds
    • Google Search Console reports 500 server errors during crawling
    • 500 errors also occur on /wp-admin/admin-ajax.php
    • Simply opening and closing the editor (without changes) sometimes triggers layout issues or 500 errors

    Key Observation (from debug.log)

    The WordPress debug.log shows repeated asset generation on almost every request, including homepage, editor, and even 404 templates.

    Example log excerpts:

    [22-Jan-2026 07:51:07 UTC] File created with name: gutenverse-template-404.css
    [22-Jan-2026 07:51:07 UTC] File created with name: gutenverse-template-404.css
    [22-Jan-2026 07:51:08 UTC] File created with name: gutenverse-content-22365.css
    [22-Jan-2026 07:51:08 UTC] File created with name: gutenverse-content-22365.css
    
    

    These file creation logs appear:

    • multiple times within the same second
    • on normal frontend requests
    • on admin-ajax calls
    • even when no content changes are made

    This suggests assets may be regenerated per request, rather than reused from cache. Hypothesis

    Repeated CSS/template generation may be causing:

    • CPU / IO spikes on first request
    • request timeout → HTTP 500 on shared hosting
    • crawler requests hitting uncached state more often

    Questions

    1. Is Gutenverse expected to regenerate CSS/templates on every request?
    2. Is there a setting to disable automatic regeneration, development mode, or verbose logging?
    3. Are there known conflicts with cache/minification plugins that could invalidate Gutenverse-generated assets?
    4. Any recommended setup to reduce server load in production environments?

    I’m happy to provide more logs or test specific settings if needed.

    Thank you!

    ### THEME INFO ###

    Theme Name : Kinderly Child
    Theme Version : 1.0.0
    Parent Theme : Kinderly
    Parent Theme Version : 1.0.1


    ### WordPress Environment ###

    Home URL : https://projectlook.co.kr/
    Site URL : https://projectlook.co.kr
    Login URL : https://projectlook.co.kr/wp-login.php
    WP Version : 6.9
    WP Multisite : -
    WP Debug Mode : Disabled
    PHP Memory Limit : 512M
    WP Memory Limit : 512M
    WP Language : ko_KR
    WP Upload Directory : ✔
    Number of Category : 7
    Number of Tag : 11


    ### Server Environment ###

    Server Info : Apache
    PHP Version : 8.1.24p1
    PHP Post Max Size : 100M
    PHP Time Limit : 600
    PHP Max Input Vars : 1000
    SUHOSIN Installed : -
    WP Remote Get : ✔
    PHP Image library installed : ✔
    PHP GD library installed : ✔
    PHP GD WebP supported : ✔
    PHP fileinfo library installed : ✔
    CURL Installed : ✔


    ### Active Plugins ###

    Disable Comments RB : by rbPlugins - 1.0.26
    EWWW Image Optimizer : by Exactly WWW - 8.3.1
    Favicon by RealFaviconGenerator : by Philippe Bernard - 1.3.44
    Gutenverse : by Jegstudio - 3.4.3
    Gutenverse Companion : by Jegstudio - 2.0.2
    Gutenverse Form : by Jegstudio - 2.4.3
    Site Kit by Google : by Google - 1.170.0
    UpdraftPlus - Backup/Restore : by TeamUpdraft, DavidAnderson - 1.26.1
    Wordfence Security : by Wordfence - 8.1.4
    WP-Sweep : by Lester 'GaMerZ' Chan - 1.1.8
    WP Content Copy Protection & No Right Click : by wp-buy - 3.6.6
    WP Super Cache : by Automattic - 3.0.3
    Yoast Duplicate Post : by Enrico Battocchi & Team Yoast - 4.5
    Yoast SEO : by Team Yoast - 26.8

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support putra1arya

    (@putra1arya)

    Hi,

    Thank you for reaching out.

    1. CSS regeneration
      No, the CSS file should not be regenerated every time the page is reloaded. We’re aware of this issue and are currently working on a fix. The solution will be included in the next update.
    2. Disabling CSS file generation.
      Yes, you can disable this behavior. Please go to WP Admin → Gutenverse Dashboard → Settings → Frontend, then change the Render Mechanism to Inline.
    3. Bug confirmation
      As mentioned in point #1, this is a known issue. Our team is actively developing a fix, and it will be released soon.
    4. Recommendations to reduce server load and improve performance
      In addition to the above, here are some best practices we recommend:
      – Use images in .webp format, as they are lighter and load faster compared to JPG or PNG.
      – Enable lazy loading for images so they load only when needed.
      – Optimize image dimensions and avoid uploading images larger than their display size.
      – Enable page caching (via a caching plugin or server-level caching) to reduce repeated processing. But if you do this please change frontend setting “Render Mechanism” to “Inline“.
      – Minimize unused blocks or sections on pages to reduce frontend rendering overhead.
    Thread Starter teocuitatl

    (@teocuitatl)

    Hi,

    Thank you so much for the quick and detailed response. I really appreciate it.
    Your explanation helped a lot, and it definitely increased my trust in the Gutenverse team.

    I’ve tried many page builder plugins so far, but Gutenverse has been the most intuitive and easy to use for me. I truly hope it continues to grow and gain more adoption.

    In my case, it seems the main issue was caused by Wordfence. After completely removing Wordfence and all related settings, everything is now working normally again. I think using a lighter security plugin is a better option in my setup.

    Thanks again for your support, and I’m looking forward to the upcoming update.

    Plugin Support putra1arya

    (@putra1arya)

    Hi,

    Thank you so much for the kind feedback, we really appreciate it. We’re glad to hear that our explanation was helpful and that it gave you more confidence in the Gutenverse team.

    It’s also great to know that you’re enjoying using Gutenverse and finding it intuitive. Feedback like this truly motivates us to keep improving and building the plugin further.

    We’d really appreciate it if you could leave us a 5-star review. It means a lot to us and helps us continue improving:

    Gutenverse : https://ww.wp.xz.cn/support/plugin/gutenverse/reviews/#new-post

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.