I think that I probably need a patch package for ver. 1.7.4, a package
that could be used to upgrade a _buggy_ version of 1.7.3 to a
_production_ version of 1.7.4. Why? Because I cannot migrate my 1.7.3
installation to version 2.5.x. The migration to version 2.5 succeeds
only half-way. For a further explanation of my situation, please see the
section "Detailed Explanation" below.
Would anyone still have such a patch package for 1.7.4? Or is my
request too late?
I currently have ver. 1.7.3 installed on my Xampp stack on my laptop
computer, and am having great difficulty in migrating this installation
to ver. 2.5.x. I have tried migrating thrice, failing each time.
The migration succeeds, but only half-way. When the migration to 2.5.x
is complete, everything in J. works _except_ for the global
configuration (GC) section of the administrative back-end. The GC page
is completely screwed up, and I cannot change anything in the GC
section. The GC section is of no use to me whatsoever. I am able to
confirm that I have migrated to ver. 2.5.x by using Extension Manager to
view the version of the database (e.g., 2.5.6). In other words, the
version is being upgraded from 1.7.3 to 2.5.6 notwithstanding that GC
does not work at all.
Let me emphasize: The migration to 2.5 succeeds _except_ for the GC section.
I do not think that this failure is due to a lack of knowledge or
research on my part. I have researched this matter thoroughly over the
last eight weeks, and have done considerable troubleshooting during that
time (See the Addendum, below). Rather, I am now beginning to suspect
that the most likely cause of my difficulty is the version of 1.7.3 that
Apparently, I did _not_ install a stable, production version of 1.7.3.
I attended the "Pizza-&-Bug-Squashing" event on 10 Dec. 2011 (in
Washington, D.C.), where the organizer of the D.C. bug-squashing event,
Ryan Ozimek (then-President of OSM), directed me to install _this_ file:
I downloaded that file from Github, _not_ JoomlaCode.org:
I now suspect that my difficulties arise from my use of this version of
1.7.3, which was probably _buggy_ -- Hence, the use of this version at
the bug-squashing event. Is there any way to confirm this suspicion?
Let us assume that my version of 1.7.3 is buggy and also the cause of
my difficulties. Is there any way for me to upgrade my 1.7.3 to a
_stable_ version of, say, 1.7.4, so as to maximize the likelihood that I
could easily migrate to ver. 2.5.x?
Here are some of the resources that I have used when troubleshooting