Install confidently.
Build without guesswork.

System requirements

• A working self-hosted WordPress website
• An administrator account with permission to install plugins
• HTTPS is strongly recommended for customer and licence security
• A valid licence for protected updates and commercial use

Install RaffleFlow

1. Download the RaffleFlow ZIP from your customer account.
2. In WordPress, open Plugins → Add New Plugin → Upload Plugin.
3. Select the ZIP file. Do not unzip it first.
4. Choose Install Now, then Activate Plugin.
5. Open RaffleFlow from the WordPress administration menu.

Activate your licence

1. Copy the licence key from your purchase email or customer account.
2. Open the RaffleFlow licence screen in WordPress.
3. Paste the key and select Activate.
4. Confirm that the screen shows an active licence and the correct plan.

Licence server details are built into the product. Customers should never need to enter or change the licensing server address.

Create your first campaign

1. Open the Setup Wizard or select RaffleFlow → Campaigns → Add New.
2. Choose a blank campaign or one of the campaign templates.
3. Add the campaign name, dates, rules, prizes and visual branding.
4. Configure entry access, consent text and draw settings.
5. Save the campaign and preview it before accepting entries.

Publish the campaign

Use the native Gutenberg blocks for the cleanest setup. Add a new WordPress page, select the required RaffleFlow block and choose the campaign in the block settings.

Legacy shortcodes remain available for existing pages. Test the page while logged out before sharing it publicly.

Safe updates

Use the normal WordPress Updates screen. Keep the licence active so WordPress can retrieve the protected package. Back up the database before major updates and never remove plugin data tables during a normal update.

Common issues

System requirements

• WordPress 6.4 or newer
• PHP 8.2 or newer
• HTTPS for licensing, secure accounts, uploads and developer webhooks
• Enough storage and upload capacity for the community media you allow
• A staging environment for testing alpha updates

Install SMitov Social

1. Create a complete backup or staging copy of the website.
2. Download the plugin ZIP from your customer account.
3. Open Plugins → Add New Plugin → Upload Plugin.
4. Upload the ZIP, install it and activate SMitov Social.
5. Allow the initial database migrations and page setup to complete.

Activate the licence

1. Open the SMitov Social control centre and select the licence area.
2. Paste the licence key supplied with your purchase.
3. Choose Activate and confirm the site is connected.

The trusted update and licensing connection is preconfigured. Do not add third-party licence endpoints or expose licence keys in screenshots.

Complete the initial setup

1. Review platform identity, registration and access settings.
2. Set community privacy, moderation and media limits.
3. Choose Light, Dark or Automatic frontend appearance.
4. Check email delivery and notification preferences.
5. Create two test accounts and verify registration, profiles, posting and privacy before launch.

Community pages and blocks

SMitov Social uses native dynamic Gutenberg blocks and can create its core pages automatically. These include the social home, activity feed, member directory, current-user profile, access portal, notifications, groups, privacy centre and discovery.

Do not delete automatically created pages while their blocks are in use. When changing a site theme, test navigation, headers and community page widths on staging first.

Security and privacy checks

• Review Security diagnostics after installation
• Keep REST and AJAX rate limiting enabled
• Configure privacy retention and personal-data tools
• Use supported file types and conservative media limits
• Never disable same-origin protection to work around a theme or caching issue

Update and recovery

SMitov Social validates protected update packages and includes recovery checks, but a current external backup is still required. Test updates on staging, verify database migrations, then check the feed, uploads, messaging, groups, notifications, discovery and privacy controls before updating production.