Modula Fullscreen - WordPress Plugin

Modula Fullscreen Guide: How to Set Up Fullscreen Viewing for WordPress Galleries

Modula Fullscreen is not meant to create a separate gallery from scratch. It supports an important user action inside an existing Modula gallery: a visitor opens an image in the lightbox and can then expand it to fullscreen view. In this guide, we will walk through where the add-on is enabled, how it ties into the lightbox settings, what to check before installation, how to prepare a gallery for a smooth fullscreen experience, and how to confirm that everything is working properly.

This guide is intended for a site owner, editor, or developer who already understands the basic purpose of an image gallery but wants to avoid common issues: the fullscreen button does not appear, images look soft, the lightbox conflicts with optimization tools, the gallery is not placed on the right page, or the experience differs for administrators and regular visitors. It does not cover purchasing or activating a paid license. The focus here is on using the product on a live site where the plugin and the required add-on are already available.

The core setup principle is simple: first make sure the main Modula gallery is created and published correctly, then enable Modula Fullscreen in the add-ons section, and only after that test the lightbox behavior on the live page. If you skip that order and start by troubleshooting the fullscreen button itself, you can miss a more basic cause - the gallery is not published, minification is interfering, or the lightbox is configured with an unsuitable display behavior.

What fullscreen mode actually adds to a gallery

A standard image grid helps users choose: a visitor sees thumbnails, compares shots, and opens the one they want. But for a portfolio, photo report, work catalog, property page, designer case study, or curated product selection, there is often an important second step - viewing the image without the distractions of the page around it. That is where Modula Fullscreen becomes useful: the add-on places an Open in Fullscreen button inside the lightbox and switches the image into the browser's fullscreen mode.

Fullscreen mode does not replace a well-structured grid or fix weak images. It strengthens the experience when a visitor is already interested in a specific shot. In practice, it works best as part of a chain: gallery structure - lightbox - image quality - on-page behavior. If one part is weak, the fullscreen button alone will not make the gallery comfortable to use.

When this feature is especially useful

For a photographer, it helps present a series without the theme's visual clutter. For an interior designer, it gives visitors space to study details without distraction. For a store with visually complex products, it can highlight texture, included components, or color options when the gallery appears on an informational page. For an educational site, it can open diagrams, illustrations, or infographics at a larger size. In all of these cases, the user is not just "looking at a picture" but checking details that shape trust in the material.

For small decorative galleries on a landing page, the add-on may be unnecessary. If the images are there only to set a mood, a fullscreen button adds another interface element without offering real practical value. It should also be enabled carefully on pages where the visitor needs to move quickly to a form, pricing, booking, or another action. In those cases, you do not want to pull someone into a long viewing flow when the page is meant to drive conversion.

How Fullscreen differs from a standard lightbox

A lightbox opens the image above the page, usually with a dimmed background, navigation arrows, and utility buttons. Fullscreen adds a separate browser state where the viewing area takes over the entire screen. This is not just a larger image inside the same window. The action feels more pronounced, and exiting the mode depends on browser behavior and the Esc key. That is why your testing should cover more than whether the button appears. It should also include entering fullscreen, exiting it, moving between images, and returning to the page.

Practical check: after enabling the add-on, open the page as a regular visitor, click an image in the gallery, and then click Open in Fullscreen. A working setup means the image expands, the arrows and close controls remain clear, and exiting returns the user to the same gallery.

Who should use Modula Fullscreen, and who should not start with it

This add-on works best for sites where visual content has standalone value. If you have a portfolio page, photo session, architectural project, art collection, event gallery, or work archive, fullscreen viewing helps visitors study the content without opening separate image pages. It is especially useful when the gallery is already built in Modula and the site owner wants a more comfortable viewing mode without replacing the whole gallery solution.

The plugin may not be a good fit if the real issue is not the viewing mode but the way the content is organized in the first place. For example, the site may be using images that are too small, a grid built from random shots, pages overloaded with third-party scripts, or a gallery that does not actually help users choose the right material. In that case, it makes more sense to clean up the images, album structure, and publishing method first, and only then add fullscreen mode.

Typical sites where the difference is noticeable

• A photographer's portfolio, where visitors evaluate a series of shots and the quality of post-processing.
• A design, architecture, or renovation studio site, where room details, materials, and layouts matter.
• An event page where the gallery replaces a long written recap and needs to be easy to browse image by image.
• A blog or media project with original illustrations that should be viewed in full.
• A site with educational content where diagrams and charts need to open at a larger size.

When a basic lightbox is the better choice

If the images are small, created only for thumbnail use, or heavily compressed, fullscreen mode will make those weaknesses more obvious. Visitors will notice blur, jagged edges, poor cropping, and image noise. If the gallery sits inside a short sales-focused block where the main action is submitting an inquiry, a fullscreen button may become a distraction. On those pages, it is often better to keep a clean lightbox without extra controls and focus on loading speed.

Another important case is a site with aggressive JavaScript optimization. Modula's documentation specifically covers conflicts with optimization, lazy loading, and minification. If the site already uses WP Rocket, Autoptimize, or similar tools, you need to know where to disable conflicting optimization for the gallery scripts before going further. Otherwise, you can end up in a situation where the gallery appears, but lightbox controls behave inconsistently.

What to check before installing and enabling the add-on

Before installing Modula Fullscreen, do not just verify that the add-on file exists. Fullscreen mode depends on the main Modula gallery already working, the lightbox being enabled, the images being large enough, and the page not breaking the plugin's scripts. That preparation usually takes less time than troubleshooting after the gallery is already published.

The base plugin and a working gallery

The foundation is Modula Image Gallery. On WordPress.org, the plugin is presented as a solution for responsive galleries with drag-and-drop building, grid variations, a lightbox, hover effects, and page insertion through a block, shortcode, or supported editors. Fullscreen works as an add-on inside that ecosystem, so you need a created and published gallery first.

If the gallery does not exist yet, do not start with Fullscreen. First add a few real images, save the gallery, place it on a page, and confirm that the regular lightbox opens the images. Only after that should you enable the add-on. This sequence helps separate installation issues from gallery issues.

Image quality and size

Modula's documentation pays close attention to image size and responsive images. For fullscreen viewing, that matters even more: a small image may look fine in the grid, but once expanded fullscreen it can appear noticeably soft. Make sure the originals are not uploaded only as small thumbnails. At the same time, do not upload extremely large files without control, because they will slow down the page, especially if the gallery contains many images.

A practical approach is to size your originals for the largest realistic viewing state, apply reasonable compression, and avoid reducing them to tiny assets. After publishing, open the same image in the normal lightbox and in fullscreen mode. If the fullscreen version looks worse than expected, the issue is usually tied to the source file, size settings, or optimization, not to the Fullscreen button itself.

Theme, cache, and JavaScript optimization

Optimization plugins can combine, defer, or minify scripts. Galleries are sensitive to that, because the lightbox controls need to load in the correct order. Modula's official knowledge base includes separate articles about conflicts with Autoptimize, WP Rocket, SiteGround Optimizer, and other performance settings. Before rolling this out on a live site, it is smart to test the gallery temporarily without aggressive optimization and then turn those features back on one by one.

If the button disappears after enabling Fullscreen or the lightbox stops opening, do not reinstall the plugin right away. First disable JavaScript combining and deferred loading for the gallery page or for Modula scripts, clear the site and browser cache, and then test again in a private window. That is usually much easier than hunting for an error inside the gallery itself.

User roles and the page editor

To configure the add-on, you need administrator access or a user role that can install and activate plugins. To publish the gallery, editor-level access may be enough if the base setup is already in place. If several people maintain the site, split responsibility clearly: the administrator enables the add-on and checks compatibility, while the editor places the gallery on the page and reviews the result as a visitor.

Installing Modula Fullscreen and running the first check

Modula's official documentation describes installing add-ons through the Modula section in the WordPress admin area. The general flow is straightforward: the base plugin must already be installed and active, then the required add-on is enabled from the add-ons list. Once Fullscreen is activated, the gallery settings gain the option to control the fullscreen button through the related lightbox settings.

The cleanest installation order

1. Confirm that the main Modula plugin is active and that the Modula section is available in the admin panel.
2. Create or open a test gallery with several images so you have something to check inside the lightbox.
3. Go to the Modula add-ons section and enable Modula Fullscreen.
4. Open the target gallery settings, go to the lightbox options, and confirm that the fullscreen button control is available.
5. Save the gallery and refresh the page where it is published.
6. Clear cache if the site uses a caching plugin or server-side optimization.

Do not change the grid, hover effects, image sizes, lightbox settings, and optimization at the same time. On the first pass, the goal is narrow: verify that the add-on has added the required capability. The fewer parallel changes you make, the easier it is to identify where an issue appears.

Where to look for the button after enabling it

The Modula Fullscreen documentation explains that after activation, a new option appears under Lightbox & Links. That option controls whether the Open in Fullscreen button is shown in the lightbox interface. This matters because an enabled add-on does not automatically mean the button is visible in every gallery. Check the specific gallery, not just the global add-ons list.

If the site uses multiple galleries, start with one test gallery. Enable the button, save the changes, test the page, and then repeat the process for other galleries only if needed. That approach reduces the risk of accidentally changing the behavior of every visual block on the site.

The first test on the public page

Open the page with the gallery as a normal visitor. Click an image, wait for the lightbox to open, find the fullscreen button, and activate it. Confirm that the image takes over the screen, the controls do not cover important details, navigation between images remains clear, and exiting returns the user to the same page.

Critical expected state: the fullscreen button should appear inside the lightbox of the specific published gallery, not only in the settings inside the admin panel.

Configuring the lightbox: Fullscreen button, links, and viewing behavior

The most important settings are not buried in some vague "general options" area. They sit next to the lightbox behavior itself. Fullscreen depends on how the image opens, which controls the visitor sees, and whether extra actions create conflicts. It is best to work through this setup as a viewing flow rather than as a checklist of toggles.

What to enable first

Open the target gallery in the Modula admin area and go to Lightbox & Links. Turn on the Open in Fullscreen button if it is disabled. Save the gallery and test one published page. At this stage, avoid changing every other lightbox effect at the same time. First make sure the button appears and actually works.

If the button is there but the user experience feels cluttered, review the other lightbox interface elements. Sometimes extra actions, captions, navigation, social elements, or links are enabled alongside the fullscreen control. That may be fine for a photography portfolio, but unnecessary for a tightly curated work catalog. The right setup depends on what the visitor should do after viewing: keep browsing, open a project description, close the lightbox, or submit an inquiry.

How lightbox links and fullscreen interact

The Lightbox & Links section in Modula does more than decide whether an image opens. It defines how visitors interact with the image after clicking it. If the gallery is configured with external links or alternative click behavior, make sure it does not conflict with the fullscreen flow. The visitor should immediately understand what a click will do: open the lightbox, follow a link, or trigger a separate action.

For most galleries where Fullscreen makes sense, the behavior is simple: clicking an image opens the lightbox, the fullscreen button is available inside it, and extra links are used sparingly. If the gallery has been turned into a navigation menu for projects, the fullscreen button may not be the primary action. In that case, make sure viewing mode and linked navigation are not competing with each other.

Captions that help instead of adding clutter

Captions can be useful when they explain the image: a project name, location, shooting technique, material, or project phase. But a long caption inside the lightbox can interfere with fullscreen viewing, especially on smaller screens. If captions matter, keep them short and specific. If the gallery already speaks for itself, leaving only a title or removing extra text elements may be the better choice.

After saving, walk through the gallery like a visitor: open the first image, switch to fullscreen, move to the next image, then close the view. Pay attention to whether the interface still feels predictable. A good configuration does not make people think about how to close the window or get back to the page.

What to roll back if something feels off

If the lightbox starts to feel overloaded after enabling Fullscreen, do not disable the entire add-on immediately. First restore the previous settings for extra buttons, links, and captions. Then leave only the fullscreen button and the basic navigation. If the problem disappears, the issue was not Fullscreen itself but the combination of controls.

How to choose the galleries that actually need fullscreen mode

One of the most common setup mistakes is enabling the button everywhere just because the add-on is available. In practice, different galleries on the same site serve different purposes. One gallery showcases a flagship project and should help visitors study details, another simply illustrates a short news post, a third displays partner logos, and a fourth acts as category navigation. If you use the same lightbox and fullscreen behavior for all of them, the interface becomes less precise.

A better approach is to map your galleries first. List the pages where Modula is used and note the role of each gallery next to it. If the role is "prove quality," "show detail," "let users inspect a diagram," or "walk visitors through a photo story," Fullscreen is almost certainly appropriate. If the role is "quickly decorate a block," "show three small logos," or "link to another section," the button may be unnecessary.

Primary portfolio galleries

For portfolio work, Fullscreen is valuable when the images carry evidential weight. Visitors are judging the quality of photography, finishes, design, composition, lighting, retouching, or the outcome of the service itself. In that kind of gallery, pay close attention to image size, shot order, and captions. The first row of the grid should catch attention, and fullscreen mode should make it easy to study the image without the site header, sidebars, or nearby content blocks.

A useful portfolio structure is this: the first image presents the overall outcome, the next few reveal details, and the final ones provide context or alternate angles. If the user opens fullscreen mode, it should feel like they are stepping through a coherent visual story, not a random image folder. Short captions are useful here: project name, area, material, technique, or phase.

Galleries inside articles and tutorials

In articles, Fullscreen is worth enabling for images that people genuinely need to study. That might include diagrams, drawings, comparison shots, interface examples, process photos, or before-and-after outcomes. If an image only sets the mood, fullscreen mode may not be worth it. The reader clicks the button, sees essentially the same decorative shot, and loses the article context.

For educational content, readability matters especially. Open the most detailed image in fullscreen and ask yourself whether the material becomes easier to understand. If it does, Fullscreen is functioning as a teaching tool. If the image is still hard to read, it is better to replace the source image, prepare a dedicated diagram, or move the critical detail into the text.

Galleries that move the user forward

Sometimes a gallery acts as a visual link hub: each item leads to a project, product, category, service page, or separate article. In that setup, Fullscreen can compete with navigation. If clicking an image is supposed to open a link and the lightbox is only a secondary action, review Lightbox & Links very carefully. The visitor should not have to guess why one click opens a viewer and another sends them to a different page.

For those galleries, a mixed strategy often works best: keep link-based navigation on the overview page, and use Modula Fullscreen inside the individual project page for detail viewing. That creates a clear path: the visitor picks a project first, then studies its images. It works better than forcing one gallery block to behave as navigation, portfolio, and fullscreen viewer all at once.

Secondary and decorative blocks

For small decorative blocks, the Fullscreen button rarely adds real value. If a gallery contains only two to four small images and sits next to a contact form, a long service card, or a benefits section, an extra lightbox can pull attention away from the main action. In those areas, it is usually more useful to keep a neat grid, optimize loading, and keep click behavior simple.

Working rule: enable fullscreen mode where users need to inspect details, not simply where you want them to notice that images exist on the page.

The grid, image sizes, and the fullscreen viewing experience

One of Modula's strengths is its gallery grid. But Fullscreen does not reveal its value in the grid itself. It matters after the click. That means you need to understand the difference between the thumbnail image and the file the user is actually inspecting. If the thumbnail is cropped or reduced, that may be a perfectly valid design choice. If the fullscreen file is also too small or too heavily compressed, the visitor will see a weak outcome.

Set up the grid for selection, then the viewing experience for inspection

In the grid, the image's job is to quickly show what is in the gallery. That is where proportions, spacing, order, and visual rhythm matter. In fullscreen mode, the job changes: now the image needs to support close inspection. Do not try to solve both tasks with a single setting. Configure the grid so it is easy to browse, and configure source image quality and lightbox behavior so the opened image holds up under close viewing.

If your gallery includes mixed formats - landscape, portrait, and square images - test several edge cases. A portrait image may look good in the grid but take up too much height in fullscreen mode. A wide panoramic shot may need a larger source file. Do not draw conclusions from one good-looking image alone.

Responsive images and real devices

Modula's documentation covers responsive images and image sizing. For Fullscreen, that means your testing should not stop at the admin display. Open the page on a wide screen and on a mobile device, or simulate both using browser developer tools. On mobile, fullscreen mode can feel very different because the browser, gestures, screen orientation, and address bar all shape the experience.

Do not enable fullscreen just because the feature exists. If most of your audience views the gallery on mobile devices, make sure the button does not interfere with closing the lightbox or compete with gestures. If people usually view the portfolio on larger screens, Fullscreen can become a meaningful part of the presentation.

A safe CSS tweak for an overly narrow container

Sometimes the gallery itself works correctly, but the site theme places the content inside a container that is too narrow. In that situation, fullscreen mode helps with detail viewing, but the grid still looks cramped before the image is opened. If the real problem is the width of the page content area, you can add a small CSS adjustment through a child theme or the WordPress Additional CSS section. Do not edit plugin files or change the theme core.

/* Example: widen the page container for the gallery without touching Modula files */
.page .entry-content .modula-gallery {
  max-width: 1180px;
  margin-left: auto;
  margin-right: auto;
}

After adding the CSS, clear cache and test the page. If the grid becomes wider and the surrounding content remains intact, you can keep the change. If the theme uses different container classes, adapt the selector to the specific page. Rolling it back is simple: remove the CSS and clear the cache again.

Managing multiple galleries and keeping editorial work consistent

On a small site, there may be only one gallery, and Fullscreen setup takes a few minutes. On a real project, there are usually more: portfolio galleries, work archives, dedicated service pages, articles, event pages, and internal collections. If editors add images regularly, the setup has to be clear to more than just the developer. Otherwise, within a few weeks the site ends up with galleries that behave differently: some show the button, some do not, some use images that are too small, and some have a lightbox that conflicts with the page container.

To prevent that, create a simple editorial rule. It does not need to be a massive document. It is enough to define which gallery types should use Fullscreen, what source image sizes to use, how to write captions, where to verify the outcome, and who is responsible for the final publishing check. This kind of internal agreement is especially useful for studio sites, agencies, educational projects, and work catalogs.

A shared review checklist for editors

An editor does not need to know every technical detail of the lightbox, but they should understand the validation flow. After adding a gallery, they open the published page, click two or three images, enter fullscreen mode, move to the next image, and close the view. If something does not work, the editor records the symptom: the button is missing, the button does not respond, the image is blurry, the page jumps, or a popup blocks the interface. That kind of note helps the administrator find the cause more quickly.

A good review checklist can live in a simple project note:

• The gallery is inserted on a published page, not just saved in the admin panel.
• At least three images of different formats open in the lightbox.
• The Open in Fullscreen button is visible and works.
• After exiting, the user returns to the same place on the page.
• The result in a private window matches what was seen during the admin check.

Grouping galleries by purpose

If the site is large, do not configure every gallery the same way. Divide them into groups. Primary portfolio galleries get Fullscreen, short illustrative blocks stay without it, link-based galleries are reviewed separately, and educational diagrams get fullscreen only when the image is large enough. This approach reduces the number of questionable interface elements on the page and makes editorial work more predictable.

Inside Modula, it helps to think in terms of finished gallery blocks rather than individual images. Define the purpose of each gallery: show an outcome, explain a process, compare options, prove quality, decorate a page, or move the user to the next step. Fullscreen is not for the generic category of "gallery." It is for the specific cases where large-format viewing genuinely improves the experience.

Tracking changes without a heavy system

You do not need a dedicated log for every single adjustment. But if the site changes galleries often, it is useful to record major changes: Fullscreen was enabled on the portfolio page, image sizes were changed, script delay was disabled for gallery pages, or a gallery was moved from a builder tab into a regular block. When an issue appears a month later, that note helps you understand what changed before the problem started.

The simplest format is a line in a work document or task: date of change, page, gallery, what was changed, and what was tested. You do not need dates inside the article itself, but they help inside the workflow. For publication, the current stable outcome matters more than the edit history: the gallery opens, Fullscreen works, and the visitor can return to the page.

How Fullscreen fits into the user flow

The fullscreen button may seem like a small detail, but in real user behavior it sits in the middle of a chain. First the visitor sees the grid, then chooses an image, then opens the lightbox, and only after that decides whether the image needs to be viewed larger. If they enter fullscreen mode, the site should still feel controlled and predictable: closing the view, moving through images, and returning to the page should all remain obvious.

Input: a published gallery

The input for the add-on is not a single image but a published Modula gallery with click behavior already configured. If the gallery is inserted via a block, shortcode, or supported editor, the outcome should be visible on the public page. That is where the testable user flow begins.

Product behavior: the lightbox and the decision to show the button

After a click, Modula opens the lightbox. If the Fullscreen add-on is active and the corresponding setting is enabled for that gallery, the Open in Fullscreen button appears in the lightbox interface. The key is not to confuse two separate states: the add-on may be installed, but the button still needs to be allowed in the settings for the specific gallery view.

Output: fullscreen viewing and proof that it works

The testable outcome is not just the presence of an icon. It is a functioning fullscreen entry, correct navigation between images, and a clear exit path. You can verify that manually: open the page, enter the lightbox, click the button, switch between two or three images, exit with Esc or the close button, and make sure the page did not reload and the user returned to the right place.

Quick takeaway: if fullscreen works only for the administrator but not in a private window, the issue is almost always related to cache, access to static resources, script optimization, or the page not being properly published.

Practical example: a portfolio gallery with result validation

Let us walk through a setup that closely matches a real-world use case: a studio website has a "Projects" page where each gallery presents one completed interior. The visitor should be able to scan the grid quickly, open the image they want, expand it fullscreen, and then return to the page to submit an inquiry or move to the next project. In this case, the role of Fullscreen is clear: not to add more effects, but to make detail viewing easier.

Goal

You want a gallery where the user sees a clean grid of work samples, opens an image in the lightbox, and switches to fullscreen mode when needed. After closing the view, they should return to the same section of the page and be able to move to the next project or the contact form.

Preparation

Prepare eight to twelve images from a single project. It is better not to mix wide overviews, detail shots, drawings, and random photos without any order in the same gallery. Arrange the images so that the top of the gallery gives a clear impression of the project: an overall view, a key area, and an important detail. Check the source image sizes and do not upload only small versions if users are expected to inspect details.

Create the gallery in Modula, add the images, configure the grid, and save it. Insert the gallery on the page using the available publishing method - block, shortcode, or an editor that supports Modula. Publish or update the page. Before enabling Fullscreen, make sure the regular lightbox already opens correctly.

Setup steps

1. Open the project gallery in the Modula admin panel.
2. Go to the Lightbox & Links settings.
3. Enable the Open in Fullscreen button for that gallery.
4. Save the gallery and refresh the project page.
5. Clear the site cache if caching or script optimization is in use.
6. Open the page in a private window and test the lightbox as a regular visitor.

Validation

Open the first image, turn on fullscreen mode, move to the next image, and then exit back out. After exiting, you should still see the same page and the same gallery. If the user lands at the top of the page or the interface freezes, check for optimization conflicts, JavaScript errors in the console, and theme settings.

It is also useful to ask someone who did not set up the site to walk through the same path. If they cannot tell how to enable fullscreen mode or how to close the view, the issue is no longer technical. It is an interface issue: too many buttons, weak captions, an overloaded lightbox, or a gallery that does not make its purpose obvious enough.

A consideration for pages with multiple galleries

If one page contains several galleries, test them separately. Make sure Fullscreen is enabled only where it is genuinely needed. A portfolio page may include one large project gallery and a small gallery of partner logos. Fullscreen viewing is useful for the first one and usually unnecessary for the second. Making that distinction keeps the interface calmer and avoids overloading the visitor.

How to verify the setup after configuration

After enabling Fullscreen, do not stop at "the button is there." You need to verify the outcome on several levels: button visibility, correct entry into fullscreen mode, image quality, navigation, exit behavior, cache behavior, and the absence of conflicts across different pages. This matters especially on sites where the gallery contributes directly to trust in the work or the product.

Testing as administrator and guest

First test the page in your current admin browser. Then open the same link in a private window or a different browser. If everything works for the administrator but not for a guest, the cause may be cache, optimization, different file versions, resource access permissions, or a CDN that has not been purged. Always test the user flow while logged out, because that is what real visitors will see.

Testing multiple images

Do not judge the setup based on the first image alone. Test a landscape image, a portrait image, and the most detailed image in the gallery. Fullscreen mode may present one format well and another poorly. If portrait images feel too tall, rethink the order of shots and the source image sizes. If fine details are still unreadable, you may need different source images or a different way of presenting the material.

Testing after caching

After enabling or changing the settings, clear the plugin cache, server cache, and CDN cache if one is being used. Then test the page in a private window. If the problem disappears after turning off minification, bring optimization back gradually. Modula's documentation covers these conflicts with common optimization tools in separate articles, so this is not a step to skip.

Usability and accessibility checks

Users should understand how to exit fullscreen mode. Test the Esc key, the close button, and navigation between images. If your audience is less technical, do not overload the lightbox with extra actions. For a work gallery, arrows, close, and the fullscreen button are often enough. The fewer competing elements there are, the lower the chance that someone gets lost.

Compatibility with the theme, editor, and optimization stack

Modula supports several ways to insert galleries into posts and pages, including shortcodes and editors. For Fullscreen, that means the issue may not be inside the add-on itself. Sometimes the gallery is configured correctly, but the page editor, theme, or optimization settings alter the container, script order, z-index, click handling, or image sizing. That kind of conflict is not always visible in the admin panel.

Block editor and shortcode

If the gallery is inserted through a block and behaves inconsistently, test it temporarily on a page where it is inserted through a shortcode. If Fullscreen works through the shortcode but not through a specific editor, the issue may be the editor wrapper or a conflict with its scripts. That does not mean you have to abandon the editor permanently. It simply helps isolate the cause.

Page builders and containers

Inside a page builder, the gallery may sit in a tab, accordion, slider, or another dynamically hidden block. Lightboxes and fullscreen modes can be sensitive to that kind of container because width and height may be calculated before the block becomes visible. If Fullscreen works on a normal page but behaves oddly inside a builder tab, move the gallery into a standard container or check whether the builder has a setting to reinitialize hidden content correctly.

Cache, minification, and deferred loading

Modula's official conflict articles are especially useful for this kind of troubleshooting. If the button stops responding after Fullscreen is enabled, if the lightbox opens without controls, or if the gallery looks different than expected, temporarily disable JavaScript combining, deferred loading, delayed script execution, and minification for the page with the gallery. Then re-enable the settings one at a time.

A good practice is not to disable the entire site cache forever. Instead, find the exact exception you need: a specific script, page, optimization type, or delay mode. After each change, clear the cache and test the page while logged out.

Theme overlap and blocked controls

Sometimes the button exists but is hard to see or gets covered by theme elements. The cause may be z-index, a sticky header, a popup bar, a chat widget, or custom styles. Test the page with nonessential popups disabled. If the conflict disappears, create an exception for that widget or change the popup behavior on gallery pages.

Safe improvements without editing plugin files

Fullscreen is best configured through the Modula interface and site settings. But sometimes small improvements around the gallery make the viewing experience much cleaner: widening the container, removing page clutter, tightening captions, and checking cache behavior. The main rule is simple: do not edit the plugin's own files, do not alter WordPress core, and do not add heavy JavaScript just for effect.

A dedicated test page for galleries

Create a draft or noindex test page where you can insert a single gallery without complex theme blocks. This is a fast way to understand where the issue lives. If Fullscreen works on the test page but not on the production page, look for the conflict in the page environment: the builder, popups, cache, containers, or additional scripts.

Short captions instead of long descriptions

Short captions usually work better for fullscreen viewing. If the visitor needs to read a long explanation, place it below the gallery or next to the project, not over the image. Inside the lightbox, keep only what helps people orient themselves: project name, step number, material, location, or a brief note. This reduces visual clutter and makes the Fullscreen button more useful.

A lightweight conflict check with Health Check

Modula's documentation mentions troubleshooting with Health Check. This approach is useful when you do not want to disrupt the live site for visitors. The idea is to temporarily test the site for the administrator with a minimal set of active components and see whether the conflict disappears. Use that mode carefully and record which plugins were disabled during the test.

If the conflict is confirmed, do not leave the site in that test state. Restore the plugins, then disable only the settings that truly interfere with the gallery. For Fullscreen, the cause is most often script optimization, hidden builder containers, or theme elements that cover the lightbox.

A final testing plan before using Fullscreen on a live page

Before leaving Fullscreen enabled on an important page, run a short control test. This is not about ticking a box. It is about seeing the page the way a visitor sees it. That matters most when the gallery appears on a service page, portfolio page, case study, or any content that affects trust in the site. Fullscreen should help, not create another failure point.

The best time to test is after every change is already in place: the images are uploaded, the gallery is saved, the page is published, the cache is cleared, and optimization is running in its normal live configuration. If you test with only half the settings enabled, you can get a false result. For example, everything may work without cache, but the button may stop responding once JavaScript delay is turned back on. Your final check should reflect the real environment.

Step 1: a clean page test

Open the page in a private window. Do not rely only on the admin browser, because it may be seeing different files, bypassing cache, or showing the admin bar. Wait for the page to load fully and make sure the gallery grid appears without layout jumps. If the images load in gradually, confirm that this does not break the above-the-fold area or shift nearby content.

Open the first image, enable Fullscreen, and exit. Then repeat the same action with an image of a different format. If the gallery contains both portrait and landscape images, test both types. Sometimes the interface looks clean on a landscape image but interferes with a portrait one.

Step 2: navigation and return-path testing

Move through several neighboring images inside the lightbox. Then turn on fullscreen mode and switch images again. The user should not lose the viewing sequence. After that, exit Fullscreen and close the lightbox. A working outcome means returning to the same page without reloading, freezing, or losing context.

If the page scrolls to an unexpected position after exit or the lightbox closes in a confusing way, inspect the theme, sticky header, and third-party popups. Sometimes the issue is not Modula at all, but another block that captures focus or adds its own modal behavior.

Step 3: testing after cache clear and reload

Clear the cache, reload the page, and repeat the test. Then open the page in another browser or on another device. If the behavior differs, look for differences in cache state, browser extensions, script blockers, and the mobile environment. For a public site, what matters is not perfect behavior on the administrator's computer but stable behavior for ordinary visitors.

Step 4: deciding whether the page should keep Fullscreen enabled

After the test, make a page-level decision. If Fullscreen helps users inspect images, does not break the journey, and does not interfere with the primary actions, keep it enabled. If the button works technically but distracts from the form, overloads the interface, or exposes weak source images, it is better to disable it for that gallery and go back to improving the content. That does not mean the add-on is bad. It means the feature needs to match the page's job.

Common Modula Fullscreen issues and how to diagnose them

Most Fullscreen problems look like a single-button issue, but the root cause often sits one layer over: the add-on is not enabled for the right gallery, the lightbox is configured differently, the page is serving stale cache, scripts are being optimized too aggressively, or the source images are not suitable for large-format viewing. The best way to troubleshoot is to move from the simplest checks to the more complex ones.

The fullscreen button does not appear

Symptom: the gallery opens in the lightbox, but the Open in Fullscreen button is missing. A likely cause is that the add-on is not activated, the setting is not enabled for that specific gallery, or you are looking at a cached version of the page. Check the Modula add-ons list first, then open the target gallery settings and review the Lightbox & Links section.

Fix: enable the required setting, save the gallery, clear cache, and test the page in a private window. If the site has multiple galleries, make sure you are editing the same one that is inserted on the page. If the button appears on a test page but not on the live one, inspect the page editor or builder.

The lightbox opens, but the button does not respond

Symptom: the button is visible, but clicking it does not switch the image into fullscreen mode. The likely cause is a JavaScript conflict, delayed script execution, or browser policy. First disable JavaScript optimization for the gallery page, clear cache, and test again. If the site uses a CDN or server-side cache, clear those too.

If the issue disappears after optimization is disabled, restore the settings one at a time. Do not turn off the entire cache permanently. The goal is to find the exact rule that interferes with the lightbox. If the conflict is tied to a specific page builder or hidden container, move the gallery to a normal test page and compare the behavior.

The fullscreen image looks blurry

Symptom: the image looks fine in the grid, but appears blurry or heavily compressed in fullscreen mode. The cause is usually the source image size or image-generation settings, not the button itself. Check the source file in the media library, the size settings, and any image optimization in place.

Fix: replace undersized images with more suitable source files, regenerate thumbnails if needed, and make sure a separate service is not compressing the images too aggressively. Do not try to sharpen them with CSS filters. That only masks the issue and does not produce a genuinely high-quality fullscreen view.

Fullscreen works for the administrator but not for visitors

Symptom: everything works in the admin browser, but in a private window or for another user the button is missing or unresponsive. Possible causes include cache, mismatched script versions, optimization protection, resource access permissions, or a CDN that has not been purged. Test the page while logged out, then temporarily disable caching for that page.

Fix: clear every cache layer, check the browser console for JavaScript errors, and confirm that the plugin files are publicly available to visitors. If the issue appears only after enabling a specific optimization feature, create an exception or change the script delay mode.

The button is covered by the header, chat widget, or popup

Symptom: the lightbox opens, but part of the interface is blocked by a sticky header, live chat, banner, or popup window. The cause is an interface layering conflict, z-index, or a global theme style. Test the page without popup widgets and temporarily disable the sticky header if your theme settings allow it.

Fix: create an exception for the popup on gallery pages or change its behavior. If a custom CSS change caused the conflict, roll back the latest edits and test again. Do not keep raising z-index values for every element, because that can break other modal windows on the site.

A gallery inside a tab or slider displays incorrectly

Symptom: Fullscreen works on a normal page, but not inside a tab, accordion, or slider. The reason may be that the gallery and lightbox initialize while the container is still hidden. Test the same gallery on a simple standalone page. If it works there, the issue is tied to the builder environment.

Fix: place the gallery in a visible container, use the builder's settings for proper hidden-content initialization, or choose a different way to present the images. If the page allows it, the better option is often to move an important gallery out of a complex hidden block.

How to tell whether the setup actually improved the page

A technically working button does not automatically make the page more useful. After setup, look at user behavior: do people open images, spend time viewing them, return to the page, and stay on track with the main action? If the site has event tracking, you can monitor image clicks or gallery interaction, but even manual checking already tells you a lot.

Signs of a good outcome

• The gallery loads quickly and does not shift the page when images appear.
• Clicking an image opens a clear, predictable lightbox.
• The fullscreen button is visible without competing with close and navigation controls.
• The fullscreen image is sharp enough for its intended purpose.
• After exiting, the user returns to the page and can continue the journey.

If at least two of these conditions are not met, do not keep the setup just because it "looks nice." Revisit image size, lightbox behavior, and the number of controls. Sometimes the best outcome is to use Fullscreen only for the primary galleries and keep secondary ones simpler.

What to recheck after updates

After updating Modula, the theme, the page builder, or an optimization plugin, review the gallery again. You do not need to repeat the entire test flow for every page, but at least one control gallery should stay on your checklist. This is especially important after changes to caching, minification, script delay, or the page template structure.

Speed, SEO, and accessibility for a fullscreen gallery

Fullscreen is part of the user interface, but its setup affects broader concerns too: page speed, how clearly search engines understand the images, accessibility for keyboard users, and the overall sense of site quality. Do not claim that the fullscreen button alone will improve SEO. That would be misleading. But a well-managed gallery helps prevent the kinds of problems that hurt page perception and make it harder for users to explore the material.

Speed: do not confuse quality with oversized source files

It is natural to want larger images for Fullscreen. But larger does not mean arbitrarily heavier. If the gallery contains twenty huge files with no optimization, the page may become slow before the visitor even opens the lightbox. In that case, fullscreen mode may be technically functional, but the user will leave before they ever see the button.

A practical compromise is this: use source images with enough quality for the frames that truly need fullscreen inspection, and do not turn secondary images into oversized files. Test the page after clearing cache and in a private window. If the top of the page feels heavy, reconsider the number of images in the gallery, file sizes, and optimization settings. At the same time, do not enable aggressive script delay without testing the lightbox.

SEO: captions and alt text should explain the image

A gallery should not be just a set of unnamed files. For important images, add clear titles, alt text, and captions when they help the user. Alt text should not become a pile of keywords. Its job is to briefly describe the image content. If the image shows a renovated kitchen, the alt text should say that. If it is a diagram, the alt text should explain what the diagram shows. You do not need to insert the name Modula Fullscreen into the alt text of every image on the site.

Use captions carefully. They can help on the page, but inside the lightbox a long description may get in the way of viewing. If the project description is substantial, place it next to the gallery and keep the caption as a short orienting note. Search engines and users both benefit more from clear surrounding context than from overloaded text layered on the image.

Accessibility: keyboard use, focus, and a clear exit path

Fullscreen mode should remain easy to control. Make sure users can close the view with Esc, that the controls are visible, that they are not blocked by the header or a popup widget, and that users do not lose their place after exiting. If the site already uses modal windows, popup forms, and chats heavily, Fullscreen needs to be tested alongside them. Two competing modal flows on one page often create confusion.

For audiences that are not comfortable with complex interfaces, fewer lightbox controls are usually better. Navigation, close, and fullscreen viewing form a clear set. If you add too many extra actions, visitors may miss the one they need or click the wrong thing by accident. Accessibility here is not just about keyboard support on paper. It is also about giving users a clear path with as few decisions as possible.

Security and external scripts

Fullscreen does not require you to expose secrets, tokens, or access credentials to visitors. But the gallery still relies on public resources: images, styles, and scripts. That is why you should not add questionable third-party libraries just to create a cosmetic effect around the lightbox. If you want to improve the page, use Modula settings, theme settings, and careful CSS. The fewer random scripts you put around the gallery, the easier the site is to maintain and troubleshoot.

If you use a CDN, image optimization, or deferred loading, test not only the first visit but also a repeated page load. Sometimes the issue appears only after cache has already been built. A proper control test always includes a private window and a cleared cache. That is a simple safeguard against the false impression that everything works just because the administrator is seeing a fresh version.

Modula Fullscreen FAQ

Do I need to enable Fullscreen separately for each gallery?

Check the settings of the specific gallery under Lightbox & Links. What matters is not only that the add-on is active, but that the required button is enabled where users actually open images. On sites with multiple galleries, this makes it easier to turn fullscreen on only where it belongs.

Why is the button not visible after installing the add-on?

Most often, you need to check three things: whether the add-on is activated, whether the option is enabled in the lightbox settings of the target gallery, and whether cache has been cleared. If the page is still serving old scripts or old markup, you may be looking at the version from before the setting was changed.

Can I use Fullscreen without the regular lightbox?

In practice, Fullscreen is tied to the lightbox flow: the user opens the image first, then enables fullscreen mode. If the click behavior is not set to open the lightbox, check Lightbox & Links and make sure the actions are not conflicting.

Does fullscreen mode affect page loading speed?

The button itself should not become the main reason a page is slow, but the overall gallery weight, source image size, number of images, and script optimization all affect speed. For fullscreen viewing, it is especially important not to sacrifice source image quality, while also avoiding unnecessarily heavy files.

What should I do if Fullscreen breaks after optimization is enabled?

Temporarily disable minification, combining, delaying, and deferred loading of JavaScript for the page with the gallery. If the issue disappears, restore the settings one by one and create an exception for the conflicting rule. Modula's documentation includes separate articles about conflicts with popular optimization tools.

Should fullscreen mode be enabled on mobile devices?

Test the real behavior on a mobile screen. If the button helps users inspect the image and does not interfere with closing the lightbox, you can keep it. If the interface feels cramped or users get confused about how to exit, it is better to simplify the mobile viewing flow and rely on a strong gallery grid instead.

Can I change the appearance of the button with code?

It is better to start with Modula's built-in settings, plus the theme and lightbox settings. If you only need a small adjustment around the gallery, add CSS through a child theme or the WordPress Additional CSS area. Do not edit plugin files, because those changes may be lost after updates or trigger conflicts.

When Modula Fullscreen is the right choice

Modula Fullscreen is worth using when the site already has Modula galleries and the images genuinely need to be viewed at a larger size. It is a practical add-on for portfolios, photo reports, visual case studies, and content where details matter more than quick decorative browsing. Its value does not come from the button by itself, but from a well-built user path: the visitor sees the grid, opens a frame, switches to fullscreen, studies the image, and returns to the page without friction.

Before rolling it out, check the base gallery, image quality, the Lightbox & Links settings, behavior on the published page, and cache compatibility. If everything works in a private window, survives optimization, and remains clear to a regular visitor, the add-on is ready to stay on live pages.

If you are ready to test it on your own site, go to the download block and download Modula Fullscreen. Start with one test gallery, record your changes, and verify the outcome while logged out. That approach is safer than enabling fullscreen across every page at once and then trying to trace the source of a conflict afterward.

The takeaway is simple: this add-on works well for sites where the gallery needs to function as a comfortable viewer for visual material. But if the images are small, the page is overloaded with scripts, or the visitor's main goal sits outside the gallery, improve the content and page environment first. Fullscreen mode strengthens a strong gallery, but it does not replace thoughtful structure, good source images, or careful testing.