Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with supee-6788
Search options not deleted
user 3744
SUPEE-6788 is a security patch released for Magento CE <= 1.9.2.1 / EE <= 1.14.2.1
0
votes
Accepted
I could not see the pages which I had created using CMS after Updating the security Patch
Blocks and custom variables now need to be added to a whitelist. You'll need to login to the admin panel and go to System > Permissions > Variables and add any custom variables used by your block to …
- 2,047
4
votes
Accepted
SUPEE-6788 Patch can't be applied/reverted successfully
Try the solution posted on this answer. The patch is sensitive to changes in .htaccess files, and also requires all previous security patches to have been applied.
- 2,047
1
vote
Have problem to display blocks after applied SUPEE-6788 ,
The blocks likely use non-standard variables, which will need to be added to the whitelist. See this answer for steps on doing so.
- 2,047
1
vote
SUPEE6788 APPSEC-1063 SQL Injection
The (very helpful) supee-6788-toolbox performs something to this effect. It looks like the regex that they're using is:
'/addFieldToFilter\(\s*[\'"]?[\`\(]/i'
Although it does have a disclaimer th …
- 2,047
4
votes
Accepted
Tables permission_block and permission_variable did not get created after SUPEE-6788
The tables should be created as part of the upgrade of Mage_Admin from version 1.6.1.1 to 1.6.1.2. You can verify that the setup/upgrade scripts succeeded by checking the version and data_version fie …
- 2,047
0
votes
Magento 1.9.1.0 patch SUPEE-6788 1 out of 1 hunk ignored missing .htaccess.sample
The error indicates that it failed to patch .htaccess.sample:
patching file .htaccess
Hunk #1 succeeded at 228 (offset 21 lines).
can't find file to patch at input line 38
Perhaps you used the wrong …
- 2,047
15
votes
Accepted
Why does PATCH_SUPEE-6788 appear to have no effect on a 1.7.0.2 installation?
It appears that changes to my .htaccess as well as a missing .htaccess.sample are the culprit. After restoring a stock copy of both files (both were required) the patch appears to apply successfully. …
- 2,047
1
vote
Patch SUPEE-6788 and catalog/navigation blocks
The block likely uses a non-standard variable, which will need to be added to the whitelist. See this answer for steps on doing so.
- 2,047
21
votes
5
answers
15k
views
Why does PATCH_SUPEE-6788 appear to have no effect on a 1.7.0.2 installation?
Note: This issue appears to apply to all versions of Magento which received the SUPEE-6788 patch. You'll see in my answer that both .htaccess and .htaccess.sample need to be restored for the patch t …
- 2,047