Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Need a _patch_ package for ver. 1.7.4 -- Have a buggy 1.7.3 version
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Paul D. Bain  
View profile  
 More options Sep 13 2012, 2:05 pm
From: "Paul D. Bain" <paulb...@pobox.com>
Date: Thu, 13 Sep 2012 14:06:36 -0400
Local: Thurs, Sep 13 2012 2:06 pm
Subject: Need a _patch_ package for ver. 1.7.4 -- Have a buggy 1.7.3 version
        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?

Sincerely,
Paul Bain

======================================
        DETAILED EXPLANATION
======================================

        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
I installed.

        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:

        elinw-joomla-cms-1.7.3-82.zip

I downloaded that file from Github, _not_ JoomlaCode.org:

        Github.com/elinw/joomla-cms/downloads/

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?

==========
ADDENDUM:
==========

        Here are some of the resources that I have used when troubleshooting
this migration:

A)  docs.joomla.org/Upgrading_from_Joomla_1.7_to_Joomla_2.5

B)  http://forum.joomla.org/viewtopic.php?f=625&t=691030

C)  http://brian.teeman.net/joomla/774-upgrading-to-joomla-2-5-some-warnings

D)
http://www.linkedin.com/groups/Has-anyone-had-good-luck-52867.S.13459...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Elin Waring  
View profile  
 More options Sep 13 2012, 2:27 pm
From: Elin Waring <elin.war...@gmail.com>
Date: Thu, 13 Sep 2012 11:27:24 -0700 (PDT)
Local: Thurs, Sep 13 2012 2:27 pm
Subject: Re: Need a _patch_ package for ver. 1.7.4 -- Have a buggy 1.7.3 version

For sure that was buggy and included many potential features we were
testing for consideration for includion not all of which got included. You
may well have database modifications that we not made to the core in the
end.

If you main problem is global configuration I would not see that as a
reason not to update ... still it seem to me that the issue of the global
config probably relates to the changes in the filter options which were
moved to global config in 2.5.

You probably need to go to the database tab and click on fix and you may
need to just open and save the configuration once. Can you post a screen
shot if doing those two things does not work?

Elin


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Elin Waring  
View profile  
 More options Sep 13 2012, 2:30 pm
From: Elin Waring <elin.war...@gmail.com>
Date: Thu, 13 Sep 2012 11:30:35 -0700 (PDT)
Local: Thurs, Sep 13 2012 2:30 pm
Subject: Re: Need a _patch_ package for ver. 1.7.4 -- Have a buggy 1.7.3 version

Hi Paul,

Please pick only the one most appropriate list to post to ... the platform
list is definitely NOT appropriate for this question.

Sorry everyone that I didn't realize about the ccs until after I posted.

Elin


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions Older topic »