-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
c7c6f89
commit 459a532
Showing
1 changed file
with
32 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
Update Module in Magento 1 Manually | ||
========================================================== | ||
|
||
.. role:: step | ||
|
||
.. role:: mail | ||
|
||
.. role:: remark | ||
|
||
**Update module via FTP** | ||
Extract module’s file, place this file into code folder of Magento site: | ||
|
||
.. image:: images/update-module-m1.PNG | ||
|
||
Log into backend, flush Magento cache and check the module function after updating. | ||
In case you want to completely uninstall the old module before updating, follow these steps: | ||
|
||
**Step 1**: To disable module, edit this file | ||
|
||
/app/etc/modules/<your_module>.xml; | ||
|
||
Replace <active>true</active> by <active>false</active>; | ||
|
||
**Step 2**: Delete all mysql tables created by the module | ||
|
||
**Step 3**: Delete the module in the core_recourse table | ||
|
||
**Step 4**: Delete files in the <project_root>/var/cache folder | ||
|
||
**Step 5**: Refresh Magento site and the module has been removed successfully | ||
|
||
Then put the code of the module to site’s folder via ftp as mentioned above and flush Magento cache |