I got this error when I tried to install the path PATCH_SUPEE-1533.
I have magento 1.9.1.0
sh PATCH_SUPEE-1533_EE_1.13.x_v1-2015-02-10-08-18-32.sh
PATCH_SUPEE-1533_EE_1.13.x_v1-2015-02-10-08-18-32.sh: 24: 127: not found
PATCH_SUPEE-1533_EE_1.13.x_v1-2015-02-10-08-18-32.sh: 24: 127: not found
PATCH_SUPEE-1533_EE_1.13.x_v1-2015-02-10-08-18-32.sh: 29: 0: not found
Checking if patch can be applied/reverted successfully...
-e ERROR: Patch can't be applied/reverted successfully.
patching file app/code/core/Mage/Adminhtml/Block/Dashboard/Graph.php
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file app/code/core/Mage/Adminhtml/Block/Dashboard/Graph.php.rej
patching file app/code/core/Mage/Adminhtml/controllers/DashboardController.php
thanks
The security patch SUPEE-1533 is already there in magento 1.9.1.0.
Check the two files the patch applies to:
app/code/core/Mage/Adminhtml/Block/Dashboard/Graph.php
app/code/core/Mage/Adminhtml/controllers/DashboardController.php
Search for serialize in both of those. If you find serialize or unserialize, you need to manually apply the fix.
Refer to lines 171, 172 in the patch file for Graph.php and 184,185,186 for DashboardController.php
Related
I have a problem with this command : php bin/console server:run on Symfony 4
When I go to http://127.0.0.1:8000/ I have this error message :
Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0
Fatal error: Unknown: Failed opening required 'J:\my_project\vendor\symfony\web-server-bundle/Resources/router.php' (include_path='.;C:\php\pear') in Unknown on line 0
Indeed, the router.php file does not exist !
But if I run this command : php -S 127.0.0.1:8000 -t public everything is ok.
Any idea ?
First check that you have installed the SF4 Web Server bundle :
> composer require server --dev
then you can start using it through Symfony using run / start command
Not sure if this is the case for you too, but it is probably worth checking (and may also be interesting for others having the same problem).
My antivirus software likes to put the router.php in quarantine (effectively removing it from that directory). Check if yours did the same and if so restore it and create an exception for that file. Additionally you should configure your antivirus to notify you if it puts something in quarantine, so you can intervene in time.
I've got a couple of problems with git am. I had a patch made from git format-patch and it usually worked nicely.
Now I just merged a couple of things and git am failed with:
Applying: Improve speed of computes
error: patch failed: product_cost_incl_bom/models/product_product.py:38
error: product_cost_incl_bom/models/product_product.py: patch does not apply
Then how do I know why the patch doesn't apply...Now the weird thing is this:
I then did this:
$: patch -p1 .git/rebase-apply/patch
patching file product_cost_incl_bom/__openerp__.py
patching file product_cost_incl_bom/models/mrp_bom.py
patching file product_cost_incl_bom/models/product_product.py
Hunk #2 succeeded at 39 with fuzz 1
So why does git am fails but patch doesn't. And what's the fuzz 1?
I am setting up a phabricator server and i am observing the below issue, both from my diffusion repository Status window and the daemons.log file
Error updating working copy: Command failed with error #128!
COMMAND
git log --format='%H%x01%P%x01%ct' --all --
STDOUT
(empty)
STDRR
fatal: bad default revision 'HEAD'
After reading on this issue, i figured out that this is a common issue with bare repositories without first commits. So i tried committing from my local system through repository http URI, but it is returning a 500 exception.
below is the error message i pulled out from phabricator database:
$ select * from phabricator_repository.repository_pullevent;
500 | {"response.message":"Error 1: sudo: a password is required\n"}
Can any one help me out to understand the issues from repository_pullevents and daemons.log file.
thanks in advance!
i resolved the problem with sudo, by changing the user running apache and adding the symlink created for git-http-backened in sudoers for the apache user.
and the problem with repository bad HEAD revision was resolved by making the first commit from a client machine.
Just did a chef-solo run. I have my cookbook defined in ~/chef-repo/cookbooks/my-cookbook, and all the dependencies were installed by berkshelf in ~/.berkshelf/cookbooks
chef-solo -c solo.rb -j params.json
I keep running into an error from ohai. I gather that ohai is a library that provides environment configurations, and my nginx-2.7.6 cookbook relies on ohai (2.0.1).
[2015-06-25T15:19:08-04:00] DEBUG: RuntimeError: remote_directory[/etc/chef/ohai_plugins for cookbook ohai] (ohai::default line 33) had an error: RuntimeError: cookbook_file[/etc/chef/ohai_plugins/README] (dynamically defined) had an error: RuntimeError: File files/default/plugins/README does not exist for cookbook ohai
I've looked into /etc/chef/ohai and it's right that there's no README there (that folder is empty, in fact). Not sure what it's looking for or how to solve this error.
Thanks!
According to ohai's supermarket readme it must be the first item on your runlist
https://supermarket.chef.io/cookbooks/ohai#readme
Give that a shot and see if it works.
While I am trying to update security patches I got following error message.
Checking if patch can be applied/reverted successfully...
ERROR: Patch can't be applied/reverted successfully.
patching file app/code/core/Mage/Admin/Model/Observer.php
Hunk #1 FAILED at 37.
Hunk #2 FAILED at 44.
Hunk #3 FAILED at 55.
3 out of 3 hunks FAILED -- saving rejects to file app/code/core/Mage/Admin/Model/Observer.php.rej
patching file app/code/core/Mage/Core/Controller/Request/Http.php
Hunk #1 succeeded at 39 with fuzz 1 (offset 1 line).
Hunk #2 succeeded at 537 (offset 1 line).
patching file lib/Varien/Data/Collection/Db.php
Hunk #1 FAILED at 442.
1 out of 1 hunk FAILED -- saving rejects to file lib/Varien/Data/Collection/Db.php.rej
How can I update patches in this regard ??
Do you have any custom changes in those core files? The problem is either that or version missmatch with the patch file. A solution could be to manually apply the patch to the file by opening up the PATCH.xxxxx-xxxxx.sh file and look at the file paths and line numbers to compare and see where the added/changes lines should go (+ in front) and which lines should be deleted (- in front).