Could not save the changes. Please try again.

PS: I’ve tried following the below link, but it didn’t help me.

https://premium.wpmudev.org/forums/topic/waf-conflicting-with-beehive/

Hi @wpkiller

I hope you are well.

Sorry to hear you are having this issue.

I checked the following link, and I can see the issue was related to our WPMU DEV hosting WAF, do you have any other WAF server side?

If not, can you try to re-save the settings and check for any log on Browser Console?

https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

Let us know the result you got.
Best Regards
Patrick Freitas

I didn’t make any change on my server (mod security is off).
Here’s the screenshot for console when trying to save changes:

View post on imgur.com

Hi @wpkiller

Thank you for the screenshot,

403 indeed is a forbidden status.
https://httpstatuses.com/403

Would it be possible to enable the debug mode by editing the wp-config.php?

Replace the line where it says:

define(‘WP_DEBUG_DISPLAY’, false);

To define(‘WP_DEBUG_DISPLAY’, true);

And then just below it adds the following lines:

// Tell WordPress to log everything to /wp-content/debug.log
define(‘WP_DEBUG_LOG’, true);

// Turn off the display of error messages on your site
define(‘WP_DEBUG_DISPLAY’, false);

// For good measure, you can also add the follow code, which will hide errors from being displayed on-screen
@ini_set(‘display_errors’, 0);

Note, it needs to be added before the line where it says: /* That’s all, stop editing! Happy publishing. */.

Retake the save process, and check if a log was generated on wp-content folder.

Best Regards
Patrick Freitas

Thank you for your reply.
I went to the site to do just what you’ve asked for (no need to treat me like a newbie, I know my way with WordPress…) but I was surprised to see all is in place. STATS are showing and even trying to re-save works.
Also, the 403 error is now gone from the console. And that’s without me doing anything, not even a plugin (any plugin) update.
Can I assume it was something on your side which you’ve fixed?!

Hi @wpkiller

I’m glad to hear it’s working now but no, it wasn’t anything we did “on our side”. The 403 error that you were getting was happening on your site/server so we don’t really have any access to it and it wasn’t related to any API connection to us or anything similar.

The 3.2.6 release that you are using is the most recent one so it wasn’t also an update that would possibly fix that.

Due to the nature of the error I’d say that the fact it “went away on its own” suggests that

– either there was some conflict on the site that went away after update of some other plugin or some changes on site
– or there’s some “aggressive” caching (most likely server-side) that affected it (though that’s not very likely to cause 403; not impossible but very rare)
– or… there’s some strong asset optimization (JS mainly) applied to the site and since plugin update (Beehive in this case) might sometimes cause such assets to be changed, a “stuck” set of optimized/cached asset can cause a lot of unexpected and difficult to troubleshoot issues.

Having said that, I’m not saying for sure that this is exactly what happened but based on information from this thread I’d suspect one of these things in the first place.

I’m glad to hear it’s working now and I think it should be fine but if this or very similar issue happens again, please update us and we’ll look into it further.

Kind regards,
Adam