-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught SyntaxError: Unexpected token , in JSON #14977
Comments
You need to flush all the caches and delete all generated data. Recompile the code too, with your caches disabled and file access to the entire magento root directory offline (this includes the web server, caching systems such as Varnish, and running cron schedules). If you have any systems running automated health checks/pings through Any time you get these "Uncaught SyntaxError: Unexpected token" type of errors in your JS right after an upgrade (there will usually be many, many JS errors) you need to clear out the caches. Also, if you are using the default backend caching to the filesystem, make sure the file and directory permissions are correct. There is a bug that causes incorrect permissions in I hope that helps... good luck! |
I will try that - I kept wiping cache, set perms and the like but maybe I missed something. The thumbnails show up for all products but when you get into the product page, then it just spins the gif. Thanks! |
Same for me, had to revert back to previous version 2.2.3 ! Still no idea how to resolve ! |
Unfortunately those suggestions did not work. Thumbnails still work everywhere but actual product images refuse to load. I know they exist on the server and 2.2.3 had zero issues with this. I'm glad @sidchs chimed in so I know it's not just my installation. |
OK - I found out that it's my theme. I added an underscore to the filename of app/design/frontend/mytheme/Magento_Catalog/templates/product/viewgallery.phtml in hopes that it would skip using my theme's version. I refreshed and the images now show. I guess I have to compare the native gallery.phtml to my theme's gallery.phtml and find out what changed. |
You are having exact same issues as me ! Thumbnails etc fine, product images just spinning disk ! Happening to me on 2 installs ! |
@sidchs Did you try doing what I posted right above? |
Hi, I hopefully will try overnight UK time, otherwise it will affect live sites !
Will keep you informed , appreciate your help thanks
From: Matt
Sent: Friday 4 May, 17:12
Subject: Re: [magento/magento2] Uncaught SyntaxError: Unexpected token , in JSON (#14977)
To: magento/magento2
Cc: sidchs, Mention
@sidchs Did you try doing what I posted right above?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi, I have the same issue with theme "Moza". Thanks for the help. |
Same issue here except that mine were random. Most product images would still load but others would show the spinning ball of death and throw, "Uncaught SyntaxError: Unexpected token N in JSON at position 84." I have done everything starting with flushing to removing all the generated files, re-compiling, and re-deploying. I've even restarted the server. Nothing works. |
If you're running a custom theme, I'd suggest trying the above or even removing a few a time (just add _ to filenames, of course keep cache off so you don't need to flush). |
Hello,
I have tried this morning your suggestions – however before I got to the point I have incurred further problems when upgrading to 2.2.4
See below
Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory.
The following modules are outdated:
Magento_Directory data: current version - 2.0.1, required version - 2.0.2
Magento_Customer data: current version - 2.0.12, required version - 2.0.13
Magento_Catalog data: current version - 2.2.3, required version - 2.2.4
Magento_Quote data: current version - 2.0.6, required version - 2.0.7
Magento_Sales data: current version - 2.0.7, required version - 2.0.9
Amazon_Core data: current version - none, required version - 2.0.4
Amazon_Login data: current version - none, required version - 1.2.0
Magento_Newsletter data: current version - 2.0.0, required version - 2.0.1
Amazon_Payment data: current version - none, required version - 1.11.0
Magento_Vault data: current version - 2.0.2, required version - 2.0.3
Klarna_Core schema: current version - none, required version - 4.1.5
Klarna_Core data: current version - none, required version - 4.1.5
Klarna_Ordermanagement schema: current version - none, required version - 4.1.2
Klarna_Ordermanagement data: current version - none, required version - 4.1.2
Klarna_Kp schema: current version - none, required version - 5.1.3
Klarna_Kp data: current version - none, required version - 5.1.3
Dotdigitalgroup_Email schema: current version - 2.3.8, required version - 2.4.9
Dotdigitalgroup_Email data: current version - 2.3.8, required version - 2.4.9
Temando_Shipping schema: current version - 0.3.1, required version - 1.1.0
Temando_Shipping data: current version - 0.3.1, required version - 1.1.0
Vertex_Tax schema: current version - none, required version - 100.1.0
Vertex_Tax data: current version - none, required version - 100.1.0
I have ‘Run "bin/magento setup:upgrade"’ as suggested , but this solved nothing.
Any further help appreciated
Thanks again
From: damien-lechopier <notifications@github.com>
Sent: 07 May 2018 09:30
To: magento/magento2 <magento2@noreply.github.com>
Cc: sidchs <simon1@discountheating.com>; Mention <mention@noreply.github.com>
Subject: Re: [magento/magento2] Uncaught SyntaxError: Unexpected token , in JSON (#14977)
Hi,
I have the same issue with theme "Moza".
The solution to remove the file app/design/frontend/mytheme/Magento_Catalog/templates/product/gallery.phtml
works for me too.
Thanks for the help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#14977 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AlLgM_wdoNQwnEkEvZmOVDNPgMEcv_CQks5twAYjgaJpZM4Tx0Ph> . <https://github.com/notifications/beacon/AlLgMzy0f-QlCSXUZ9tuw9ReT0FXHUCKks5twAYjgaJpZM4Tx0Ph.gif>
|
problem is the JSON object is broken and cannot be parse. take a look at the line
to fix this, in your custom theme file app/design/frontend/{Vendor}/{theme}/Magento_Catalog/templates/product/view/gallery.phtml
change to
you may need to check other property and surround it with "if" condition |
this work for me validating the json options, thanks |
Found it. Any of my products that have the quote symbol (") in the title are not loading the image. Apparently they are not being formatted into special characters and are causing the image not to load regardless of the theme. |
Thank you all for trying to help on this
Unfortunately I am getting the same error – I have tried all suggested
Error is:
Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory.
The following modules are outdated:
Amazon_Core data: current version - none, required version - 2.0.4
Amazon_Login data: current version - none, required version - 1.2.0
Amazon_Payment data: current version - none, required version - 1.11.0
Klarna_Core schema: current version - none, required version - 4.1.5
Klarna_Core data: current version - none, required version - 4.1.5
Klarna_Ordermanagement schema: current version - none, required version - 4.1.2
Klarna_Ordermanagement data: current version - none, required version - 4.1.2
Klarna_Kp schema: current version - none, required version - 5.1.3
Klarna_Kp data: current version - none, required version - 5.1.3
Vertex_Tax schema: current version - none, required version - 100.1.0
Vertex_Tax data: current version - none, required version - 100.1.0
From: leekung <notifications@github.com>
Sent: 10 May 2018 11:20
To: magento/magento2 <magento2@noreply.github.com>
Cc: sidchs <simon1@discountheating.com>; Mention <mention@noreply.github.com>
Subject: Re: [magento/magento2] Uncaught SyntaxError: Unexpected token , in JSON (#14977)
problem is the JSON object is broken and cannot be parse. take a look at the line
"showCaption": ,
to fix this, in your custom theme file app/design/frontend/{Vendor}/{theme}/Magento_Catalog/templates/product/view/gallery.phtml
find the line
"allowfullscreen": <?php /* @escapeNotVerified */ echo $block->getVar("gallery/allowfullscreen"); ?>,
"showCaption": <?php /* @escapeNotVerified */ echo $block->getVar("gallery/caption"); ?>,
"width": <?php /* @escapeNotVerified */ echo $image_width; ?>,
change to
<?php if (($block->getVar("gallery/allowfullscreen"))): ?>
"allowfullscreen": <?= /* @escapeNotVerified */ $block->getVar("gallery/allowfullscreen") ?>,
<?php endif; ?>
<?php if (($block->getVar("gallery/caption"))): ?>
"showCaption": <?= /* @escapeNotVerified */ $block->getVar("gallery/caption") ?>,
<?php endif; ?>
"width": <?php /* @escapeNotVerified */ echo $image_width; ?>,
you may need to check other property and surround it with "if" condition
take a look at magento template file
vendor/magento/module-catalog/view/frontend/templates/product/view/gallery.phtml for reference
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#14977 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AlLgM77zvoSJmLjTxxPIWlklnlpQEKwyks5txBQ0gaJpZM4Tx0Ph> . <https://github.com/notifications/beacon/AlLgM0Jxo-eRJeELif1l6v8RDF6MlMGOks5txBQ0gaJpZM4Tx0Ph.gif>
|
i have tried solution of @sidchs but its not working. |
i removed following code from my theme porto 3.0.4 .
|
@leekung method works although the attribute is different. My empty attributes are "arrows" and "showCaption" inside "fullscreen" I think every case can refer to different attributes, Magento side should have a better attribute checking on this file. |
I'm having the same issue, but none of the above works. I'm not using a theme gallery.phtml, just the luma default. I've also checked to make sure no special characters in the filenames. No attributes for the product and only one image file. I'm also having issues with the content of the details tab showing on the product page. The tab is visible, but clicking on it doesn't show any of the long description, it just bounces down the page. The content is visible in google dev tools when viewing the elements, so probably a javascript issue opening/switching to the tab (which should show by default). I've reset file permissions, manually cleared the cache, recompiled, flushed cache, redeployed the static content, and reindexed. Nada, zip, zilch. As stated above, not all images are blocked, but I can't see any differences as to why this one and not that. exemplar page link: ((http://theplasticmart.com/acrylic-tv-stand-36-waterfall-riserstyle.html#product.info.description)) text of js error: VM1971:5 Uncaught SyntaxError: Unexpected token w in JSON at position 137 |
That's exactly what mine is doing - same with the content on tabs all messed up. I can't fix ! Still back at previous version 2.2.3
On Wed, May 23, 2018 at 6:34 AM +0100, "dschmidthawk" <notifications@github.com> wrote:
I'm having the same issue, but none of the above works. I'm not using a theme gallery.phtml, just the luma default. I've also checked to make sure no special characters in the filenames. No attributes for the product and only one image file.
I'm also having issues with the content of the details tab showing on the product page. The tab is visible, but clicking on it doesn't show any of the long description, it just bounces down the page. The content is visible in google dev tools when viewing the elements, so probably a javascript issue opening/switching to the tab (which should show by default).
I've reset file permissions, manually cleared the cache, recompiled, flushed cache, redeployed the static content, and reindexed. Nada, zip, zilch. As stated above, not all images are blocked, but I can't see any differences as to why this one and not that.
exemplar page link: ((http://theplasticmart.com/acrylic-tv-stand-36-waterfall-riserstyle.html#product.info.description))
text of js error:
VM1971:5 Uncaught SyntaxError: Unexpected token w in JSON at position 137
at JSON.parse ()
at getData (main.js:58)
at Array.map ()
at HTMLDocument.apply (main.js:74)
at fire (jquery.js:3232)
at Object.add [as done] (jquery.js:3291)
at jQuery.fn.init.jQuery.fn.ready (jquery.js:3542)
at jQuery.fn.init (jquery.js:2967)
at new jQuery.fn.init (jquery-migrate.js:225)
at jQuery (jquery.js:75)
getData @ main.js:58
apply @ main.js:74
fire @ jquery.js:3232
add @ jquery.js:3291
jQuery.fn.ready @ jquery.js:3542
jQuery.fn.init @ jquery.js:2967
jQuery.fn.init @ jquery-migrate.js:225
jQuery @ jquery.js:75
(anonymous) @ bootstrap.js:20
execCb @ require.js:1650
check @ require.js:866
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
enable @ require.js:1143
init @ require.js:774
(anonymous) @ require.js:991
(anonymous) @ require.js:132
(anonymous) @ mixins.js:106
execCb @ require.js:1650
check @ require.js:866
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
enable @ require.js:1143
init @ require.js:774
(anonymous) @ require.js:991
(anonymous) @ require.js:132
(anonymous) @ mixins.js:106
execCb @ require.js:1650
check @ require.js:866
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
enable @ require.js:1143
init @ require.js:774
(anonymous) @ require.js:991
(anonymous) @ require.js:132
(anonymous) @ mixins.js:106
execCb @ require.js:1650
check @ require.js:866
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
(anonymous) @ require.js:1113
(anonymous) @ require.js:132
(anonymous) @ require.js:1156
each @ require.js:57
emit @ require.js:1155
check @ require.js:917
enable @ require.js:1143
init @ require.js:774
(anonymous) @ require.js:991
(anonymous) @ require.js:132
runCallbacks @ domReady.js:24
callReady @ domReady.js:35
pageLoaded @ domReady.js:50
load (async)
(anonymous) @ domReady.js:59
execCb @ require.js:1650
check @ require.js:866
enable @ require.js:1143
init @ require.js:774
callGetModule @ require.js:1170
completeLoad @ require.js:1544
onScriptLoad @ require.js:1671
load (async)
req.load @ require.js:1882
load @ require.js:1639
load @ require.js:820
fetch @ require.js:810
check @ require.js:840
enable @ require.js:1143
enable @ require.js:1511
(anonymous) @ require.js:1128
(anonymous) @ require.js:132
each @ require.js:57
enable @ require.js:1090
init @ require.js:774
callGetModule @ require.js:1170
completeLoad @ require.js:1544
onScriptLoad @ require.js:1671
load (async)
req.load @ require.js:1882
load @ require.js:1639
load @ require.js:820
fetch @ require.js:810
check @ require.js:840
enable @ require.js:1143
enable @ require.js:1511
(anonymous) @ require.js:1128
(anonymous) @ require.js:132
each @ require.js:57
enable @ require.js:1090
init @ require.js:774
callGetModule @ require.js:1170
completeLoad @ require.js:1544
onScriptLoad @ require.js:1671
load (async)
req.load @ require.js:1882
load @ require.js:1639
load @ require.js:820
fetch @ require.js:810
check @ require.js:840
enable @ require.js:1143
enable @ require.js:1511
(anonymous) @ require.js:1128
(anonymous) @ require.js:132
each @ require.js:57
enable @ require.js:1090
init @ require.js:774
callGetModule @ require.js:1170
completeLoad @ require.js:1544
onScriptLoad @ require.js:1671
load (async)
req.load @ require.js:1882
load @ require.js:1639
load @ require.js:820
fetch @ require.js:810
check @ require.js:840
enable @ require.js:1143
enable @ require.js:1511
(anonymous) @ require.js:1128
(anonymous) @ require.js:132
each @ require.js:57
enable @ require.js:1090
init @ require.js:774
callGetModule @ require.js:1170
completeLoad @ require.js:1544
onScriptLoad @ require.js:1671
load (async)
req.load @ require.js:1882
load @ require.js:1639
load @ require.js:820
fetch @ require.js:810
check @ require.js:840
enable @ require.js:1143
enable @ require.js:1511
(anonymous) @ require.js:1128
(anonymous) @ require.js:132
each @ require.js:57
enable @ require.js:1090
init @ require.js:774
callGetModule @ require.js:1170
completeLoad @ require.js:1544
onScriptLoad @ require.js:1671
load (async)
req.load @ require.js:1882
load @ require.js:1639
load @ require.js:820
(anonymous) @ require.js:806
(anonymous) @ require.js:132
execCb @ require.js:1650
check @ require.js:866
enable @ require.js:1143
init @ require.js:774
(anonymous) @ require.js:1416
setTimeout (async)
req.nextTick @ require.js:1755
localRequire @ require.js:1405
fetch @ require.js:805
check @ require.js:840
enable @ require.js:1143
enable @ require.js:1511
(anonymous) @ require.js:1128
(anonymous) @ require.js:132
each @ require.js:57
enable @ require.js:1090
init @ require.js:774
callGetModule @ require.js:1170
completeLoad @ require.js:1544
onScriptLoad @ require.js:1671
load (async)
req.load @ require.js:1882
load @ require.js:1639
load @ require.js:820
fetch @ require.js:810
check @ require.js:840
enable @ require.js:1143
enable @ require.js:1511
(anonymous) @ require.js:1128
(anonymous) @ require.js:132
each @ require.js:57
enable @ require.js:1090
init @ require.js:774
(anonymous) @ require.js:1416
setTimeout (async)
req.nextTick @ require.js:1755
localRequire @ require.js:1405
window.require @ mixins.js:245
(anonymous) @ acrylic-tv-stand-36-waterfall-riserstyle.html:1458
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Short version: this is a theme issue. Make sure your theme has been updated with the relevant changes for 2.2.4. We use Porto and it broke the same way. |
Had same issue upgrading from 2.2.3 to 2.2.4 so looking at solutions above I replaced the file app/design/frontend/mytheme/Magento_Catalog/templates/product/gallery.phtml Cleared cache and all working now. I see some suggestions above to just remove app/design/frontend/mytheme/Magento_Catalog/templates/product/gallery.phtml |
Any word on this? Using the Luma theme so not a theme issue. The Luma gallery.phtml has the updated json language, no files to replace since using Luma files. So none of the fixes above have worked. Issue can be seen at link at my issue above. |
This was resolved for me from https://github.com/magento/magento2/blob/2.2-develop/app/code/Magento/Catalog/view/frontend/templates/product/breadcrumbs.phtml. The quotes needed to be escaped. |
I'm a Porto 3.1.2 (child) user running Magento 2.2.5. @PaperDS solution worked a treat for me. I'm yet to work out why Porto requires a custom file. Low on my list of things to think about right now though... Thanks for the solution! |
I was experiencing same issue. Having "s in the product name is what was the problem. It put " next to "in the JS. So TV 36" wide had to be TV 36inches wide or TV 36 Wide, no inches. |
Hi @heyepic I cannot reproduce by your scenario steps. In clean magento install |
I am not sure if this adds anything to the conversation but I will chime in anyway. I changed all product title characters with multi-quotes to two single quotes. This didn't alter URLs or anything other than the title and fixed the JSON issue. A screenshot demonstrating the issue on a fresh Magento 2 install 2.2.5: |
Hi folks There are two issues being discussed in here. The first one from @heyepic, that one has a fix over here: https://github.com/magento/magento2/pull/16594/files Fix is scheduled for Magento 2.2.7 (or 2.2.6, it's a bit unclear for me) The other one from @erichagz & @KSaho, has a fix over here: https://github.com/magento/magento2/pull/15521/files This fix is scheduled for Magento 2.2.6 (was targeted for 2.2.5 but then they missed it somehow) Hope this is enough info so people can try to resolve their current issues. :) |
i see global problem with use previusly this method work as: "loop": true, return true and false values. and now: "loop": 1, on "true' = 1 |
@Nix-id: see discussion over here: #17920 (comment) |
@hostep then i will don't get errors with my theme after update magento... how many places use this method getVar in Magento. |
PR #18443 fixes this issue. Well, it makes the gallery.phtml work properly with the current implementation of the getVar routine atleast. Once PR #18443 has been merged and everything is working ok again, I will look to reinstate my PR that reverts the changes made to the getVar routine, but this may be slow time. |
for me the same issue, but I dont find gallery.phtml in Magento 2.2.4 version. Im using Porto theme and have no idea what went wrong. I just added NGINX with Apache and suddenly this stopped working. And its not just picture not loading even size and color dropdown values not loading pls check the picture attached JQMIGRATE: Logging is active Pls provide your guidance to fix this issue |
please post the gallery sections of your themes view.xml file. |
Also, view source on your page and look for the fotorama section of code. There will be some json code that is missing a field and is incorrectly formatted. Look for an entry like
You probably have an entry like That will give you a pointer as to what is wrong. |
These issue are all resolved in the latest release by the way, but if you want a workaround without updating, follow the above. |
Hi @gwharton sorry im not able to get you what is the gallery section of the theme. if you look at my website i can give you the link you can see the error here. Im not sure what's wrong it was working earlier and suddenly it stopped working may be some issue, not able to understand this. I can provide the full details - we were running apache web server and sometimes the size and the color dropdown was not loading on the same page above and when we refresh it loads, so somebody recommended to install NGINX alongwith Apache and this issue will resolve. And when we completed that it didnt resolve rather it behaving this way and even if we uninstall nginx even then it doesnt work and behave this way only. |
No problem, A quick look at the source of your webpage shows this section
You can see that in the options section "showCaption" does not have a value set These values are read from your view.xml file in your theme. Version 2.2.4 of magento had some serious bugs in the processing of these variables, which means that for some view.xml settings, the errors happen, like you have above. Can you locate your view.xml file. It should be in your theme folder Where is the name of your theme. Can you open that file and post the
|
Dear @gwharton - thank you for such a quick response. it looks like the view.xml is correct. Im attaching it here. i changed it to txt file so that it can be uploaded here.
not able to get it whats going wrong here without making code change. |
OK, that view.xml file doesnt seem to be the right one as it is not matching the setting on your webpage. Your webpage indicates that the following values are set to false gallery/captions but the view.xml file shows they are not all false. You have 3 options.
|
I too can't explain why this is happening if, as you say, there has been no code changes. The bug only happens in 2.2.4 for entries in the theme view.xml where values are set to false. When they are set to true, the bug does not happen. Did you update or change themes recently. Perhaps the previous version of the theme had these values set true. |
Dear @gwharton - YOU ARE AWESOME to say the least. Thank you my dear friend - you solved my big issue and i was struggling with it from last 20 days with no resolution. Thank you so much !! Now everything works well but on click it opens a full page of image viewer but doesnt provide any CLOSE option for that window/page, it covers entire screen with no option to go back. Is there any way we can include the CLOSE option in the full screen page to go back to the product page , because majority of the times customers will click back button and that will take them to the list page and their product page will be lost. |
yes it shows magnifying icon but not the close option, anyways this is workable. Thank you so much @gwharton Im running through one more issue with 2.2.4 but i found that its a bug in the tool. Mya be you might have some workaround for that. When we add a product in the cart, and click on "Go to Checkout" it takes to this page https://www.colorcherry.com/checkout/#payment and we apply the Discount code, then it doesn't work there. But if you go to "View Cart" and you enter the discount code then it works there. Not sure if there is any solution for this issue. |
No idea on your separate issue I am afraid. not something that I have seen. I have just had another thought about your original issue. The problem is that variables in your view.xml file are not processed properly when they are set as false. The first workaround was to change them to true and accept the fact that you would get fullscreen and captions, but instead of changing them to true, you could try removing the line entirely from the view.xml (well, or better to comment them out). This should have the effect of removing the erronous content from your webpage and letting the fotorama library set the default options for fullscreen and caption (which I think has fullscreen set to false and caption set to false). (This should work, aslong as it is not inheriting the values from a parent theme). I havent tried this myself. was just thinking. Worth a go atleast. |
thank you @gwharton - i will try that as well. |
I think it is possible to use:
instead of:
in |
Preconditions
Steps to reproduce
Expected result
Actual result
This is the error: Uncaught SyntaxError: Unexpected token , in JSON at position 1025, from a JSON array. Attached an image. Here is the full data array "data": [{"thumb":"https:\/\/v3.asdf.com\/pub\/media\/catalog\/product\/cache\/460a3bcbdb4cc235aac43a6f81f8f135\/s\/j\/sjm2016.jpg","img":"https:\/\/v3.asdf.com\/pub\/media\/catalog\/product\/cache\/c687aa7517cf01e65c009f6943c2b1e9\/s\/j\/sjm2016.jpg","full":"https:\/\/v3.asdf.com\/pub\/media\/catalog\/product\/cache\/926507dc7f93631a094422215b778fe0\/s\/j\/sjm2016.jpg","caption":"SJM 2016 Camaro Line Lock","position":"1","isMain":true,"type":"image","videoUrl":null}],
The text was updated successfully, but these errors were encountered: