Forum or community plugin errors — posts failing to submit, notifications not sending, permission errors on categories — usually trace to a plugin conflict, a permission configuration mismatch, or a database issue specific to the forum’s own tables.
Forum / community plugin errors
A forum or community feature traced to the actual plugin conflict, permission mismatch, or database issue.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| A forum or community feature is throwing errors, failing to submit, or misbehaving | This fix covers it |
| The issue is member directory or profile display, not forum functionality specifically | Member directory & profile display errors |
| Two plugins are both trying to control access and conflicting | Access rule conflict between plugins |
| You want a forum or community feature set up for the first time | Worth discussing directly — likely a larger, dedicated setup rather than a repair |
What you are seeing
- Posts or replies failing to submit, or submitting without appearing
- Notifications for new posts or replies not sending
- A permission error appearing for members who should have posting access
- The issue possibly affecting only certain forum categories
Common causes
- A plugin conflict interrupting the post submission process
- A permission configuration mismatch between the forum plugin and membership levels
- A database issue affecting the forum plugin’s own tables
- A caching issue serving a stale version of a forum page
- A moderation or spam-filter setting silently holding legitimate posts for approval without notifying the poster
What we do
- Reproduce the specific error with a test post or action
- Identify the underlying cause
- Correct the plugin conflict, permission mismatch, or database issue found
- Verify posting, replying, and notifications work correctly
- Check across different member levels and forum categories
What is included
- The forum or community issue identified and corrected
- Verified working posting and notifications
- A check across member levels and categories
- The pre-fix backup, kept for 30 days
Not included
- Setting up a new forum or community feature from scratch — a separate, larger fix
- Member directory or profile display issues — a separate, related fix
- Moderating or removing existing forum content
- Ongoing monitoring for future forum issues
Questions about this fix
Could this be caused by a membership plugin rather than the forum plugin itself?
Yes, genuinely possible — many community and forum plugins integrate with a separate membership plugin for access control, and a mismatch between the two is a common cause of a permission-related error.
Will fixing this affect posts already submitted?
No, this addresses the submission and notification process going forward — content already in the database is unaffected unless it's specifically part of the reported issue.
Is this urgent if an active community is affected?
Worth prioritising if members are actively trying to engage and can't, since a broken community feature discourages continued participation quickly.
Does this cover private or members-only forum categories specifically?
Yes, we check across whichever categories are affected, including permission-restricted ones.
What if the issue only started after adding a new membership level?
That's a useful detail to mention upfront, since it often points directly at a permission configuration mismatch introduced by the new level.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.