Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 46 total)
  • Author
    Posts
  • in reply to: ℹ️Something went wrong. Please try again! #49724
    KaraKara
    Participant

    You're welcome, Peter.

    in reply to: ℹ️Something went wrong. Please try again! #49715
    KaraKara
    Participant

    After a bunch of trial and error, this worked for me. I wouldn't have guessed Cloudflare was caching scripts in the backend, but it was.

    Fix MetaBox Group fields breaking in wp-admin (Cloudflare caching)

    Symptoms

    1. MetaBox Group fields don’t load in wp-admin (Builder / edit screens).
    2. Console shows errors like: Cannot access 'c' before initialization
    3. Hard refresh (Empty cache + hard reload) temporarily fixes it.
    4. Network headers for MetaBox JS show cf-cache-status: HIT.

    Cause
    Cloudflare is caching MetaBox’s webpack JS chunks (often under /wp-content/plugins/...) with a long TTL. When MetaBox updates, Cloudflare can serve a stale chunk that doesn’t match the current app.js, which crashes the admin UI.

    Step 1: Confirm Cloudflare is caching the file

    1. In Chrome, open the broken wp-admin page.
    2. DevTools → Network
    3. Click one MetaBox JS chunk (often named like 4988.app.js).
    4. Check Response Headers: If you see cf-cache-status: HIT → Cloudflare is caching it and likely causing the break.

    Step 2: Add Cloudflare bypass rules (Free plan)

    In Cloudflare Dashboard → your site:
    Bypass MetaBox plugin JS chunks (important)
    Create a Cache Rule:

    1. Caching → Cache Rules → Create rule
    2. If URI Path contains /wp-content/plugins/meta-box (or your MetaBox plugin folder name)
      AND
      URI Path contains .app.js
      → Bypass cache
    3. Make sure this bypass rule is above any rule that caches /wp-content/* or “static assets”.

    Step 3: Purge caches

    1. Cloudflare → Caching → Configuration → Purge Cache → Purge Everything
    2. Purge any WordPress cache plugin you use (e.g., Breeze).

    Step 4: Verify the fix

    1. Reload the wp-admin page and re-check the JS chunk headers.
    2. You should now see cf-cache-status: MISS or BYPASS (not HIT).
    3. MetaBox Group fields should load normally.
    in reply to: ℹ️Something went wrong. Please try again! #49704
    KaraKara
    Participant

    This site was on php 8.1 and I just upgraded to 8.3, the problem persists.
    (My host doesn't have 8.5 yet so can't try that.)
    Also running AIO Version 3.4.0, WP 6.9.

    Theme is Bricks, but changing to default theme doesn't help.
    Hosting on Vultr HF on Cloudways.

    in reply to: ℹ️Something went wrong. Please try again! #49694
    KaraKara
    Participant

    This issue is still happening. I was able to create a new set of custom fields earlier today, including a Group. But I cannot edit the custom field set now, nor can I create a new set that includes a new group.

    I get the same error: "Something went wrong. Please try again!"
    And two errors show in the console:
    https://www.awesomescreenshot.com/image/58557602?key=bade5115441d813ab615595613086dbe

    Deactivating all plugins, turning off cache, etc does not help.
    This is extremely disruptive - how can we fix this?

    in reply to: ℹ️Something went wrong. Please try again! #49538
    KaraKara
    Participant

    Perhaps it's linked also to MetaBox AIO not recognizing my license? The license page says it's confirmed, and I just removed and re-added it to be sure. But when I look at the options for custom fields, I can't select a Tab. It says: "Tab (Premium)" and prompts me to upgrade to MetaBox AIO.

    Note: I purchased my license from AppSumo in 2021.

    in reply to: ℹ️Something went wrong. Please try again! #49535
    KaraKara
    Participant

    I think it's related to the Group field.
    In a new set of Custom Fields, I just tried to add it and was immediately hit with "Something went wrong. Please try again!".

    Please let me know how to fix ASAP. I use Groups throughout many sites and they are connected to Bricks Builder queries - I need to be able to edit them.

    Thank you.

    in reply to: ℹ️Something went wrong. Please try again! #49534
    KaraKara
    Participant

    Oh and to note: I'm updated to MetaBox AIO 3.3.5. I tried deactivating all plugins and clearing cache etc etc. No luck. Hosting with Rocket.net if that helps.

    Don't see any errors in the log, but from the console:
    https://www.awesomescreenshot.com/image/57909569?key=07860e3136754c02df33805b351e7402

    in reply to: ℹ️Something went wrong. Please try again! #49533
    KaraKara
    Participant

    I'm still experiencing this issue - cannot edit any of the custom field groups. It loads briefly (flashes) and then I get the same error: "Something went wrong. Please try again!"

    KaraKara
    Participant

    Sent, and thank you!

    KaraKara
    Participant

    Hi Peter -

    This might help.

    This is what the console shows on the CPT = Member Contents, with "editor" supported.
    We can see the test field group showing up properly:
    https://tinyurl.com/2d3kzfgj

    And the "Member Contents Wizard" section with class="hidden"
    https://tinyurl.com/28pbn4bm

    KaraKara
    Participant

    Hi Peter -

    I've done exactly that and no luck.
    Screen recording: https://www.awesomescreenshot.com/video/25955993?key=bbc80aec7bf5e7227d1083c175865feb

    But, if I add the same custom fields to another post, they show up as expected.
    Screen recording: https://www.awesomescreenshot.com/video/25956296?key=75a46229b4b367951525b4c170d6f44c

    Conversely, if I create new custom fields to show up on the original CPT, that works fine, too.
    Screen recording: https://www.awesomescreenshot.com/video/25955993?key=bbc80aec7bf5e7227d1083c175865feb

    I have hundreds of posts created using the custom field group, connected to dynamic templates on the front-end, and so don't want to re-create these if possible.

    in reply to: Elasticsearch Support? #44906
    KaraKara
    Participant

    Hi - any word on having ElasticPress/Elastic Search recognize MB Custom Fields?

    KaraKara
    Participant

    Worked perfectly.
    Thanks for your help, Peter!

    in reply to: CPT Custom Fields Keep Disappearing #44348
    KaraKara
    Participant

    Peter - that worked perfectly.

    I assume that, as long as we trust the embed codes being used here, we shouldn't be concerned about turning off the sanitize feature?

    For what it's worth, Website A does *not* bypass sanitization and it still works perfectly.
    Same server and theme but a different plugin stack.

    Thanks very much!

    KaraKara
    Participant

    Hi Peter -

    Thanks for your response.
    It's because I have forums on the site and 'topics' is used there as the slug 🙃

    Is it possible to change the slug of the taxonomy without losing all of the data? I have hundreds of posts, all assigned to multiple topics - it would be awful to lose.

    I used to use Pods and I recall it had a way to update the database automatically if you had to change the slug. Is there an option for this here?

    Thank you!

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