X (Twitter) Feed Integration: setup and help

On older PrestaShop versions, use the equivalent module installation page. Open this module through Configure whenever you need to return to its settings.

The Display Hook menu also offers Custom Widget (use {widget} in templates), but this version does not implement that rendering path. Select a standard hook, including when placing the feed in a theme template.

Column controls apply to the grid and carousel. At widths from 768px to 991px, the carousel and grids with at least two posts use two columns; a one-post grid stays one column. Below 768px, they use Mobile Columns. Grids containing only one or two posts use one or two desktop columns respectively, and one column on mobile. The gap and border radius apply to every layout, including the carousel.

The server resolves an empty X User ID through https://api.x.com/2/users/by/username/{username}. It fetches the timeline through https://api.x.com/2/users/{user_id}/tweets, including creation dates, public metrics, media attachments, and author data. Your configured account and API access must allow those requests. The module does not fetch a hashtag wall or combine multiple accounts.

The fetch logic caps the requested display count at 20. It requests up to three times that count before keeping the required number of results. Keep a positive count. Text is shortened to Max Text Length during retrieval; use 0 for full text. The metadata switches control card display, while the exclusion switches change the API request.

The selected standard hook renders a grid, carousel, or list. The header follow button opens https://x.com/{username}. Each card opens https://x.com/{author_handle}/status/{post_id} in a new tab. Video media remain previews, without an embedded player.

If you change accounts, update X Username and manually clear X User ID before saving. A non-empty ID is reused even after the username changes. Then use Sync Now.

The feed cache uses this local JSON file:

modules/mprxintegration/mprx_feed_cache.json

Feed settings and this file are shared by shops using the same module installation. Storefront requests reuse it while it is valid and fetch posts from X when it is missing or expired. Saving the main form clears it; this version has no scheduled feed-refresh worker.

Sync Now requires a Bearer Token and a resolved X User ID, then clears the cache and fetches fresh posts immediately. Clear Cache only deletes the file; the next storefront request fetches new data. If the API request then fails or returns no posts, no cached posts remain. Check the timeline, credentials and API access, then retry.

Only non-empty API results are cached. An expired file is not used as a fallback when retrieval fails, so the feed can disappear until a later request succeeds. API counts and relative dates reflect the cached response.

Configure the four OAuth 1.0a credential fields in X (Twitter) Connection if you need blog publishing. A read-only Bearer Token alone does not configure this publishing path. Then use the separate Auto-Publish to X form:

The Blog Posts panel requires MPR Blog Revolution and provides a manual publishing action when the publisher is configured. It uses the blog title, excerpt, URL, and featured image when available. The publisher supports text and image/GIF media. Publication runs through shared queue and history records that prevent duplicate handling. If the panel reports a queue or reconciliation error, check the existing result before retrying.

Feed display and publishing have separate switches, but saving the main feed form resets the publishing switch and caption because those fields are absent from that form. After each main-form save, save Enable Auto-Publish and its caption again in the separate publishing form.

Publishing is suppressed when Social Revolution’s X takeover flag is set. It can also be blocked on a development/staging or unresolved shop host by the outbound-write policy. The UI reports the reason. Another installed social module loading an older shared publisher package can block the send; update the installed social modules together if you see that error.

The examples below describe values to enter in the back-office forms. They are not shell commands. Replace account names and credentials with real values. The theme hook must match Display Hook.

Display a homepage grid with six posts, three columns on desktop, one column on mobile, and original posts only:

MPRX_DISPLAY_HOOK=displayHome
MPRX_LAYOUT=grid
MPRX_POST_COUNT=6
MPRX_COLUMNS=3
MPRX_MOBILE_COLUMNS=1
MPRX_EXCLUDE_REPLIES=1
MPRX_EXCLUDE_RETWEETS=1

Use a compact right-column list without media or engagement counters:

MPRX_DISPLAY_HOOK=displayRightColumn
MPRX_LAYOUT=list
MPRX_POST_COUNT=3
MPRX_SHOW_MEDIA=0
MPRX_SHOW_LIKES=0
MPRX_SHOW_RETWEETS=0
MPRX_SHOW_REPLIES=0
MPRX_TEXT_LENGTH=140

Use the slider with automatic scrolling every eight seconds:

MPRX_LAYOUT=slider
MPRX_COLUMNS=3
MPRX_AUTO_SCROLL=1
MPRX_SCROLL_SPEED=8000

Customize the Blog Revolution caption sent to X:

{title}

{excerpt}

Read more: {url}

Available caption placeholders are:

{title}
{excerpt}
{url}
{shop_name}

Render the module through a standard PrestaShop hook in a theme template, with the module configured for the same hook:

{hook h='displayHome' mod='mprxintegration'}

Theme developers can override the storefront templates here:

themes/your_theme/modules/mprxintegration/views/templates/hook/feed.tpl
themes/your_theme/modules/mprxintegration/views/templates/hook/post_item.tpl

Useful CSS selectors for theme-level styling:

.mprx-section { margin-top: 32px; }
.mprx-title { font-size: 1.25rem; }
.mprx-item { border-radius: 8px; }
[data-theme="dark"] .mprx-item { background: #16181c; }
.mprx-follow-btn { text-transform: none; }

The feed cache uses this local JSON file:

modules/mprxintegration/mprx_feed_cache.json

For a carousel, check the configured columns and gap at desktop, tablet, and mobile widths. Keep CSS and template changes in your theme.

• If the section is absent, check Enable Module, the source fields, Show on Mobile, and the selected hook. The module returns no section when no items are available.
• Check that your theme calls displayHeader to load the stylesheet and JavaScript, and renders your selected display hook.
• If images remain blank, inspect browser network errors. Try disabling lazy loading and check the image URLs.
• If the layout is wrong, test the grid first, then verify the carousel at desktop and mobile widths.
• If MPR Social Revolution has its X_ACTIVE setting enabled, this standalone feed is suppressed. This check reads the saved flag; it does not require Social Revolution to be currently enabled as a module.

Open the module’s Integrity page for configuration and hook checks. License, Support, and Update are maintenance pages. Test the actual destinations after changing account identifiers or feed sources.

Set Enable Module to No and save to hide the feed while retaining its source and display configuration. Saving the main form resets the publishing switch and caption; review and save the separate publishing form afterwards if publishing should continue. Uninstall through the module manager to remove this module’s configuration, local cache, and admin menu entries. Shared mpr_social_publish and mpr_social_queue tables are marked shared and are retained on uninstall. Uninstall does not delete posts already sent to the platform.