LinkedIn Integration: setup and help

Upload and install mprlinkedinintegration in Modules > Module Manager, then click Configure. Use the equivalent module upload screen on older PrestaShop versions. The module provides Configuration, Integrity, License, Support, and Update pages.

Requires PrestaShop 1.6.0.0 or later and PHP 7.1 or later.

In LinkedIn Connection, enter Access Token and Organization ID. The ID must contain 1 to 20 digits and cannot start with zero. Enter Organization Name if you want a specific display name. Save and check the connection result. A configured token and ID are required before the standalone feed can render.

This module reads LinkedIn organization pages, not personal-profile feeds. Its connection help specifies organization social read and write permissions, r_organization_social and w_organization_social. Obtain credentials with access to the intended organization. The module does not provide a pasted-widget-code mode or a complete token-issuance workflow.

Supported placement hooks are displayHome, displayFooterBefore, displayFooter, displayLeftColumn, and displayRightColumn. The theme must render the selected hook. The follow link uses https://www.linkedin.com/company/{ORGANIZATION_ID}.

Layout

Post metadata

The stored THEME value defaults to light and is passed as a markup data attribute. The current form does not expose a separate Theme picker; do not expect a configuration control for every stored key.

Advanced

Slider navigation and automatic scrolling use the bundled JavaScript. Automatic scrolling pauses on hover, keyboard focus, touch interaction, and hidden tabs, and stays off when reduced motion is requested.

The cache file is /modules/mprlinkedinintegration/mprlinkedin_feed_cache.json. The web process needs permission to write in that module directory. Save the feed configuration to clear the cache when you need an immediate refresh. Otherwise, the next uncached or expired-cache request fetches posts.

Publishing is implemented for MPR Blog Revolution posts. It is not a product publisher.

The Blog Posts panel lists recent Blog Revolution entries and offers manual publishing when the token, organization, and publishing policy allow it. Select a test article, review its title and caption template, then use its publish action when you intend to create a real LinkedIn post.

Enable Auto-Publish defaults to No. Enable it only after verifying manual publishing. The lifecycle hooks can publish eligible Blog Revolution posts when saved with published status. Published-history checks prevent the module from deliberately publishing the same source again for the tracked destination. An uncertain remote result needs inspection before retrying.

Caption Template defaults to:

{title}

{excerpt}

Read more: {url}

Supported template values include {title}, {excerpt}, {url}, and {shop_name}. For example:

{title}

{excerpt}

Read the full article: {url}

{shop_name}

The standalone feed and automatic publishing step aside when Social Revolution's LINKEDIN_ACTIVE takeover flag is enabled. Manage that platform in the owning module and verify the actual takeover state, rather than assuming installation alone activates it.

Publishing also checks employee write access and shared outbound-write policy. Development/staging hosts can be blocked. An older social publishing package loaded by another module can block writes; update the participating social modules together.

1. Save valid credentials, choose a layout, and leave Lazy Load Images enabled for the initial test.
2. Open the configured storefront hook and check title, cards, text, and image loading.
3. Click a post and the follow link; they should open LinkedIn destinations.
4. Check desktop and mobile output.
5. If publishing is required, publish one controlled Blog Revolution article and confirm the actual LinkedIn post and stored published state.
6. Enable Auto-Publish only after that test, then verify one newly published article.

Visitors read feed cards in your store. Likes and comments are handled on LinkedIn, not inside the store. Media may be absent when the API returns internal URNs without usable thumbnail URLs.

Theme template paths are:

themes/your-theme/modules/mprlinkedinintegration/views/templates/hook/feed.tpl
themes/your-theme/modules/mprlinkedinintegration/views/templates/hook/post_item.tpl

Use .mprli-section, .mprli-title, .mprli-follow-btn, and .mprli-item for theme CSS. For example:

.mprli-follow-btn {
  background: #0a66c2;
  border-radius: 4px;
}

If no feed appears, check enabled state, Organization ID validation, token, organization permissions, takeover flag, hook, cache, and whether the API returned public posts. The feed and publisher use the same API version from the shared social publishing package, currently LinkedIn-Version: 202601. If LinkedIn rejects an API version, update the module and participating social modules; there is no API-version setting.

If media is blank, check Show media/images and inspect the returned URL. If slider controls do nothing, check that the module JavaScript and stylesheet load through displayHeader and that theme overrides preserve the slider markup. If publishing is unavailable, check Blog Revolution data, employee edit permission, credential validity, outbound policy, and shared package compatibility. Use Integrity for module infrastructure checks.

Record your settings and publishing history before uninstalling. Uninstall removes the module menu, configuration, and feed cache and invokes schema cleanup. The shared publisher tables are marked shared and are not dropped by that schema cleanup. Remote LinkedIn posts are not deleted by uninstalling this module.