WDS X Feed Slider Pro Documentation

WDS Twitter Widget Slider Pro 3.0 has been completely rebuilt for Joomla 5.4 and Joomla 6. Inside Joomla, you’ll find it listed as WDS X Feed Slider Pro.

Although the name has changed to reflect the move from Twitter to X, it is still the same extension internally: mod_wdstwitterwidget_pro. This allows existing module instances to remain in place when upgrading from version 2.x.

You can also open this guide from within the module by going to:

Content → Site Modules → WDS X Feed Slider Pro → Documentation

• License
• Support
• Purchase WDS X Feed Slider Pro

Requirements

Before installing the module, make sure your website meets the following requirements:

• Joomla 5.4 or later, including Joomla 6
• PHP 8.1 or later, or whichever newer PHP version your Joomla installation requires
• HTTPS enabled on the public website for official X embeds
• A public X username or public X List URL for Easy X Feed
• Public X post URLs containing /status/ for Social Proof
• A Bearer Token from your own X Developer account for Advanced X API v2

WDS does not include or provide a shared X API key. If you use Advanced X API mode, X may charge the developer account connected to the module.

Installing the Module

1. In Joomla, go to System → Install → Extensions.
2. Upload and install the extension ZIP file.
3. Go to Content → Site Modules.
4. Click New and select WDS X Feed Slider Pro.
5. Enter a title, choose a module position and set the status to Published.
6. Under Menu Assignment, choose the pages where you want the module to appear.
7. Open the Feed tab, select one of the available feed sources and complete its settings.
8. Click Save.

Even when using the slide-out panel, the module must still be assigned to a valid position used by your Joomla template.

Upgrading from Version 2.x

Back up your website before installing the new version. Once you have a backup, install version 3.x directly over WDS Twitter Widget Pro 2.x. Do not uninstall the old module first.

The upgrade is designed to retain your existing module records, including their positions, publishing status and menu assignments.

Legacy Twitter API v1.1 credentials are no longer supported or used. If an older module was configured to display search results, you will need to add a current Bearer Token from your X Developer account.

Choosing a Feed Source

The module offers three ways to display content from X. Only one feed source can be active in each module instance.

Choose your preferred option from the Feed source setting on the Feed tab.

1. Easy X Feed

Easy X Feed is the simplest option and does not require an X API key. It can display one or more public X profiles or a public X List.

The posts are not downloaded or stored in Joomla. Instead, the module places an official X embed on the page, and X’s widget script draws the timeline in the visitor’s browser.

Displaying X Profiles

1. Set Feed source to Easy X Feed (no API required).
2. Choose X profile account(s).
3. Enter one or more public usernames.
4. Add one username per line or separate multiple usernames with commas.
5. Set the number of posts, feed height and preferred layout.
6. Click Save.

Enter usernames only, such as:

joomla

Do not include the @ symbol or paste the full profile URL.

Displaying an X List

1. Set Feed source to Easy X Feed (no API required).
2. Choose Public X List.
3. Paste the complete public List URL.
4. Configure the feed height and other display options.
5. Click Save.

A valid List URL looks like this:

The module uses twitter.com addresses behind the scenes when creating official embeds because X’s current widget script does not reliably convert equivalent x.com links into timelines.

If the Full Timeline Does Not Appear

If X cannot load the timeline, the module displays a simple profile link instead of leaving an empty space. For example, visitors may see @youraccount with a button that opens the profile on X.

This usually means the module is configured correctly, but X did not draw the official timeline.

Common causes include:

• The website is using HTTP instead of HTTPS
• An ad blocker or browser privacy feature is blocking X
• X’s widget service is temporarily unavailable or rate-limited
• The website’s Content Security Policy is blocking platform.twitter.com, platform.x.com or syndication.twitter.com
• Privacy consent is enabled and the visitor has not clicked Load X Content

2. Social Proof

Social Proof lets you hand-pick individual public X posts and display them as a curated collection. It does not require an X API key.

This is useful for displaying customer feedback, testimonials, announcements, endorsements, event reactions or any other posts you want to feature.

Each selected post is displayed using the official X widget.

Adding Selected Posts

1. Set Feed source to Social Proof.
2. Open the Social Proof tab.
3. Find Selected X posts and click Add.
4. Paste the complete URL of a public X post.
5. Add an optional label, such as Customer Review.
6. Add an optional editor’s note if you want to provide context.
7. Repeat the process to add more posts.
8. Arrange the posts in your preferred order.
9. Choose a layout and click Save.

A valid post URL looks like this:

A profile URL alone will not work. Each entry must be the URL of an individual post and contain /status/.

You can display selected posts as a:

• List
• Grid
• Masonry layout
• Carousel
• Vertical slider
• Single rotating post

Add at least two posts if you want to use a carousel, slider or rotating-post layout effectively.

If you feature someone else’s post as an endorsement or advertisement, you are responsible for obtaining any permission that may be required. Installing this extension does not grant permission to use third-party content.

3. Advanced X API v2

Advanced X API mode provides additional options for combining accounts, displaying recent search results and filtering posts.

This mode requires a Bearer Token from your own X Developer account.

Connecting Your X Developer Account

1. Create or open a project at developer.x.com.
2. Generate and copy the project’s Bearer Token.
3. In Joomla, set Feed source to Advanced X API v2.
4. Open the X API tab.
5. Paste the Bearer Token into the appropriate field.
6. Choose either combined account timelines or recent search.
7. Enter your usernames or search query.
8. Configure your filters, layout and API Cost Guard settings.
9. Click Save.

For account feeds, enter public usernames without the @ symbol.

For search feeds, you can use queries such as:

#Joomla

or:

from:username

Official Embeds and WDS Cards

We recommend using official X embeds whenever possible.

The module can also create custom WDS cards for simple, eligible posts. However, replies, reposts, quoted posts, edited posts, sensitive content and posts missing required information will continue to use the official X embed.

This helps preserve the context and attribution provided by X.

API Cost Guard

The optional API Cost Guard helps you control how often the module contacts X.

You can set daily limits for requests and estimated resources. The module also uses caching to reduce unnecessary API activity. Failed requests and timeouts do not count against the module’s local Cost Guard allowance.

For a public website, leave Show API/cache status on frontend turned off unless you are actively testing or troubleshooting the module.

The Cost Guard only controls requests made by this Joomla module. The limits and billing controls inside your X Developer account remain the final safeguard against API charges.

Protecting Your Bearer Token

The Bearer Token is stored in the Joomla database as part of the module’s settings.

It can be accessed by:

• Joomla Super Users
• Administrators who have permission to edit the module
• Anyone with direct access to the Joomla database
• Anyone with access to unencrypted database backups

The token is never printed in the public page HTML or sent to frontend JavaScript. However, you should still treat it like a password and only give trusted users access to the module settings and website backups.

Layout and Slider Settings

Carousel, vertical slider and single rotating-post layouts use the settings found on the Slider tab.

Depending on the selected layout, you can configure:

• Automatic rotation
• Time between slides
• Pause on hover
• Number of visible posts
• Previous and next controls

Slider settings only affect layouts that rotate or move between posts.

Slide-Out Panel

The slide-out panel places a clickable tab along the left or right edge of the browser window. Visitors can open the panel to view the feed without it taking up permanent space in the page layout.

You can configure:

• Left or right placement
• Vertical position
• Tab label
• Click or hover activation
• Opening animation speed
• Optional automatic opening

The module must still be assigned to a valid template position, even when the slide-out panel is enabled.

If you are not using the slide-out option and the feed appears too narrow, try assigning the module to a wider or full-width template position.

Appearance Settings

The Appearance tab lets you adjust the module to suit your Joomla template.

Available options include:

• Automatic, light or dark theme
• Modern or classic wrapper
• Module width
• Desktop, tablet and mobile columns
• Background color
• Text and link colors
• Border color
• Card spacing
• Corner radius
• Card shadow

The automatic theme follows the visitor’s browser or operating-system preference.

Privacy Settings

New module instances use Consent mode by default.

With Consent mode enabled, X’s external script, images and other remote content do not load until the visitor clicks Load X Content. This gives you more control over when the visitor’s browser connects to X.

You can also choose how long the visitor’s consent is remembered.

Select Immediate loading only if you are satisfied that you have an appropriate lawful basis for loading external X content as soon as the page opens.

Existing module instances retain their previously saved privacy setting during an upgrade.

What the Module Does Not Do

To avoid confusion, WDS X Feed Slider Pro has a few intentional limitations:

• It does not scrape content from X
• Easy X Feed does not display hashtag or keyword searches
• Hashtag and keyword feeds require Advanced X API mode
• It cannot create or invent posts when X’s widgets or API are unavailable
• It cannot bypass ad blockers, browser privacy tools or website security policies
• It does not provide a shared X API account or Bearer Token

WDS X Feed Slider Pro is not affiliated with or endorsed by X Corp. X, Twitter and related marks belong to their respective owners.