Soliloquy Protection - WordPress Plugin

Soliloquy Protection Guide: Protecting Images in WordPress Sliders

Soliloquy Protection is an add-on for Soliloquy that blocks the simplest way to copy images from a slider: right-clicking the image in the standard slider view and in lightbox mode. This guide covers more than just where to check a box. We will also look at how to prepare the slider, how to test old and new slides, what to expect on the live site, and where this type of protection has clear real-world limits.

This article is for site owners, editors, photographers, designers, or developers who already use Soliloquy to display images and want to reduce casual saving from public pages. We will separately cover portfolios, work showcases, galleries with lightbox, the Gutenberg block, shortcodes, caching, and the common situations where protection appears to be enabled but visitors still see the standard browser context menu.

It is important to understand the boundary here: Soliloquy Protection does not turn a published image into an inaccessible file. If an image has been loaded in the browser, a technically skilled person can still find it in network requests, cache, source code, or simply take a screenshot. That is why this guide treats protection as a practical deterrent layer against simple copying, not as an absolute digital rights system.

To make the result useful, we will move from the task to verification: first identify where the add-on makes sense, then prepare Soliloquy and the slider, enable protection for the right image sets, test both the standard display and lightbox, troubleshoot problems, and compare it with similar solutions.

What Soliloquy Image Protection Actually Solves

Soliloquy Protection has a narrow and straightforward purpose: disabling the standard right-click action on images inside Soliloquy sliders. The official add-on page specifically notes that protection applies to both the regular slider display and the lightbox view. The documentation also clarifies one more important detail: the add-on protects only images displayed through Soliloquy, not every image on a WordPress site.

This approach works well when a site has a small number of visually valuable areas: a photographer's portfolio, a designer's project gallery, a course slider with illustrations, a handmade product showcase, a case study presentation, or a set of promotional images that should not be easy to copy. Instead of disabling right-click across the entire page, you limit the effect to a specific slider.

That matters for usability. General right-click blocking plugins sometimes interfere with opening links in a new tab, copying text, using the browser context menu, or accessibility workflows. With Soliloquy Protection, the behavior is more context-aware: if the issue is specifically with slider images, the protection is applied where those images are displayed.

In a real project, the goal is usually stated like this: "We want to display portfolio images at a useful size, but not encourage one-click saving from the page." For that purpose, the add-on is a better fit than sitewide restrictions. At the same time, the source images still need to be prepared sensibly: do not upload unprocessed originals, do not use overly large files without a reason, add a watermark where that is part of your policy, and do not publish materials that should never be shown to an external audience in the first place.

What Exactly Changes for the Visitor

Once protection is enabled, visitors should no longer get the usual image-saving menu when they right-click a slide image. If the slider is opened in lightbox, the same check should work inside the enlarged view. This reduces the number of quick "save for later" actions that often happen without bad intent but still take the image out of the site's controlled context.

At the same time, users should still be able to browse slides, view images, interact with navigation, and read captions. A solid protection setup should not break the slider's main purpose. If enabling the add-on makes it hard to swipe on mobile, breaks the lightbox, or leaves the slider stuck on a loading indicator, that is a conflict to troubleshoot, not a normal tradeoff of protection.

What This Protection Is Not

Right-click is only one way to get a file. It is the most visible and most common one among regular visitors, but it is not the only one. That means you should not promise a client that Soliloquy Protection completely prevents copying. A more accurate description is this: the add-on makes quick image saving from the slider and lightbox harder for an ordinary user.

Practical rule: if an image cannot be shown without a real risk of leakage, it should not be published in an open slider even with protection enabled. For commercial previews, it is better to use reduced-size copies, watermarks, licensing terms, and separate delivery of originals to the client.

Who Soliloquy Protection Is For, and When Another Approach Makes More Sense

The add-on is useful for people who already build visual sections with Soliloquy and want to add a deterrent layer without moving to another gallery plugin. The strongest use case is when Soliloquy already handles image display and Protection adds a targeted restriction on top of it. There is no need to rebuild the page template, switch gallery systems, or install a sitewide content-blocking plugin.

Soliloquy Protection is a good fit for photographers, illustrators, interior designers, studios, course creators, agencies, and showcase site owners where the slider is not displaying random decorative images but actual work output. Those sites usually need balance: the image quality has to be visible, but visitors should not get the easiest possible way to download the file through the context menu.

The plugin is also convenient for editors who need to manage protection at the level of individual sliders. The official product page notes that protection is enabled for new sliders after activation, while existing sliders need their settings updated. The same page also points out that protection can be disabled for a specific slider using the Enable Image Protection option on the Misc tab. That gives you useful flexibility: a portfolio can stay protected, while an informational slider with icons or banners can remain unrestricted.

When the Add-on May Not Be the Right Fit

If you need to protect more than just Soliloquy images - such as the full WordPress media library, PDF files, client pages, downloadable archives, or access to originals by user role - Soliloquy Protection is too narrow. That kind of task requires different mechanisms: private pages, membership access, password-protected galleries, file access restrictions, client agreements, watermarks, or a dedicated client gallery.

If the site does not use Soliloquy, the add-on is not a standalone protection system either. It was built as an extension for Soliloquy, not as a universal image protection plugin. In that case, it makes more sense to compare several gallery and slider tools: you may need a gallery plugin with built-in protection, or a more general deterrent plugin for selected images.

You should also avoid choosing the add-on just because it includes the word "protection" if your actual goal is legal copyright enforcement. A sound publishing strategy usually has multiple layers: reduced file versions, captions and alt text, licensing terms, watermarks, clear usage terms, and careful control over which originals ever make it onto the site.

Scenarios Where Protection Makes the Most Sense

• Portfolio with original photography. Visitors need to review a series of works, but one-click image saving via right-click is undesirable.
• Showcasing design work, mockups, or illustrations. The slider displays project excerpts that should not be easy to extract as standalone files.
• Handmade product showcase. Images matter for sales, but the owner does not want to offer the most convenient possible copying path.
• Educational content with paid visual examples. The page can show previews, while the source materials are delivered separately and not through a public slider.
• Client presentations without a private portal. Protection does not replace restricted access, but it can reduce casual copying if the page still has to remain public.

What to Check Before Installing and Enabling Protection

The preparation step matters. Soliloquy Protection works together with the main Soliloquy plugin, a specific slider, lightbox, the theme, cache, and the page editor. If you skip the basic checks, you may enable the add-on, see the checkbox in the admin area, and still get a weak result on the public site.

First, make sure the main Soliloquy plugin is installed, active, and can output a normal slider without errors. The documentation for creating your first slider shows the basic flow: open Soliloquy, add a new slider, upload images through the media library, edit metadata if needed, configure the settings, and embed the slider on a page. Protection sits on top of that chain, so it is much easier to troubleshoot when the base slider output is already working properly.

Next, verify that the add-on is available under your Soliloquy license. The official Protection Addon documentation lists it as available for the Master, Agency, Developer, or Multi plans. This guide does not cover purchasing or paying for a license, but in practical terms one point matters: if the add-on does not appear on the add-ons page, the cause may be your access level rather than a WordPress error.

Another required check is your WordPress version and environment. The Protection Addon documentation lists WordPress 4.8+ as a requirement. In practice, it is worth looking more broadly: updates to Soliloquy Lite on WordPress.org show that the core plugin actively changes support rules, permissions, blocks, lazy loading, image formats, and compatibility. So before configuring protection, it is safer to update a staging copy of the site, verify the base slider, and only then move changes to the live page.

Checking Existing Sliders

The main trap involves older sliders. The official add-on page states that protection is applied automatically to new sliders after activation, but existing sliders have to be updated before protection starts working. So after installing the add-on, do not stop with a new test slider. Open each important existing slider and check the Misc tab.

For a project with multiple pages, it helps to keep a short list: page name, slider name, where it is embedded, whether lightbox is enabled, whether protection is enabled, and when the result was last checked. This is not bureaucracy. If a client says a month later that right-click is working again on one page, you will have a clear map instead of a chaotic search across the site.

Preparing the Images Themselves

Even with protection enabled, you should not upload full-resolution originals to the slider if a web-sized version is enough for visitors. Prepare separate export files: sensible dimensions, compression without visible quality loss, a clear file name, alt text, a caption, and a visible watermark if needed. Soliloquy lets you edit image metadata in the slider, including Title, Caption, Alt Text, and URL. Those fields matter not just for SEO and accessibility, but also for validating the lightbox scenario.

If you use lightbox, verify that the image actually opens the way you expect. Soliloquy troubleshooting documentation specifically covers the case where lightbox does not work because the image has an empty URL. In that situation, you need to open the item editor, fill in the URL using Media File, enable Load in Lightbox?, and save the metadata. This matters for Protection because part of the check has to happen in lightbox, not just on the visible slide.

Installing the Add-on and Running the First Admin Check

Installing Soliloquy Protection follows the standard Soliloquy add-on flow. In the official activation guide, the path starts in the WordPress admin area: open Soliloquy - Addons, find the required add-on, click Install, and then Activate. Once installed, the add-on is updated like a regular WordPress plugin through the Plugins screen when an update is available.

This guide does not cover license retrieval, key entry, or purchasing a paid version. We are assuming the main Soliloquy plugin has already been installed legitimately and that the required add-on is available in the interface. If there is no install button, do not try to solve that by downloading random archives. It is safer to check your access level, Soliloquy account, and the official support channel.

After activation, do not jump straight to the public page. First open a test slider or create a new one. If the add-on is working as expected, the slider settings should include the Enable Image Protection? option on the Misc tab. Protection should be enabled automatically for new sliders, but it is still better to confirm it directly. For older sliders, open the tab manually and save the changes.

Quick Check After Activation

The minimum validation flow has four steps. Create or open a slider, make sure it contains images, enable Enable Image Protection?, and click Publish or Update. Then embed the slider on a test page and open it in a browser where you are not logged into WordPress. That matters because testing from an admin session can hide cache issues, permission conditions, or visitor-facing behavior.

On the public page, try right-clicking the image inside the slider. If lightbox is enabled, open the image in the enlarged view and repeat the check there. If protection fails in one of the modes, do not rush to change the theme or disable everything at once. First confirm that you actually modified the same slider that is embedded on the page, and that the page is not showing a different copy through an old shortcode.

How to Roll Back Safely

The rollback is simple: open the relevant slider, go to the Misc tab, uncheck Enable Image Protection?, save the slider, and clear the page cache. If you need to temporarily disable the add-on entirely, you can do that under Soliloquy - Addons using Deactivate for that specific add-on. That rollback should not remove the slider itself or its images, but it is still wise to have a backup before making changes on a production site.

Detailed Setup: New Sliders, Old Slides, and Lightbox Mode

Soliloquy Protection has only a few settings, but that is exactly why setup discipline matters. One checkbox does not mean you can skip checking page structure, lightbox, and the embedding method. On a real site, the slider may be inserted through a Gutenberg block, a shortcode, a classic editor button, a widget, or template code. Protection has to be tested in the same context where visitors actually see the image.

New Sliders After Installing the Add-on

For new sliders, Protection should enable itself automatically after the add-on is activated. That is convenient if you create many similar visual sections, such as a separate slider for each photo session or each project. But automatic enablement does not replace final testing, because the public result depends not only on the slider setting but also on the theme, JavaScript, cache, and lightbox.

In practice, the workflow looks like this: create the slider, give it a clear name, upload the prepared images, add alt text, check the Misc tab, save it, and insert it on a test page. Then open the public page in a private window. If the slider works, advances properly, does not break the mobile experience, and does not show the standard save-image menu on right-click, the base setup is successful.

Existing Sliders and Manual Updating

Older sliders need special attention. If a product page or portfolio was created before the add-on was installed, protection may not apply automatically. The official page explicitly says that existing sliders must be updated for protection to take effect. So for each important slider, do a manual pass:

1. Open Soliloquy in the WordPress admin area and find the required slider by name.
2. Go to the Misc tab and check Enable Image Protection?.
3. Save the slider with Update, even if the checkbox is already enabled.
4. Clear the page cache if you use a caching plugin, CDN, or server-side cache.
5. Open the page as a normal visitor and test right-click in both the regular slider and the lightbox.

This takes more time than a global enablement step, but it reduces the risk that part of the portfolio remains unprotected. That is especially noticeable on sites where some sliders were inserted with an older shortcode workflow while newer sections were added through Gutenberg.

Lightbox: A Separate Area to Test

Protection Addon is documented as working for slider display and lightbox views. That means lightbox needs its own test. If right-click is blocked in the main slider but the standard context menu becomes available again once the image opens in lightbox, the setup is incomplete or conflicting with another script. The add-on changelog includes a fix related to protecting lightbox images, so this scenario should not be skipped.

Check two things: whether the Lightbox Addon is enabled for the slider, and whether the image URLs are populated in metadata. The lightbox documentation describes a separate Lightbox tab and the Enable Lightbox? option, while the troubleshooting docs explain that an empty image URL can break lightbox. If lightbox does not open, restore its normal behavior first and only then test the protection layer.

Which Settings to Enable Only When Needed

The Protection Addon itself has one key setting, but there are surrounding decisions that should not be enabled without a reason. Lightbox is useful for portfolios and detailed viewing, but not every banner slider needs it. Links to the media file make sense when lightbox should open the image, but if you are not using lightbox and do not want to provide direct file access, verify the URL behavior for each item. Autoplay, complex effects, and extra add-ons like Pinterest can all influence user behavior, so it is better to test them together carefully instead of enabling everything at once.

A good strategy is this: start with the base slider plus Protection, then add lightbox, then add extra effects. After each step, test the public result. If something breaks, you will know at which stage the conflict appeared.

How to Embed the Protected Slider on a Page Without Losing the Result

Once the slider is configured, it has to be displayed where it is actually needed. Soliloquy supports several insertion methods, and each can be useful in its own context. The documentation for creating your first slider shows that insertion options become available in the sidebar with the slider code after publishing. The Gutenberg documentation describes the Soliloquy Block and the alternative Shortcode Block workflow.

If the site uses the block editor, the clearest option is to add the Soliloquy block and choose the desired slider from the list. If you work in the classic editor, you can use the insert button or a shortcode. If the slider needs to appear in a theme template, a developer can use the PHP embed code from the slider sidebar, though that becomes a matter of careful theme or child theme work.

Gutenberg and the Soliloquy Block

In the block editor, the flow is simple: create a page or post, add the Soliloquy block, choose the published slider, and update the page. If the block is not available, the official documentation allows using the Shortcode block with the Soliloquy shortcode pasted into it. That is a useful fallback for editors, but for long-term maintenance it is still worth documenting which slider is used where.

After publishing, check more than just right-click. Also test behavior on a mobile screen. Some general image protection plugins can interfere with scrolling or touch events. Soliloquy Protection works in its own slider context, but mobile validation is still required: swipe gestures, arrows, navigation dots, and lightbox should all remain comfortable to use.

Shortcode and Reuse Across Multiple Pages

Shortcodes are convenient when the same slider needs to appear on multiple pages. But there is a risk here: an administrator may edit one slider while the page is actually using a different ID. The documentation for finding the ID explains that the number and slug are shown in the Soliloquy Slider Code sidebar. When troubleshooting, always compare the ID from the page with the ID in the admin panel.

If the same protected slider is reused in multiple places, test at least one page of each type: a standard post, a landing page, a page built in a page builder, and a widget area. Different templates may load CSS and JavaScript differently. The protection checkbox is the same, but the output environment is not always identical.

Cache, CDN, and JavaScript Optimization

If enabling Soliloquy Protection leaves the public page behaving as if nothing changed, clear the cache first. That may mean browser cache, a caching plugin, server cache, a CDN, or JavaScript optimization. Soliloquy troubleshooting docs repeatedly recommend clearing browser cache when script-related issues appear, and the main plugin changelog includes fixes related to lazy loading, WP Rocket, and shortcode rendering.

Do not disable optimization sitewide forever just to fix one slider. Start with a targeted check: temporarily exclude the page or Soliloquy scripts from combination or deferred loading, clear the cache, and test right-click again. If the issue disappears, configure the exclusion carefully and record it in the site's technical notes.

Quick takeaway: working protection is a chain of "the correct slider, the option enabled, metadata saved, proper embedding, cache cleared, and visitor-mode testing." If any link in that chain is skipped, the add-on can appear to be broken.

Practical Scenario: A Photographer Portfolio with a Protected Slider and Lightbox

Let us walk through a realistic example. A photographer's site has a page with a series of images. The goal is to display 8 to 12 images in a clean slider, allow visitors to browse them and open lightbox, but remove the standard right-click save behavior. The key objective is not to make the site "unbreakable," but to reduce casual copying while keeping the viewing experience intact.

Goal

Create a portfolio slider where images are comfortable to view on desktop and mobile, lightbox opens a larger version, and right-clicking images in both modes does not trigger the usual save flow. At the same time, alt text, captions, and reasonable loading performance need to stay intact.

Preparation

Before setup, prepare web-ready image copies. Do not upload originals intended for print or client delivery. For a portfolio, export files are enough if they show the work properly without exposing the full source material. Add clear file names, and in Soliloquy fill in alt text and captions where they help the user.

Make sure the main Soliloquy plugin is active, the Protection Addon is installed and activated, and the Lightbox Addon is available and enabled for the required slider. If lightbox is not needed, you can build the scenario without it, but then validation will be limited to the standard slider display.

Setup Steps

1. Open Soliloquy - Add New and create a slider with a clear name, for example "Portfolio - Wedding Highlights".
2. Add images through the WordPress media library and arrange them in the desired order.
3. Open the metadata editor for each important slide and fill in the alt text, caption, and URL if lightbox should open the media file.
4. On the Lightbox tab, enable Enable Lightbox? if you want enlarged viewing.
5. On the Misc tab, verify Enable Image Protection?.
6. Click Publish or Update and copy the shortcode, or use the Soliloquy block on the portfolio page.
7. Clear the page cache and open the page in a private browser window.

Verifying the Result

On the public page, test four states. First, a regular slide without lightbox: right-click should not trigger the usual save-image workflow. Second, move to the next slide: navigation should continue to work normally. Third, lightbox: open the image, repeat the right-click test, and confirm that protection works there as well. Fourth, mobile view: swipe behavior, lightbox closing, and page scrolling should all remain predictable.

If protection does not work in lightbox, go back to the image metadata and Lightbox Addon settings. If it stops working only after the page is served from cache, clear the cache or exclude the page from aggressive JavaScript optimization. If protection works in a private window but not in the normal administrator browser session, the issue may be local cache, a browser extension, or testing while logged in.

A Detail People Often Miss

If clicking a slide takes the visitor directly to the media file or attachment page, the image can be opened outside Soliloquy. In that mode, the add-on no longer controls file behavior because the image is no longer being displayed inside the slider. That is why for protected slides you should test not just right-click, but also the normal click action. If the goal is lightbox viewing, configure the URL and Load in Lightbox? so the user stays within the managed Soliloquy workflow.

Result Quality Check: What to Review After Enabling Protection

A proper quality check is not limited to asking whether the right-click menu appears. You also need to confirm that protection did not damage the user experience, hide the image, break lightbox, conflict with the theme, or slow down an important page. Visual content often lives on the home page or in a portfolio, which means any issue is immediately visible.

Editor Checklist

• The slider is visible on the page and does not remain stuck on a loading indicator.
• Images can be browsed with the mouse, arrows, navigation dots, or swipe gestures if those elements are enabled in settings.
• Right-clicking the image in the slider display does not open the standard save-image menu.
• If lightbox is enabled, right-click has also been tested inside the enlarged view.
• Captions and alt text were not lost after metadata editing.
• The page was tested in a private window, not only from an admin session.
• Page cache and JavaScript optimization were cleared after the setting change.
• On mobile, the slider does not block page scrolling or create false gesture behavior.

How to Tell Whether Protection Is Configured Well Enough

A good-enough result looks like this: a regular visitor can browse the slides, but does not get a simple "Save image" command through the Soliloquy context menu. At the same time, the site does not try to scare users with loud warnings, break navigation, or block the rest of the browser. The less the protection interferes with the rest of the page, the lower the risk of frustrating visitors.

For a client or support team, it is useful to keep a short internal protocol: where protection is enabled, which sliders were tested, whether lightbox is involved, and which cache has to be cleared after changes. That is especially helpful on sites maintained by multiple editors. One person may create a new slider, another may place it on the page, and a third may test the public result. Without shared notes, it is easy to miss the Misc tab.

When to Add a Watermark or Another Layer

If the images are commercially important, blocking right-click is not enough. Add a subtle watermark, publish reduced-size copies, avoid serving originals through the media file, use licensing terms, and deliver original files to clients through a separate restricted channel. Soliloquy Protection is effective at blocking a fast user gesture, but it is not a substitute for an actual visual content protection strategy.

Common Soliloquy Protection Problems and How to Diagnose Them

Most add-on problems look similar: the checkbox is enabled, but something on the site does not match expectations. The key is to break the symptom into parts: where exactly protection is being tested, which slider is being displayed, whether lightbox is working, whether cache is involved, and whether the theme or another JavaScript component is interfering.

Right-click Still Works on the Page

Symptom: a visitor opens the page with the slider, right-clicks the image, and sees the standard browser menu. A possible cause is that you are testing the wrong slider, protection was not saved for an older slider, the page is being served from cache, or the image is not being displayed through Soliloquy at all.

Start by checking the slider ID or name. Open the page editor, find the shortcode or selected Soliloquy block, then open that exact slider in the admin panel. On the Misc tab, verify Enable Image Protection? and click Update. After that, clear the cache and open the page in a private window.

If the image is displayed through a regular Image block, Gallery block, or another slider, Soliloquy Protection will not affect it. In that case, either move the images into Soliloquy or use a different protection solution for those specific files.

Protection Works in the Slider but Not in Lightbox

Symptom: right-click is blocked on the visible slide, but once the lightbox opens the context menu becomes available again. A possible cause is that lightbox is not configured as part of Soliloquy, the images have empty URLs, a different lightbox plugin is being used, or a conflicting script is loaded on the page.

Check the Lightbox tab in the slider settings and make sure Enable Lightbox? is enabled. Then open the image metadata through the edit icon and verify the URL. If the field is empty, use the Media File button, enable Load in Lightbox?, and save the metadata. Then save the slider again and clear the cache.

If the site uses a separate lightbox plugin, test the page without it on a staging copy. Do not disable working plugins on the live site without a rollback plan. If the conflict is confirmed, choose one lightbox workflow instead of trying to run two at the same time.

New Sliders Are Protected but Old Sliders Are Not

Symptom: a newly created slider behaves correctly, but an older portfolio on an already published page does not. This is an expected risk area: after the add-on is activated, new sliders get protection automatically, while existing ones have to be updated.

Make a list of older sliders, open each one, verify Enable Image Protection? on the Misc tab, save it with Update, and clear the cache. If there are many sliders, start with the pages where images matter most: portfolio pages, the home page, case studies, and work showcases.

The Slider Hangs or Stops Loading After Enabling Protection

Symptom: instead of the slider, you see a loading indicator, slides do not advance, or the page shows JavaScript errors. Soliloquy troubleshooting documentation connects those symptoms with script loading errors, theme or plugin conflicts, and browser cache.

Start with the safest actions: clear the cache, open the page in another browser, and temporarily test without JavaScript optimization on a staging copy. If the issue disappears when script combination or deferred loading is disabled, configure an exclusion for Soliloquy. If the problem remains, check the theme: the Soliloquy docs specifically mention the importance of wp_footer(); in the footer.php template.

Rolling back Protection makes sense when the slider is critical to the page and the conflict cannot be isolated quickly. Uncheck the option, save, clear the cache, and record the symptom for further debugging.

The Image Can Still Be Opened Directly and Saved

Symptom: right-click is blocked inside the slider, but a normal click opens the image as a standalone file or attachment page where it can still be saved. The reason is that the user has already left the managed Soliloquy context.

Check the URL in the slide metadata and the click behavior. If the goal is to show a larger version, use Soliloquy lightbox. If direct file opening is unnecessary, change the image URL or link behavior. After making the change, always retest the public page, because users often reach the file through a regular click rather than a right-click action.

Mobile Viewing Became Uncomfortable

Symptom: on a phone, the slider is hard to swipe, the page does not scroll properly, or the lightbox is difficult to close. This is not the most typical Soliloquy Protection symptom, but any protection tied to user actions has to be tested on touch devices.

First determine whether the problem appeared specifically after enabling Protection or was already present before. Test the same slider without lightbox, then with lightbox, then with JavaScript optimization disabled. If a general right-click or copy-blocking plugin is also active, it may interfere with gestures more than Soliloquy's targeted protection does. Do not keep two protection mechanisms on the same area unless there is a real reason.

Safe Improvements Without Editing Plugin Core

With Soliloquy Protection, there is no reason to invent PHP hooks or JavaScript workarounds without fresh confirmation from the documentation. The official sources provide clear configuration points: the add-on, the Misc tab, lightbox, image metadata, shortcode, block, and baseline troubleshooting. So the safest improvements here are organizational or CSS-level, not code-level intervention in the add-on itself.

A CSS Hint for a Protected Portfolio

If you want to politely tell visitors that the images are provided for viewing, you can add a normal text block or caption near the slider without interfering with the plugin itself. If you need a lightweight visual note in the theme, use CSS only for the page container, not for Soliloquy files. For example, you can style an explanatory paragraph below the slider like this:

.portfolio-image-note {
  margin-top: 12px;
  font-size: 14px;
  line-height: 1.5;
  color: #4b5563;
}

Add that CSS in a child theme, the theme's additional CSS section, or a trusted CSS snippet plugin. Then verify the result on the portfolio page and on mobile. The rollback is simple: remove the CSS and the explanatory paragraph itself. This snippet does not modify the Protection Addon, does not break JavaScript, and does not try to replace technical protection with a text warning.

What You Should Avoid

Do not edit Soliloquy files, the add-on, WordPress core, or the active theme directly. Do not inject global JavaScript that blocks all keys, menus, and text selection across the site. Those kinds of solutions often damage accessibility and maintainability, while a determined user can still retrieve the image another way. If you need more control, choose a purpose-built tool for the task: a protected client gallery, selective image protection, watermarks, or restricted access.

When Soliloquy Protection Is a Good Choice

Soliloquy Protection is worth using if you already have Soliloquy sliders with valuable images and need a simple targeted layer against right-click in both the slider display and lightbox. Its strength is that it is tied to a specific tool and configured in a straightforward way through the Misc tab. For editors, that is faster and safer than blocking the context menu across the entire site.

Before deploying it, verify the base Soliloquy setup, the availability of the add-on, your list of older sliders, lightbox, and caching. After enabling it, test the page as a normal visitor, check lightbox separately, and review the mobile experience. If everything works, you can move forward with publishing and maintain a record of protected sliders in the site's technical notes.

If you are ready to configure and test the result on your site, the most logical next step is to download the latest version of Soliloquy Protection, install the add-on alongside Soliloquy, and start with one test slider. That will let you see the real behavior in your own theme, with your cache and your images, without risking every portfolio page at once.

The main conclusion is simple: the add-on is useful not as a magical defense against every copying method, but as a clean control layer inside an existing Soliloquy workflow. Treated that way, it helps make an image-heavy page feel more professional, more understandable, and easier to maintain.