Troubleshooting

Fixes for the problems site owners and members run into most often. Each section starts with the message or symptom you see.

---

“Revision history is part of the Developer licence and above”

Revision history and the diff view need a Developer or Agency licence. On a Personal licence, or before a licence is activated, the Revisions panel shows this notice instead of the version list.

SnipShare still records every edit on every tier. Only viewing the history is locked, so nothing is lost: activate a Developer or Agency key under SnipShare → Settings → License and the full history appears straight away.

See License and Revision History.

An app or script gets a 403 with snipshare_license_required

Logged-in REST requests from outside the site (Application Passwords, Basic auth or a token plugin) need a Developer or Agency licence. The error reads “Authenticated access to the SnipShare REST API from apps and scripts needs a Developer or Agency licence.”

What is not affected, on any tier:

• The site’s own pages. They send a valid wp_rest nonce, so creating, editing, starring and forking from the front end always works.
• Logged-out reads of public pastes.

See the REST API Reference.

A paste embedded on another website shows a plain link

Embedding pastes on other websites through oEmbed needs a Developer or Agency licence. Embeds on your own site (in posts, pages and BuddyPress activity) work on every tier.

See oEmbed.

Paste pages return “Page not found”

SnipShare registers its URLs (/pastes/, /paste/{hash}/ and the rest) and refreshes WordPress permalinks automatically when it is activated and whenever the URL bases change.

If you still see a 404:

1. Go to Settings → Permalinks and click Save Changes without changing anything. This rebuilds the permalink rules.
2. Clear any page cache or CDN cache, so an old 404 is not being served.
3. Make sure no other page or post already uses the slug pastes.

Old paste links stopped working after renaming the URLs

Developers can rename the /paste/ and /pastes/ bases with the snipshare_rewrite_slugs filter. Old links redirect (301) to the new ones automatically. If they do not, save Settings → Permalinks once, as above.

See Hooks and Filters.

“This paste has been burned after reading.”

A burn-after-read paste is deleted the first time someone other than its author clicks Reveal. This message means it has already been revealed, and it cannot be recovered.

What does not burn a paste:

• The author viewing it.
• Link previews in chat apps and email clients. The paste only opens through the Reveal button, so a preview bot cannot destroy it.

“Too many incorrect passwords. Please wait before trying again.”

A visitor gets five password attempts on a protected paste in a 15-minute window, then has to wait. Each visitor is counted separately, and one visitor unlocking a paste never unlocks it for anyone else.

Developers can change the limits with the snipshare_unlock_max_attempts and snipshare_unlock_window filters.

“You have created too many pastes recently. Please wait before trying again.”

Members are limited to a number of new pastes per hour (20 by default). Change it under SnipShare → Settings → Permissions → Paste Rate Limit.

Members who can moderate (editors and administrators by default) are not limited. Developers can exempt other users with the snipshare_limits_exempt filter.

See Permissions Settings.

“You have reached the limit of N pastes. Delete one before creating another.”

The site has a cap on how many pastes each member can keep. Raise it, or set it to 0 for unlimited, under SnipShare → Settings → General → Max Pastes Per User.

See General Settings.

The Pastes tab or paste activity is missing in BuddyPress

1. Check SnipShare → Settings → Integrations: Member Profile Tab, Activity Stream and Notifications are separate switches.
2. Activity items need the BuddyPress Activity Streams component (Settings → BuddyPress → Components).
3. Only public pastes post to the activity stream. Unlisted, private, password-protected and burn-after-read pastes never do, and a paste’s activity is removed when it is trashed, deleted, burned or made non-public.

See Integrations Settings.

The plugin will not activate

SnipShare needs WordPress 6.5 or later and PHP 8.1 or later. WordPress refuses to activate it on older versions and shows which requirement is missing. Your host can update PHP from the hosting control panel.

See Requirements.