SUPEE 10975 but still getting warnings
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
We installed SUPEE 10975 a while ago and more patches since. Lately we are getting warnings that jQuery is out of date and I'm not quite sure what to do.
SUPEE-10975 - Failed.
Outdated JQuery library v.1.12.0 found (PRODSECBUG-2108), got '200'.
The patch was installed successfully. The only thing I can think of at the moment is to grab the jQuery files from the latest Magento release and manually use them to replace the files on the server
Do you guys have any thoughts?
Thanks
Update - I replaced the jquery files with ones from the latest Magento 1.9 download and I'm still getting the same error when I do a security scan.
magento-1.9 supee-10975
add a comment |
We installed SUPEE 10975 a while ago and more patches since. Lately we are getting warnings that jQuery is out of date and I'm not quite sure what to do.
SUPEE-10975 - Failed.
Outdated JQuery library v.1.12.0 found (PRODSECBUG-2108), got '200'.
The patch was installed successfully. The only thing I can think of at the moment is to grab the jQuery files from the latest Magento release and manually use them to replace the files on the server
Do you guys have any thoughts?
Thanks
Update - I replaced the jquery files with ones from the latest Magento 1.9 download and I'm still getting the same error when I do a security scan.
magento-1.9 supee-10975
add a comment |
We installed SUPEE 10975 a while ago and more patches since. Lately we are getting warnings that jQuery is out of date and I'm not quite sure what to do.
SUPEE-10975 - Failed.
Outdated JQuery library v.1.12.0 found (PRODSECBUG-2108), got '200'.
The patch was installed successfully. The only thing I can think of at the moment is to grab the jQuery files from the latest Magento release and manually use them to replace the files on the server
Do you guys have any thoughts?
Thanks
Update - I replaced the jquery files with ones from the latest Magento 1.9 download and I'm still getting the same error when I do a security scan.
magento-1.9 supee-10975
We installed SUPEE 10975 a while ago and more patches since. Lately we are getting warnings that jQuery is out of date and I'm not quite sure what to do.
SUPEE-10975 - Failed.
Outdated JQuery library v.1.12.0 found (PRODSECBUG-2108), got '200'.
The patch was installed successfully. The only thing I can think of at the moment is to grab the jQuery files from the latest Magento release and manually use them to replace the files on the server
Do you guys have any thoughts?
Thanks
Update - I replaced the jquery files with ones from the latest Magento 1.9 download and I'm still getting the same error when I do a security scan.
magento-1.9 supee-10975
magento-1.9 supee-10975
edited yesterday
John Doyle
asked yesterday
John DoyleJohn Doyle
62
62
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you open your website, then in dev tools console run
console.log(jQuery.fn.jquery);
This will give you the version of the loaded jQuery library. If the output is 1.12.1
it's all fine.
If it's 1.12.0
it means that your theme is not extending rwd
theme. The patch is applied only to rwd
theme because it's the only one that includes jQuery by default. So if your custom theme doesn't extend rwd
you are including jQuery on your own. The patch doesn't know how you include it and that's why it can't patch it.
To check if your current theme is descendant of rwd
check contents of app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/etc/theme.xml
<parent>
node. Traverse back until you reach to the end of the hierarchy tree. Even if it is a descendant of rwd
it's possible that you have overridden the jQuery loading. Usually this will happen in app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/layout/page.xml
in the <default>
handle. Find the line
<action method="addJs"><script>lib/jquery/jquery-1.12.0.min.js</script></action>
and update it.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f269365%2fsupee-10975-but-still-getting-warnings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you open your website, then in dev tools console run
console.log(jQuery.fn.jquery);
This will give you the version of the loaded jQuery library. If the output is 1.12.1
it's all fine.
If it's 1.12.0
it means that your theme is not extending rwd
theme. The patch is applied only to rwd
theme because it's the only one that includes jQuery by default. So if your custom theme doesn't extend rwd
you are including jQuery on your own. The patch doesn't know how you include it and that's why it can't patch it.
To check if your current theme is descendant of rwd
check contents of app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/etc/theme.xml
<parent>
node. Traverse back until you reach to the end of the hierarchy tree. Even if it is a descendant of rwd
it's possible that you have overridden the jQuery loading. Usually this will happen in app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/layout/page.xml
in the <default>
handle. Find the line
<action method="addJs"><script>lib/jquery/jquery-1.12.0.min.js</script></action>
and update it.
New contributor
add a comment |
If you open your website, then in dev tools console run
console.log(jQuery.fn.jquery);
This will give you the version of the loaded jQuery library. If the output is 1.12.1
it's all fine.
If it's 1.12.0
it means that your theme is not extending rwd
theme. The patch is applied only to rwd
theme because it's the only one that includes jQuery by default. So if your custom theme doesn't extend rwd
you are including jQuery on your own. The patch doesn't know how you include it and that's why it can't patch it.
To check if your current theme is descendant of rwd
check contents of app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/etc/theme.xml
<parent>
node. Traverse back until you reach to the end of the hierarchy tree. Even if it is a descendant of rwd
it's possible that you have overridden the jQuery loading. Usually this will happen in app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/layout/page.xml
in the <default>
handle. Find the line
<action method="addJs"><script>lib/jquery/jquery-1.12.0.min.js</script></action>
and update it.
New contributor
add a comment |
If you open your website, then in dev tools console run
console.log(jQuery.fn.jquery);
This will give you the version of the loaded jQuery library. If the output is 1.12.1
it's all fine.
If it's 1.12.0
it means that your theme is not extending rwd
theme. The patch is applied only to rwd
theme because it's the only one that includes jQuery by default. So if your custom theme doesn't extend rwd
you are including jQuery on your own. The patch doesn't know how you include it and that's why it can't patch it.
To check if your current theme is descendant of rwd
check contents of app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/etc/theme.xml
<parent>
node. Traverse back until you reach to the end of the hierarchy tree. Even if it is a descendant of rwd
it's possible that you have overridden the jQuery loading. Usually this will happen in app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/layout/page.xml
in the <default>
handle. Find the line
<action method="addJs"><script>lib/jquery/jquery-1.12.0.min.js</script></action>
and update it.
New contributor
If you open your website, then in dev tools console run
console.log(jQuery.fn.jquery);
This will give you the version of the loaded jQuery library. If the output is 1.12.1
it's all fine.
If it's 1.12.0
it means that your theme is not extending rwd
theme. The patch is applied only to rwd
theme because it's the only one that includes jQuery by default. So if your custom theme doesn't extend rwd
you are including jQuery on your own. The patch doesn't know how you include it and that's why it can't patch it.
To check if your current theme is descendant of rwd
check contents of app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/etc/theme.xml
<parent>
node. Traverse back until you reach to the end of the hierarchy tree. Even if it is a descendant of rwd
it's possible that you have overridden the jQuery loading. Usually this will happen in app/design/frontend/{PACKAGE_NAME}/{THEME_NAME}/layout/page.xml
in the <default>
handle. Find the line
<action method="addJs"><script>lib/jquery/jquery-1.12.0.min.js</script></action>
and update it.
New contributor
New contributor
answered yesterday
Dimitar IvanovDimitar Ivanov
512
512
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f269365%2fsupee-10975-but-still-getting-warnings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown