php - Joomla 1.7.0 Security fixes (Upgrade) -
i have shopping cart platform joomla 1.7.0 , vm2.0.6.is there option update versions manually (like files , db tables).i can't upgrade normal joomla upgrade bcoz version customized .so 1 can advise how security issues on joomla 1.7.0 fix ? manual files updates ?
any response valuable recourse appreciate.
thanks in advance.
you need find hacked files, , apply hacks new version of joomla.
the procedure quite long.
- identify exact joomla version using i.e. 1.7.3
- download new copy
make backup of entire joomla site + database (you never know)
tar czf ../joomcustom17.tgz *
put project under versioning: either svn or git do, i'll write example git:
git init git add * git commit -m "initial"
extract new copy of joomla on it:
tar xzvf ../joomla_1_7_3.tgz
and commit again
git add * git commit -m "base 1.7.3"
now have basic 1.7.3 version files added it. want diff original installation, create , checkout branch , name core17, extract initial backup on it, , commit again: contain core changes.
git checkout -b core17 tar xzf ../joomcustom17.tgz git commit -m "customised 1.7.3"
now have standard joomla 1.7.3 installation several files in master branch, , core hacks in core17 branch.
> git diff master..core17 and presented core changes.
you might want use high level tool view diffs quickly. see link below.
you absolutely need document these changes. these called "core hacks" , bad practice . absolutely need keep list explaining why applied future reference. great moment find out if can replace template overrides (in case views); see if can obtain same functionality plugin or maybe overriding core class.
once have nice picture of core changes, you're ready proceed further. it's time update joomla, switch master branch, update joomla latest version, commit. merge master, solve conflicts, , might have updated version core hacks.
it's keep core hacks separate branch next time need update easy 1,1,2,3,5,8,13.
be sure make backups , commits proceed wrong command or right command on wrong branch , can start on scratch.
document work proceed. references you:
http://git-scm.com/book/en/git-branching-basic-branching-and-merging
git visual diff between branches
hope helps... it's not difficult it's annoyingly long. remember: it's fault, , price pay hacking core.
Comments
Post a Comment