I’m using a CMS collection to display a table. In the collection one of the fields (View Part), The field type is “Image”. After a bit of hassle I got it figured out and working. However, is there a way to make the image expand, or popup in a window when clicked?
I don’t mind changing the thumbnail to a text link or button, I just really need the end user to be able to view the image full size somehow.
Thanks in advance.
View of collection
View on website
Thank you for your reply.
That makes sense, but I’m completely lost as to where to place this code.
You are showing only cor collection, but your collection is connected to a page or even to a PRODUCT-PAGE, right? Or maybe a DYNAMIC-PAGE?
Since you never really mentioned your setup, those are all just guesses.
Anyone can see your setup.
However …
Now, you will see a code-section where you will find some code like…
…similar to…
$w.onReady(()=>{cosnole.log('Page is ready!');
// some code....
// some code....
// some code....
// some code....
// some code....
});
Your IMAGE-ELEMENT on your page will have an ID (when selecting the image you will see the ID in the PROPERTY-PANEL)
—> let action = $w(“#myImage”).clickAction; //---->" (ID = myImage in this example)
Now modify the code for your page to take control over your image-element…
$w.onReady(()=>{cosnole.log('Page is ready!');
// some code....
$w("#myImage").clickAction = "magnified";
// more code....
});
Copy + Paste + test it 
I “Think” its a static page. My experience with web design is mostly Joomla based and it’s been several years since I’ve used that, so I’m kind of lost.
I did activate the DEV node and added the snippet you provided, but it didn’t seem to do anything.
I REALLY appreciate your help on this, I think if I can figure this out it will open a lot of doors for my project. I will be create several pages like this so being able to just change
I guess maybe I should be pulling in all text and images from collection rather that just placing them in the editor directly on the page?
Well that was one of the most important questions, before developing and designing your Website.
As i can see, you maybe already did a lot of mistakes, generating a → STATIC WEBSITE <–.
Your website should start inside your collection!
Suggested steps how to generate a DYNAMIC-WEBSITE.
The DATABASE, especially it’S structure is the most important part of your website.
To be capable to generate a DYNAMIC and DATA-DRIVEN WEBSITE, you will need a perfect aligned DATABASE (collection).
Another important Question will be which Website-Elements you will want to use, which will also determine which direction your website will go …
a) …eighter using all the already WIX-PREDEFINED-STUFF like (tables, repeaters, datasets, apps, gallaries and so on and so on …
…or…
b) going a more custom way, which often results in ---> CODING-WAY <---.
Since you are not a real CODER, i guess you will want to choose WAY-A. But you can still mix it with own CODED-SOLUTIONS anyway.
When and why you should use —> CODE <— ???
Well there are many reasons when and why you should prefer the CODING-WAY.
Not using CODE makes your site less customizable (you already feel it, because you can’t always do exactly the way you want.
Another important thing is → using PREDEFINED stuff you do not realy know about how it was coded and what it is doing on the background (background-processes) → can slow down your website (and yes, it will slow down your website the more you use it)
Another negative aspect of using predefined stuff you immediately will see as soon as you open the console on your website, take a look onto the following logs…
As you can see, you already have a lot of warnings. Most of them are harmless but still those warnings already existing.
What i want to tell you at this point is to be carefull what kind of element you want to place on your website, especially WIDGETS or APPS from the Wix-Marketplace.
The most mostly do not provide enough flexibility and customization options and you can get stuck very fast on things if it comes to customization processes.
.
.
INVESTIGATION:
1. 
Unrecognized feature: 'vr'Meaning:
This message comes from Chrome’s security feature policy. Some Wix pages include a <meta http-equiv="origin-trial"> or <iframe allow="vr"> attribute for Virtual Reality (VR) or WebXR content.
Modern browsers don’t recognize 'vr' anymore — it’s deprecated.
Fix:
Ignore it. It’s harmless and controlled by Wix’s internal code, not yours.
2. customCssClasses is deprecated, please use formatClassNames insteadMeaning:
Some older Wix components (or apps added to your site) use an outdated API.
Wix’s internal JavaScript (class-names-formmater.js) now prefers a new method formatClassNames().
Fix:
If you’re not using custom code, ignore this — Wix will fix it in a future update.
If you added custom Wix Velo code, search your scripts for customCssClasses and replace it with formatClassNames().
3. Firebase is already defined in the global scopeMeaning:
You have multiple Firebase libraries loading on the same page — either because:
Fix:
<script src="https://www.gstatic.com/firebasejs/..."> if Wix already includes it.
4. The resource was preloaded but not used within a few secondsMeaning:
This is a performance warning from Chrome.
Your Wix page preloads assets (like JavaScript bundles or icons) to speed things up — but if they’re not actually used right away, Chrome warns that preloading might be unnecessary.
Fix:
You can’t directly fix this in Wix — these are automatically added preload links.
They don’t break your site, they just slightly reduce efficiency.
Wix does this aggressively for optimization; Chrome is just being picky.
5. Large URLs and “Thunderbolt” script messagesMeaning:
These long URLs (with parameters like thunderbolt?appDefinitionIdToSiteRevision=...) come from Wix’s Thunderbolt rendering engine — it handles:
Fix:
These are not real errors, just warnings about preload or caching behavior.
Ignore them unless you have a specific page loading problem.
TL;DR – What’s actually happening| Warning / Error | Cause | Harmless? | Fixable by you? |
|---|---|---|---|
Unrecognized feature: 'vr' |
Deprecated browser feature |  Yes |
 No |
customCssClasses is deprecated |
Outdated Wix component | Yes |
Only if you wrote custom code |
Firebase already defined |
Duplicate Firebase script |  Medium |
Yes (remove duplicate) |
Preload but not used |
Wix optimization preload | Yes |
No |
Thunderbolt URL preload |
Wix runtime / A/B experiments | Yes |
No |
.
.
Back to your Website … (here we can see your HOMEPAGE)…
Taking a closer look onto your NAVIGATION-MENU …
I asume you are generating STATIC PAGES FOR EVERY SINGLE MACHINE (one web-page for each of your available machine for presentation) → What is the absolute wrong way !!!
And another beginner failure is to use → TABLES <–. I mean TABLES are ok, but there are better ways to do a presentation.
What could be your solutions?
How to generate a dynamic webpage?
You simply generate a normal website, placing all needed elements onto your page first → (IMAGES, BOXES, INPUT-FILDS, OUTPUT-FIELDS, BUTTONS and so on), then you right-click the generated page in your Wix-Editor pages-menu and convert it into a dynamic one, which will generate automatically a dynamic —> DATASET <—. This DYNAMIC-DATASET, will connect all the elements on your generated PAGE with your COLLECTION (database) in the background.
What is the benefit doing this?
Your whole website becomes dynamic and data-driven.
-less time-consuming maintenance of your website, since now you can simply manage your whole website directly inside your collection, by adding or editing data, which will be shown automatically on your dynamic web-page. → NO NEED TO GENERATE EACH PAGE MANUALLY FOR EVERY NEW ITEM IN YOUR COLLECTION.
A little culprit: ALL PAGES WILL LOOK IDENTICAL, only showing different data.
BUT THIS CAN ALSO BE MANAGED by CODE!!!
Both can be connected to the DATABASE using datasets or CODING aswell.
I would recommend REPEATERS i guess.
So, as you can see there are a lot of question, if you really should continue to go your static web-developent at all, or better start from scratch and REDESIGN everything starting with a perfect DATABASE-STRUCTURE first, answering questions of what kind of types your datafields will include, for example…
Then deciding to choose the right elements which will represent those formats.
Also you did not mention if you have used any kind of APPS or WIDGETS!
MOST APPS AND WIDGEST, are somekind of SELF-INCLOSED-ELEMENTS (not really customizable), you should also know about that!
So, now you have a little more information about your own website, maybe it will open your eyes a little bit more.
