Social Revolution: setup and help

Upload and install the mprsocialrevolution ZIP in Modules > Module Manager. Open Social Media in the back office. The module provides Dashboard, Accounts, Connect Platform, Compose Post, Post Queue, Published Posts, Campaigns, Caption Templates, Feed Settings, Analytics, Conversions, Settings, and Cron & Scheduler, with configuration and maintenance pages under Settings.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.

Start with one connected account and one controlled post. Publishing, storefront feeds, and ad tracking use separate configuration. Connecting a publishing account does not automatically configure a pixel or create feed display settings.

Select the intended shop context before changing configuration or queue items. Publishing settings resolve shop, shop group, then global values. Queued posts have shop and remote-account identity bindings; an item from another shop or an unknown shop requires reconciliation.

Open Connect Platform. Save the platform credentials, then use its authorization flow. Copy the module's generated callback URL into your provider app configuration where required. Complete authorization for the actual account, Page, organization, or board you intend to use.

Credential values start empty. Review Accounts after connecting. Expired, revoked, and reconnect-required accounts block publishing. Reconnect them before retrying queued work. An account whose expiry is unknown has its own status; it does not mean the token is valid.

Publishing requires the master switch to be on, compatible publishing components, the correct account identity, and a shop permitted to publish. Development and staging shops are blocked unless your administrator has explicitly allowed publishing. A successful connection or saved caption does not mean a post has been published.

Open Social Media > Settings > Configuration. The form is titled Social Revolution Settings and saves with Save configuration.

Publishing

App Credentials

Meta App ID/Secret, LinkedIn Client ID/Secret, Pinterest App ID/Secret, TikTok Client Key/Secret, and YouTube Client ID/Secret all default to empty. Enter the application credentials for platforms you use, or save them through Connect Platform. TikTok OAuth scopes defaults to user.info.basic. YouTube fields do not enable a working YouTube publisher.

Queue

Retry Limit defaults to 3 and becomes the queue item's maximum attempt count. It is not three retries in addition to the first attempt. Retry Delay defaults to 300 seconds and provides the retry backoff base. Automatic retries apply only to failures classified as retryable. Configuration, authorization, validation, account mismatch, and uncertain remote outcomes can require manual correction or reconciliation.

Analytics

Analytics Enabled defaults to Yes. Analytics records published and failed post counts per account. Reach, impressions, engagement, clicks, and followers appear as zero because these platform metrics are unavailable; those zeros do not represent measured audience activity.

Feeds

Feed image retention days defaults to 7. Feed images to keep defaults to 120 per platform. They control cached-image retention and pruning. The installation also saves a 3600-second feed cache value (FEED_CACHE_DURATION); this form has no control for it.

Theme styles

The shared theme styling controls use detected theme values. Facebook and Instagram feed prefixes are mprfacebook and mprinstagram. Their registered mappings include primary, primary-hover, text, muted text, backgrounds, border, radius, shadows, and transition. Change these controls when the detected styling needs adjustment.

Open Compose Post and review Publish to. Write Base Caption, then review every selected platform’s caption field. The base caption is copied into the individual platform captions. Confirm the copied text before saving or publishing.

Add Link URL where offered and Title where offered. Use accessible media URLs. Instagram, Pinterest, and TikTok require media in the composer. YouTube publishing is unavailable.

Choose immediate publishing or a future schedule. Use the shop/server's configured time consistently and inspect the saved queue timestamp. Scheduling validation enforces the maximum window and LinkedIn cadence. A scheduled post requires cron to become published.

The saved payload uses names such as:

platforms[]=facebook
platforms[]=linkedin
platform_data[facebook][caption]=Specific Facebook caption
platform_data[facebook][link]=https://example.com/article
platform_data[linkedin][caption]=Specific LinkedIn caption
platform_data[linkedin][link]=https://example.com/article
platform_data[linkedin][title]=Article title
media_urls[]=https://example.com/image.jpg
schedule_at=2026-11-01 09:30:00
id_campaign=12

The actual form also uses a submission token. Do not replay a payload as a substitute for the protected admin workflow.

In Campaigns, set Name, optional Description, Platforms, Status, Start Date, and End Date. Status starts as Draft; other choices are Active, Paused, and Completed. Open a saved campaign to add posts through the composer. Review the resulting queue rows; dates on a campaign alone do not author post content.

In Caption Templates, enter Name, optional Platform or All Platforms, Template, and Default. New text fields start empty; Default is a boolean choice. Use a specific platform template where caption length or wording differs.

The module replaces the placeholders supplied by the content source, including {title}, {excerpt}, {url}, {shop_name}, and an optional {hashtags} value. Automatic product/blog content does not supply hashtags by default. Unresolved lowercase placeholders are removed. For example:

{title}

{excerpt}

Shop now: {url}

{hashtags}

Included platform fallback formats are:

facebook:  {title}\n\n{excerpt}\n\nRead more: {url}
instagram: {title}\n\n{excerpt}\n\n{url}
x:         {title}\n\n{url}
linkedin:  {title}\n\n{excerpt}\n\n{url}
pinterest: {excerpt}
tiktok:    {title} {url}

Open Cron & Scheduler and copy the exact generated URL with its token. Configure your scheduler to call it every minute. A non-rewritten example is:

curl 'https://yourshop.com/index.php?fc=module&module=mprsocialrevolution&controller=cron&token=YOUR_TOKEN'

The token is required. The controller returns 401 for a missing token, 403 for an invalid token, and 503 when cron is disabled. It sends X-Robots-Tag: noindex, nofollow, noarchive. Optional execution parameters include max_tasks and max_seconds; use the generated scheduler instructions for your installation.

Registered tasks include queue processing every 60 seconds, feed refresh every 1800 seconds, token refresh and feed image backfill every 3600 seconds, analytics daily at 06:00, and provider conversion queue processing every 300 seconds. These are due-task intervals; your external invocation must actually run.

Use Post Queue to inspect pending, failed, blocked, and reconciliation states. Use Published Posts for recorded remote outcomes. Check a live destination before retrying an unknown outcome: the remote post may exist even when its receipt could not be saved. Reconnecting a different account does not retarget an old queue row; compose a new post for a changed destination.

Feed rendering is implemented for Facebook and Instagram only. The module can render on displayHome, displayFooterBefore, displayFooter, displayLeftColumn, and displayRightColumn, provided an enabled account and matching feed configuration exist.

Feed Settings shows connected-account status and the Optimize existing feed images action. Feed enablement, placement, layout, and displayed details cannot be configured on this screen and are not set up during installation. Connecting an account and assigning a hook alone does not complete feed setup.

Ask your administrator or support to configure the feed, then check it on the storefront. The following configuration keys are for that integration and are not fields on the settings screen:

FEED_FACEBOOK_ENABLED=1
FEED_FACEBOOK_DISPLAY_HOOK=displayHome
FEED_FACEBOOK_POST_COUNT=8
FEED_FACEBOOK_LAYOUT=grid
FEED_FACEBOOK_COLUMNS=4
FEED_FACEBOOK_MOBILE_COLUMNS=2

FEED_INSTAGRAM_ENABLED=1
FEED_INSTAGRAM_DISPLAY_HOOK=displayFooterBefore
FEED_INSTAGRAM_LAYOUT=slider
FEED_INSTAGRAM_AUTO_SCROLL=1
FEED_INSTAGRAM_SCROLL_SPEED=5000

For each FEED_{PLATFORM}_ prefix, the renderer reads these options:

Feed refresh keeps the last usable cache if a fetch fails. The image cache tool resizes and generates formats supported by GD/Imagick on your server. It needs edit permission and writable cache locations. Feeds are available for Facebook and Instagram only.

Theme selectors include .mprfacebook-section, .mprfacebook-grid, .mprfacebook-follow-btn, .mprinstagram-section, .mprinstagram-grid, and .mprinstagram-slider-btn. Inspect the actual rendered markup before applying CSS. Do not assume a generic unified social-wall selector exists for every output path.

Publishing account credentials and ad-tracking credentials are separate. Open the provider's tracking tab in Settings > Configuration, enable its browser tag, and enter the correct tracking identifier. Keep only events you intend to use enabled. Then configure server delivery separately if required.

Tracking is implemented for Facebook, Pinterest, Microsoft Ads, Google Ads, LinkedIn, TikTok, X, Snapchat, Reddit, Taboola, and Outbrain. Server delivery needs provider credentials and the scheduled conversion tasks. Google Ads click conversion queueing defaults on, while API upload defaults off.

Use the configuration page's tracking ownership controls if multiple installed modules compete for the same provider identifiers. Internal traffic is controlled through the shared shop/module/feature policy section. The individual provider forms no longer include Exclude employees; use the shared internal-traffic policy.

Respect cookie consent defaults to Yes for every provider. The module reads supported MPR consent cookies and its consent state. Without a granted marketing decision, required-consent tracking remains blocked; it is not automatically permitted just because a consent module is absent. Test both refusal and acceptance, including queued server delivery.

Empty means the module supplies no credential or identifier. A default event switch of 1 does not activate tracking while its provider master switch is off. Your theme must also send the corresponding interaction events.

Facebook Tracking

Pinterest Tracking

Microsoft Ads Tracking

Google Ads Tracking

LinkedIn Tracking

TikTok Tracking

X Tracking

Snapchat Tracking

Reddit Tracking

Taboola Tracking

Outbrain Tracking

The Facebook Tracking tab also includes a connection status/check panel and setup guide. Use its exact Pixel ID, access token, and test-event fields to verify the server connection.

The current form and runtime do not provide the old arbitrary click-selector custom-event JSON setup. Do not add the earlier GalleryBrowse, conversion_label, or x_event_id examples as undocumented configuration values. The per-event Google labels and X IDs in the tables are supported controls.

Publishing

Connect one account, keep Publishing Enabled on, and create a specific caption for one selected target. Schedule it shortly ahead, confirm it in Post Queue, invoke your configured cron, and verify the remote post and Published Posts receipt. Repeat an immediate publish only when you intend another real post.

If publishing is blocked, read the reported cause. Check the master switch, account health, destination identity, host policy, employee edit access, and shared package compatibility. An unknown remote result needs reconciliation before retry. A failed scheduled post does not necessarily qualify for an automatic retry.

Feeds

Check that the platform feed is enabled, the exact hook is configured, the connected account is enabled, and cached or API posts exist. Check the storefront in desktop and mobile layouts. A feed appears only where it has an enabled placement, whatever the Feed Settings status shows.

Tracking

Test as a visitor allowed by internal-traffic policy. Check marketing refusal first, then acceptance. Trigger the chosen product, cart, checkout, search, signup, and purchase flows that your shop supports. Check provider browser tools, the module's conversion results, cron outcomes, and provider-side test reports. Confirm one purchase is associated with the expected order and provider IDs.

If the browser tag is absent, check the provider switch, tracking ID, ownership, internal traffic, consent, and loaded assets. If server events do not arrive, check server-delivery switches, provider tokens, conversion rules/labels, queue errors, and cron. Google upload also needs its customer/action identifiers and readable service-account key. Enabling a switch alone does not complete provider setup.

Use Integrity for database and hook failures. Audience metrics are unavailable. Use the platform’s own tools to reply to comments and manage its inbox.

Record account setup, queue state, and history before uninstalling. Uninstall removes theme registration, cron tasks, admin menus, configuration, conversion queue rows owned by the module, and module-owned schema tables such as accounts, campaigns, templates, and analytics. Shared publishing/queue tables are marked shared and are not dropped by schema cleanup. The uninstall action leaves feed and image cache files on disk. Inspect remaining module files separately if removing the package.

Remote social posts and ad-platform records are not deleted by uninstalling the module. If theme registration cleanup fails, uninstall returns a failure before the remaining removal steps. Disable the module when you need to retain installed data while stopping its normal hooks.