Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially attempted to perform the upgrade via the in-engine updater; however, after numerous failures I realized that while it was prompting for an upgrade from v2.5.4 to v2.5.5, the updater was downloading the *full* v2.5.5 package (not the update package). After discovering this, I manually downloaded the v2.5.5 upgrade and extracted it over my existing install. Sidenote here: I did perform both file/folders and MYSQL backups before this step, so I can always revert if needed.
This week I discovered that I was being affected by the widespread 'Missing Save As Copy' article function. Read a bunch on that and eventually decided to upgrade to v2.5.6, which supposedly fixed the issue. This afternoon I did so, again, by extracting the update files directly over my existing install, and only after backing up MySQL and my existing files/folder.
Amazingly, the upgrade fixed the problem, but now I've noticed another issue which may or may not have been present previously: When creating a hyperlink from within an article, I am no longer able to choose anchor targets, page targets (new window, existing window, etc...), or a title. Basically anything on the 'General' tab with the exception of the link itself is non-functional. This issue may have existed the moment I upgraded to v2.5.5, but I hadn't noticed. It's definitely present under v2.5.6. Anyone run into this problem?
Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA version which displays in the footer of the main Control Panel page still shows v2.5.5. Very odd.
Again, any thoughts? I've tried to provide some thorough background info, but if anything else is needed, please ask.
Any reason why you don't use the recommended auto-update feature? If
you did that, I think you would save yourself a lot of work and it
would work correctly. Mark
On Mon, Jul 30, 2012 at 2:54 PM, bgruett <robertgru...@gmail.com> wrote:
> Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially attempted to
> perform the upgrade via the in-engine updater; however, after numerous
> failures I realized that while it was prompting for an upgrade from v2.5.4
> to v2.5.5, the updater was downloading the *full* v2.5.5 package (not the
> update package). After discovering this, I manually downloaded the v2.5.5
> upgrade and extracted it over my existing install. Sidenote here: I did
> perform both file/folders and MYSQL backups before this step, so I can
> always revert if needed.
> This week I discovered that I was being affected by the widespread 'Missing
> Save As Copy' article function. Read a bunch on that and eventually decided
> to upgrade to v2.5.6, which supposedly fixed the issue. This afternoon I
> did so, again, by extracting the update files directly over my existing
> install, and only after backing up MySQL and my existing files/folder.
> Amazingly, the upgrade fixed the problem, but now I've noticed another issue
> which may or may not have been present previously: When creating a hyperlink
> from within an article, I am no longer able to choose anchor targets, page
> targets (new window, existing window, etc...), or a title. Basically
> anything on the 'General' tab with the exception of the link itself is
> non-functional. This issue may have existed the moment I upgraded to
> v2.5.5, but I hadn't noticed. It's definitely present under v2.5.6. Anyone
> run into this problem?
> Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA version which
> displays in the footer of the main Control Panel page still shows v2.5.5.
> Very odd.
> Again, any thoughts? I've tried to provide some thorough background info,
> but if anything else is needed, please ask.
> Thanks,
> Bob
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! bug Squad" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/joomlabugsquad/-/zRWkObXKrZcJ.
> To post to this group, send email to joomlabugsquad@googlegroups.com.
> To unsubscribe from this group, send email to
> joomlabugsquad+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomlabugsquad?hl=en.
Yes. I initially tried using the in-engine update function, which up until this situation has worked well. However, in this case I could not use it for the following reasons:
- When upgrading from v2.5.4 to v2.5.5, the updater kept downloading the full v2.5.5 package, not the update package. After doing so, the install would consistently fail. Initially I did not realize that it was grabbing the wrong package, and so I tried several times to update, but each time an error ensued. When I finally took a look at the file that it was downloading I immediately realized it was the wrong packge, and therefore I manually downloaded the update package and extracted it on top of my existing install. - After upgrading to v2.5.5, the update function on the main control panel in Joomla no longer showed that an update was available, even though v2.5.6 was being advertised on the JOOMLA.ORG site. Since the updater apparently had no idea that a newer version existed, I again had to manually download the update package and extract it.
If the updater was working then yes, the update process itself would have gone much more smoothly. However, I don't know if the problems I'm seeing now would have been eliminated.
I'm thinking at this point that I will revert back to v2.5.4, since it seemed to be the last stable version of the platform, and wait this one out until I'm confident that I can upgrade without introducing problems.
On Monday, July 30, 2012 6:56:41 PM UTC-5, Mark Dexter wrote: > Any reason why you don't use the recommended auto-update feature? If > you did that, I think you would save yourself a lot of work and it > would work correctly. Mark
> On Mon, Jul 30, 2012 at 2:54 PM, bgruett wrote: > > Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially > attempted to > > perform the upgrade via the in-engine updater; however, after numerous > > failures I realized that while it was prompting for an upgrade from > v2.5.4 > > to v2.5.5, the updater was downloading the *full* v2.5.5 package (not > the > > update package). After discovering this, I manually downloaded the > v2.5.5 > > upgrade and extracted it over my existing install. Sidenote here: I did > > perform both file/folders and MYSQL backups before this step, so I can > > always revert if needed.
> > This week I discovered that I was being affected by the widespread > 'Missing > > Save As Copy' article function. Read a bunch on that and eventually > decided > > to upgrade to v2.5.6, which supposedly fixed the issue. This afternoon > I > > did so, again, by extracting the update files directly over my existing > > install, and only after backing up MySQL and my existing files/folder.
> > Amazingly, the upgrade fixed the problem, but now I've noticed another > issue > > which may or may not have been present previously: When creating a > hyperlink > > from within an article, I am no longer able to choose anchor targets, > page > > targets (new window, existing window, etc...), or a title. Basically > > anything on the 'General' tab with the exception of the link itself is > > non-functional. This issue may have existed the moment I upgraded to > > v2.5.5, but I hadn't noticed. It's definitely present under v2.5.6. > Anyone > > run into this problem?
> > Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA version > which > > displays in the footer of the main Control Panel page still shows > v2.5.5. > > Very odd.
> > Again, any thoughts? I've tried to provide some thorough background > info, > > but if anything else is needed, please ask.
Try Download the Joomla 2.5.6 full package and install as you would an extension. Then clear your Browser cash and check Joomla 'Database' and 'Discover' tabs.
On Tuesday, 31 July 2012 16:32:12 UTC+1, bgruett wrote:
> Yes. I initially tried using the in-engine update function, which up > until this situation has worked well. However, in this case I could not > use it for the following reasons:
> - When upgrading from v2.5.4 to v2.5.5, the updater kept downloading > the full v2.5.5 package, not the update package. After doing so, the > install would consistently fail. Initially I did not realize that it was > grabbing the wrong package, and so I tried several times to update, but > each time an error ensued. When I finally took a look at the file that it > was downloading I immediately realized it was the wrong packge, and > therefore I manually downloaded the update package and extracted it on top > of my existing install. > - After upgrading to v2.5.5, the update function on the main control > panel in Joomla no longer showed that an update was available, even though > v2.5.6 was being advertised on the JOOMLA.ORG site. Since the updater > apparently had no idea that a newer version existed, I again had to > manually download the update package and extract it.
> If the updater was working then yes, the update process itself would have > gone much more smoothly. However, I don't know if the problems I'm seeing > now would have been eliminated.
> I'm thinking at this point that I will revert back to v2.5.4, since it > seemed to be the last stable version of the platform, and wait this one out > until I'm confident that I can upgrade without introducing problems.
> -Bob
> On Monday, July 30, 2012 6:56:41 PM UTC-5, Mark Dexter wrote:
>> Any reason why you don't use the recommended auto-update feature? If >> you did that, I think you would save yourself a lot of work and it >> would work correctly. Mark
>> On Mon, Jul 30, 2012 at 2:54 PM, bgruett wrote: >> > Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially >> attempted to >> > perform the upgrade via the in-engine updater; however, after numerous >> > failures I realized that while it was prompting for an upgrade from >> v2.5.4 >> > to v2.5.5, the updater was downloading the *full* v2.5.5 package (not >> the >> > update package). After discovering this, I manually downloaded the >> v2.5.5 >> > upgrade and extracted it over my existing install. Sidenote here: I >> did >> > perform both file/folders and MYSQL backups before this step, so I can >> > always revert if needed.
>> > This week I discovered that I was being affected by the widespread >> 'Missing >> > Save As Copy' article function. Read a bunch on that and eventually >> decided >> > to upgrade to v2.5.6, which supposedly fixed the issue. This afternoon >> I >> > did so, again, by extracting the update files directly over my existing >> > install, and only after backing up MySQL and my existing files/folder.
>> > Amazingly, the upgrade fixed the problem, but now I've noticed another >> issue >> > which may or may not have been present previously: When creating a >> hyperlink >> > from within an article, I am no longer able to choose anchor targets, >> page >> > targets (new window, existing window, etc...), or a title. Basically >> > anything on the 'General' tab with the exception of the link itself is >> > non-functional. This issue may have existed the moment I upgraded to >> > v2.5.5, but I hadn't noticed. It's definitely present under v2.5.6. >> Anyone >> > run into this problem?
>> > Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA version >> which >> > displays in the footer of the main Control Panel page still shows >> v2.5.5. >> > Very odd.
>> > Again, any thoughts? I've tried to provide some thorough background >> info, >> > but if anything else is needed, please ask.
Unless I misunderstood your recommendation, I did download and attempt to install the full v2.5.6 package via the extension installer (browsing for a ZIP package), but this resulted in an error. Therefore I restored to my earlier v2.5.4 version of the platform for the time being - so far things look good.
On a related note, when I restored back to the v2.5.4 version of the engine I did not touch the corresponding MySQL database. To be honest I wasn't sure if I had to in this particular instance, and the upside is that I haven't lost any of the articles published after the v2.5.5 upgrade last week. Not sure if I'm asking for trouble here and if I should re-restore to v2.5.4 while also reverting to the old copy of the database, but I don't think it's necessary. Correct me if I'm wrong on this.
On Tuesday, July 31, 2012 10:52:30 AM UTC-5, Kevin wrote: > Try > Download the Joomla 2.5.6 full package and install as you would an > extension. Then clear your Browser cash and check Joomla 'Database' and > 'Discover' tabs.
> On Tuesday, 31 July 2012 16:32:12 UTC+1, bgruett wrote:
>> Yes. I initially tried using the in-engine update function, which up >> until this situation has worked well. However, in this case I could not >> use it for the following reasons:
>> - When upgrading from v2.5.4 to v2.5.5, the updater kept downloading >> the full v2.5.5 package, not the update package. After doing so, the >> install would consistently fail. Initially I did not realize that it was >> grabbing the wrong package, and so I tried several times to update, but >> each time an error ensued. When I finally took a look at the file that it >> was downloading I immediately realized it was the wrong packge, and >> therefore I manually downloaded the update package and extracted it on top >> of my existing install. >> - After upgrading to v2.5.5, the update function on the main control >> panel in Joomla no longer showed that an update was available, even though >> v2.5.6 was being advertised on the JOOMLA.ORG site. Since the >> updater apparently had no idea that a newer version existed, I again had to >> manually download the update package and extract it.
>> If the updater was working then yes, the update process itself would have >> gone much more smoothly. However, I don't know if the problems I'm seeing >> now would have been eliminated.
>> I'm thinking at this point that I will revert back to v2.5.4, since it >> seemed to be the last stable version of the platform, and wait this one out >> until I'm confident that I can upgrade without introducing problems.
>> -Bob
>> On Monday, July 30, 2012 6:56:41 PM UTC-5, Mark Dexter wrote:
>>> Any reason why you don't use the recommended auto-update feature? If >>> you did that, I think you would save yourself a lot of work and it >>> would work correctly. Mark
>>> On Mon, Jul 30, 2012 at 2:54 PM, bgruett wrote: >>> > Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially >>> attempted to >>> > perform the upgrade via the in-engine updater; however, after numerous >>> > failures I realized that while it was prompting for an upgrade from >>> v2.5.4 >>> > to v2.5.5, the updater was downloading the *full* v2.5.5 package (not >>> the >>> > update package). After discovering this, I manually downloaded the >>> v2.5.5 >>> > upgrade and extracted it over my existing install. Sidenote here: I >>> did >>> > perform both file/folders and MYSQL backups before this step, so I can >>> > always revert if needed.
>>> > This week I discovered that I was being affected by the widespread >>> 'Missing >>> > Save As Copy' article function. Read a bunch on that and eventually >>> decided >>> > to upgrade to v2.5.6, which supposedly fixed the issue. This >>> afternoon I >>> > did so, again, by extracting the update files directly over my >>> existing >>> > install, and only after backing up MySQL and my existing files/folder.
>>> > Amazingly, the upgrade fixed the problem, but now I've noticed another >>> issue >>> > which may or may not have been present previously: When creating a >>> hyperlink >>> > from within an article, I am no longer able to choose anchor targets, >>> page >>> > targets (new window, existing window, etc...), or a title. Basically >>> > anything on the 'General' tab with the exception of the link itself is >>> > non-functional. This issue may have existed the moment I upgraded to >>> > v2.5.5, but I hadn't noticed. It's definitely present under v2.5.6. >>> Anyone >>> > run into this problem?
>>> > Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA version >>> which >>> > displays in the footer of the main Control Panel page still shows >>> v2.5.5. >>> > Very odd.
>>> > Again, any thoughts? I've tried to provide some thorough background >>> info, >>> > but if anything else is needed, please ask.
On Tuesday, July 31, 2012 2:36:37 PM UTC-4, bgruett wrote:
> Unless I misunderstood your recommendation, I did download and attempt to > install the full v2.5.6 package via the extension installer (browsing for a > ZIP package), but this resulted in an error. Therefore I restored to my > earlier v2.5.4 version of the platform for the time being - so far things > look good.
> On a related note, when I restored back to the v2.5.4 version of the > engine I did not touch the corresponding MySQL database. To be honest I > wasn't sure if I had to in this particular instance, and the upside is that > I haven't lost any of the articles published after the v2.5.5 upgrade last > week. Not sure if I'm asking for trouble here and if I should re-restore > to v2.5.4 while also reverting to the old copy of the database, but I don't > think it's necessary. Correct me if I'm wrong on this.
> Thanks for the help.
> -Bob
> On Tuesday, July 31, 2012 10:52:30 AM UTC-5, Kevin wrote:
>> Try >> Download the Joomla 2.5.6 full package and install as you would an >> extension. Then clear your Browser cash and check Joomla 'Database' and >> 'Discover' tabs.
>> On Tuesday, 31 July 2012 16:32:12 UTC+1, bgruett wrote:
>>> Yes. I initially tried using the in-engine update function, which up >>> until this situation has worked well. However, in this case I could not >>> use it for the following reasons:
>>> - When upgrading from v2.5.4 to v2.5.5, the updater kept downloading >>> the full v2.5.5 package, not the update package. After doing so, the >>> install would consistently fail. Initially I did not realize that it was >>> grabbing the wrong package, and so I tried several times to update, but >>> each time an error ensued. When I finally took a look at the file that it >>> was downloading I immediately realized it was the wrong packge, and >>> therefore I manually downloaded the update package and extracted it on top >>> of my existing install. >>> - After upgrading to v2.5.5, the update function on the main control >>> panel in Joomla no longer showed that an update was available, even though >>> v2.5.6 was being advertised on the JOOMLA.ORG site. Since the >>> updater apparently had no idea that a newer version existed, I again had to >>> manually download the update package and extract it.
>>> If the updater was working then yes, the update process itself would >>> have gone much more smoothly. However, I don't know if the problems I'm >>> seeing now would have been eliminated.
>>> I'm thinking at this point that I will revert back to v2.5.4, since it >>> seemed to be the last stable version of the platform, and wait this one out >>> until I'm confident that I can upgrade without introducing problems.
>>> -Bob
>>> On Monday, July 30, 2012 6:56:41 PM UTC-5, Mark Dexter wrote:
>>>> Any reason why you don't use the recommended auto-update feature? If >>>> you did that, I think you would save yourself a lot of work and it >>>> would work correctly. Mark
>>>> On Mon, Jul 30, 2012 at 2:54 PM, bgruett wrote: >>>> > Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially >>>> attempted to >>>> > perform the upgrade via the in-engine updater; however, after >>>> numerous >>>> > failures I realized that while it was prompting for an upgrade from >>>> v2.5.4 >>>> > to v2.5.5, the updater was downloading the *full* v2.5.5 package (not >>>> the >>>> > update package). After discovering this, I manually downloaded the >>>> v2.5.5 >>>> > upgrade and extracted it over my existing install. Sidenote here: I >>>> did >>>> > perform both file/folders and MYSQL backups before this step, so I >>>> can >>>> > always revert if needed.
>>>> > This week I discovered that I was being affected by the widespread >>>> 'Missing >>>> > Save As Copy' article function. Read a bunch on that and eventually >>>> decided >>>> > to upgrade to v2.5.6, which supposedly fixed the issue. This >>>> afternoon I >>>> > did so, again, by extracting the update files directly over my >>>> existing >>>> > install, and only after backing up MySQL and my existing >>>> files/folder.
>>>> > Amazingly, the upgrade fixed the problem, but now I've noticed >>>> another issue >>>> > which may or may not have been present previously: When creating a >>>> hyperlink >>>> > from within an article, I am no longer able to choose anchor targets, >>>> page >>>> > targets (new window, existing window, etc...), or a title. Basically >>>> > anything on the 'General' tab with the exception of the link itself >>>> is >>>> > non-functional. This issue may have existed the moment I upgraded to >>>> > v2.5.5, but I hadn't noticed. It's definitely present under v2.5.6. >>>> Anyone >>>> > run into this problem?
>>>> > Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA version >>>> which >>>> > displays in the footer of the main Control Panel page still shows >>>> v2.5.5. >>>> > Very odd.
>>>> > Again, any thoughts? I've tried to provide some thorough background >>>> info, >>>> > but if anything else is needed, please ask.
I just ran through the procedure again to make sure I wasn't missing anything, and here's the overview. Keep in mind that the current version is 2.5.4.
- I log into the Joomla back end, and on the Control Panel I see the udpate icon showing the following message: 'Joomla! 2.5.5 Update now!' - Before doing anything more, I check the \tmp\ subfolder in my Joomla installation and verify that the only file in there is an index.html file. Nothing else. - I click the aforementioned update icon in the Control Panel. This takes me to the Joomla! Update page, where the following update package URL is displayed: http://joomlacode.org/gf/download/frsrelease/17174/74751/Joomla_2.5.0.... Pay special attention to the fact that despite my current version being 2.5.4, this patch is the v2.5.0-to-2.5.6 update, and despite the update button telling me that v2.5.5 was avilable, this link is clearly pointing me to a 2.5.6 package. Two oddities there, not sure if they are noteworthy or not. - I click the Install the update button the Joomla! Update page. I immediately get the following error: 'The archive file is corrupt, truncated or archive parts are missing', and at the same time, I see the file Joomla_2.5.0_to_2.5.6-Stable-Patch_Package.zip appear in the \tmp\ folder which I earlier checked.
The reason I've been assuming the updater downloads the new version is because when I tell it to install, the file mentioned above suddenly appears in the \tmp\ folder. I didn't put it there, so I'm guessing the updater is responsible for obtaining and placing it.
To help clarify, I've attached five screenshots to this post. These correspond to the points notated above. Hopefully they'll make clear what I'm trying to relay through words.
On Tuesday, July 31, 2012 2:27:08 PM UTC-5, Elin wrote: > I'm a little confused because the updater doesn't do any downloading.
> Elin
> On Tuesday, July 31, 2012 2:36:37 PM UTC-4, bgruett wrote:
>> Unless I misunderstood your recommendation, I did download and attempt to >> install the full v2.5.6 package via the extension installer (browsing for a >> ZIP package), but this resulted in an error. Therefore I restored to my >> earlier v2.5.4 version of the platform for the time being - so far things >> look good.
>> On a related note, when I restored back to the v2.5.4 version of the >> engine I did not touch the corresponding MySQL database. To be honest I >> wasn't sure if I had to in this particular instance, and the upside is that >> I haven't lost any of the articles published after the v2.5.5 upgrade last >> week. Not sure if I'm asking for trouble here and if I should re-restore >> to v2.5.4 while also reverting to the old copy of the database, but I don't >> think it's necessary. Correct me if I'm wrong on this.
>> Thanks for the help.
>> -Bob
>> On Tuesday, July 31, 2012 10:52:30 AM UTC-5, Kevin wrote:
>>> Try >>> Download the Joomla 2.5.6 full package and install as you would an >>> extension. Then clear your Browser cash and check Joomla 'Database' and >>> 'Discover' tabs.
>>> On Tuesday, 31 July 2012 16:32:12 UTC+1, bgruett wrote:
>>>> Yes. I initially tried using the in-engine update function, which up >>>> until this situation has worked well. However, in this case I could not >>>> use it for the following reasons:
>>>> - When upgrading from v2.5.4 to v2.5.5, the updater kept >>>> downloading the full v2.5.5 package, not the update package. After doing >>>> so, the install would consistently fail. Initially I did not realize that >>>> it was grabbing the wrong package, and so I tried several times to update, >>>> but each time an error ensued. When I finally took a look at the file that >>>> it was downloading I immediately realized it was the wrong packge, and >>>> therefore I manually downloaded the update package and extracted it on top >>>> of my existing install. >>>> - After upgrading to v2.5.5, the update function on the main >>>> control panel in Joomla no longer showed that an update was available, even >>>> though v2.5.6 was being advertised on the JOOMLA.ORG site. Since >>>> the updater apparently had no idea that a newer version existed, I again >>>> had to manually download the update package and extract it.
>>>> If the updater was working then yes, the update process itself would >>>> have gone much more smoothly. However, I don't know if the problems I'm >>>> seeing now would have been eliminated.
>>>> I'm thinking at this point that I will revert back to v2.5.4, since it >>>> seemed to be the last stable version of the platform, and wait this one out >>>> until I'm confident that I can upgrade without introducing problems.
>>>> -Bob
>>>> On Monday, July 30, 2012 6:56:41 PM UTC-5, Mark Dexter wrote:
>>>>> Any reason why you don't use the recommended auto-update feature? If >>>>> you did that, I think you would save yourself a lot of work and it >>>>> would work correctly. Mark
>>>>> On Mon, Jul 30, 2012 at 2:54 PM, bgruett wrote: >>>>> > Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially >>>>> attempted to >>>>> > perform the upgrade via the in-engine updater; however, after >>>>> numerous >>>>> > failures I realized that while it was prompting for an upgrade from >>>>> v2.5.4 >>>>> > to v2.5.5, the updater was downloading the *full* v2.5.5 package >>>>> (not the >>>>> > update package). After discovering this, I manually downloaded the >>>>> v2.5.5 >>>>> > upgrade and extracted it over my existing install. Sidenote here: I >>>>> did >>>>> > perform both file/folders and MYSQL backups before this step, so I >>>>> can >>>>> > always revert if needed.
>>>>> > This week I discovered that I was being affected by the widespread >>>>> 'Missing >>>>> > Save As Copy' article function. Read a bunch on that and eventually >>>>> decided >>>>> > to upgrade to v2.5.6, which supposedly fixed the issue. This >>>>> afternoon I >>>>> > did so, again, by extracting the update files directly over my >>>>> existing >>>>> > install, and only after backing up MySQL and my existing >>>>> files/folder.
>>>>> > Amazingly, the upgrade fixed the problem, but now I've noticed >>>>> another issue >>>>> > which may or may not have been present previously: When creating a >>>>> hyperlink >>>>> > from within an article, I am no longer able to choose anchor >>>>> targets, page >>>>> > targets (new window, existing window, etc...), or a title. >>>>> Basically >>>>> > anything on the 'General' tab with the exception of the link itself >>>>> is >>>>> > non-functional. This issue may have existed the moment I upgraded >>>>> to >>>>> > v2.5.5, but I hadn't noticed. It's definitely present under v2.5.6. >>>>> Anyone >>>>> > run into this problem?
>>>>> > Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA version >>>>> which >>>>> > displays in the footer of the main Control Panel page still shows >>>>> v2.5.5. >>>>> > Very odd.
>>>>> > Again, any thoughts? I've tried to provide some thorough background >>>>> info, >>>>> > but if anything else is needed, please ask.
On Tue, Jul 31, 2012 at 2:37 PM, bgruett <robertgru...@gmail.com> wrote:
> I just ran through the procedure again to make sure I wasn't missing
> anything, and here's the overview. Keep in mind that the current version is
> 2.5.4.
> I log into the Joomla back end, and on the Control Panel I see the udpate
> icon showing the following message: 'Joomla! 2.5.5 Update now!'
> Before doing anything more, I check the \tmp\ subfolder in my Joomla
> installation and verify that the only file in there is an index.html file.
> Nothing else.
> I click the aforementioned update icon in the Control Panel. This takes me
> to the Joomla! Update page, where the following update package URL is
> displayed:
> http://joomlacode.org/gf/download/frsrelease/17174/74751/Joomla_2.5.0....
> Pay special attention to the fact that despite my current version being
> 2.5.4, this patch is the v2.5.0-to-2.5.6 update, and despite the update
> button telling me that v2.5.5 was avilable, this link is clearly pointing me
> to a 2.5.6 package. Two oddities there, not sure if they are noteworthy or
> not.
> I click the Install the update button the Joomla! Update page. I
> immediately get the following error: 'The archive file is corrupt, truncated
> or archive parts are missing', and at the same time, I see the file
> Joomla_2.5.0_to_2.5.6-Stable-Patch_Package.zip appear in the \tmp\ folder
> which I earlier checked.
> The reason I've been assuming the updater downloads the new version is
> because when I tell it to install, the file mentioned above suddenly appears
> in the \tmp\ folder. I didn't put it there, so I'm guessing the updater is
> responsible for obtaining and placing it.
> To help clarify, I've attached five screenshots to this post. These
> correspond to the points notated above. Hopefully they'll make clear what
> I'm trying to relay through words.
> Thanks,
> Bob
> On Tuesday, July 31, 2012 2:27:08 PM UTC-5, Elin wrote:
>> I'm a little confused because the updater doesn't do any downloading.
>> Elin
>> On Tuesday, July 31, 2012 2:36:37 PM UTC-4, bgruett wrote:
>>> Unless I misunderstood your recommendation, I did download and attempt to
>>> install the full v2.5.6 package via the extension installer (browsing for a
>>> ZIP package), but this resulted in an error. Therefore I restored to my
>>> earlier v2.5.4 version of the platform for the time being - so far things
>>> look good.
>>> On a related note, when I restored back to the v2.5.4 version of the
>>> engine I did not touch the corresponding MySQL database. To be honest I
>>> wasn't sure if I had to in this particular instance, and the upside is that
>>> I haven't lost any of the articles published after the v2.5.5 upgrade last
>>> week. Not sure if I'm asking for trouble here and if I should re-restore to
>>> v2.5.4 while also reverting to the old copy of the database, but I don't
>>> think it's necessary. Correct me if I'm wrong on this.
>>> Thanks for the help.
>>> -Bob
>>> On Tuesday, July 31, 2012 10:52:30 AM UTC-5, Kevin wrote:
>>>> Try
>>>> Download the Joomla 2.5.6 full package and install as you would an
>>>> extension. Then clear your Browser cash and check Joomla 'Database' and
>>>> 'Discover' tabs.
>>>> On Tuesday, 31 July 2012 16:32:12 UTC+1, bgruett wrote:
>>>>> Yes. I initially tried using the in-engine update function, which up
>>>>> until this situation has worked well. However, in this case I could not use
>>>>> it for the following reasons:
>>>>> When upgrading from v2.5.4 to v2.5.5, the updater kept downloading the
>>>>> full v2.5.5 package, not the update package. After doing so, the install
>>>>> would consistently fail. Initially I did not realize that it was grabbing
>>>>> the wrong package, and so I tried several times to update, but each time an
>>>>> error ensued. When I finally took a look at the file that it was
>>>>> downloading I immediately realized it was the wrong packge, and therefore I
>>>>> manually downloaded the update package and extracted it on top of my
>>>>> existing install.
>>>>> After upgrading to v2.5.5, the update function on the main control
>>>>> panel in Joomla no longer showed that an update was available, even though
>>>>> v2.5.6 was being advertised on the JOOMLA.ORG site. Since the updater
>>>>> apparently had no idea that a newer version existed, I again had to manually
>>>>> download the update package and extract it.
>>>>> If the updater was working then yes, the update process itself would
>>>>> have gone much more smoothly. However, I don't know if the problems I'm
>>>>> seeing now would have been eliminated.
>>>>> I'm thinking at this point that I will revert back to v2.5.4, since it
>>>>> seemed to be the last stable version of the platform, and wait this one out
>>>>> until I'm confident that I can upgrade without introducing problems.
>>>>> -Bob
>>>>> On Monday, July 30, 2012 6:56:41 PM UTC-5, Mark Dexter wrote:
>>>>>> Any reason why you don't use the recommended auto-update feature? If
>>>>>> you did that, I think you would save yourself a lot of work and it
>>>>>> would work correctly. Mark
>>>>>> On Mon, Jul 30, 2012 at 2:54 PM, bgruett wrote:
>>>>>> > Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially
>>>>>> > attempted to
>>>>>> > perform the upgrade via the in-engine updater; however, after
>>>>>> > numerous
>>>>>> > failures I realized that while it was prompting for an upgrade from
>>>>>> > v2.5.4
>>>>>> > to v2.5.5, the updater was downloading the *full* v2.5.5 package
>>>>>> > (not the
>>>>>> > update package). After discovering this, I manually downloaded the
>>>>>> > v2.5.5
>>>>>> > upgrade and extracted it over my existing install. Sidenote here: I
>>>>>> > did
>>>>>> > perform both file/folders and MYSQL backups before this step, so I
>>>>>> > can
>>>>>> > always revert if needed.
>>>>>> > This week I discovered that I was being affected by the widespread
>>>>>> > 'Missing
>>>>>> > Save As Copy' article function. Read a bunch on that and eventually
>>>>>> > decided
>>>>>> > to upgrade to v2.5.6, which supposedly fixed the issue. This
>>>>>> > afternoon I
>>>>>> > did so, again, by extracting the update files directly over my
>>>>>> > existing
>>>>>> > install, and only after backing up MySQL and my existing
>>>>>> > files/folder.
>>>>>> > Amazingly, the upgrade fixed the problem, but now I've noticed
>>>>>> > another issue
>>>>>> > which may or may not have been present previously: When creating a
>>>>>> > hyperlink
>>>>>> > from within an article, I am no longer able to choose anchor
>>>>>> > targets, page
>>>>>> > targets (new window, existing window, etc...), or a title.
>>>>>> > Basically
>>>>>> > anything on the 'General' tab with the exception of the link itself
>>>>>> > is
>>>>>> > non-functional. This issue may have existed the moment I upgraded
>>>>>> > to
>>>>>> > v2.5.5, but I hadn't noticed. It's definitely present under v2.5.6.
>>>>>> > Anyone
>>>>>> > run into this problem?
>>>>>> > Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA version
>>>>>> > which
>>>>>> > displays in the footer of the main Control Panel page still shows
>>>>>> > v2.5.5.
>>>>>> > Very odd.
>>>>>> > Again, any thoughts? I've tried to provide some thorough background
>>>>>> > info,
>>>>>> > but if anything else is needed, please ask.
>>>>>> > Thanks,
>>>>>> > Bob
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! bug Squad" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/joomlabugsquad/-/kG1F8JWpWD0J.
> To post to this group, send email to joomlabugsquad@googlegroups.com.
> To unsubscribe from this group, send email to
> joomlabugsquad+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomlabugsquad?hl=en.
On Tuesday, July 31, 2012 5:42:38 PM UTC-4, Mark Dexter wrote:
> You should be seeing 2.5.6, not 2.5.5. I wonder if that is part of the > problem? Mark
> On Tue, Jul 31, 2012 at 2:37 PM, bgruett <robertgru...@gmail.com> wrote: > > I just ran through the procedure again to make sure I wasn't missing > > anything, and here's the overview. Keep in mind that the current > version is > > 2.5.4.
> > I log into the Joomla back end, and on the Control Panel I see the > udpate > > icon showing the following message: 'Joomla! 2.5.5 Update now!' > > Before doing anything more, I check the \tmp\ subfolder in my Joomla > > installation and verify that the only file in there is an index.html > file. > > Nothing else. > > I click the aforementioned update icon in the Control Panel. This takes > me > > to the Joomla! Update page, where the following update package URL is > > displayed:
> > Pay special attention to the fact that despite my current version being > > 2.5.4, this patch is the v2.5.0-to-2.5.6 update, and despite the update > > button telling me that v2.5.5 was avilable, this link is clearly > pointing me > > to a 2.5.6 package. Two oddities there, not sure if they are noteworthy > or > > not. > > I click the Install the update button the Joomla! Update page. I > > immediately get the following error: 'The archive file is corrupt, > truncated > > or archive parts are missing', and at the same time, I see the file > > Joomla_2.5.0_to_2.5.6-Stable-Patch_Package.zip appear in the \tmp\ > folder > > which I earlier checked.
> > The reason I've been assuming the updater downloads the new version is > > because when I tell it to install, the file mentioned above suddenly > appears > > in the \tmp\ folder. I didn't put it there, so I'm guessing the updater > is > > responsible for obtaining and placing it.
> > To help clarify, I've attached five screenshots to this post. These > > correspond to the points notated above. Hopefully they'll make clear > what > > I'm trying to relay through words.
> > Thanks, > > Bob
> > On Tuesday, July 31, 2012 2:27:08 PM UTC-5, Elin wrote:
> >> I'm a little confused because the updater doesn't do any downloading.
> >> Elin
> >> On Tuesday, July 31, 2012 2:36:37 PM UTC-4, bgruett wrote:
> >>> Unless I misunderstood your recommendation, I did download and attempt > to > >>> install the full v2.5.6 package via the extension installer (browsing > for a > >>> ZIP package), but this resulted in an error. Therefore I restored to > my > >>> earlier v2.5.4 version of the platform for the time being - so far > things > >>> look good.
> >>> On a related note, when I restored back to the v2.5.4 version of the > >>> engine I did not touch the corresponding MySQL database. To be honest > I > >>> wasn't sure if I had to in this particular instance, and the upside is > that > >>> I haven't lost any of the articles published after the v2.5.5 upgrade > last > >>> week. Not sure if I'm asking for trouble here and if I should > re-restore to > >>> v2.5.4 while also reverting to the old copy of the database, but I > don't > >>> think it's necessary. Correct me if I'm wrong on this.
> >>> Thanks for the help.
> >>> -Bob
> >>> On Tuesday, July 31, 2012 10:52:30 AM UTC-5, Kevin wrote:
> >>>> Try > >>>> Download the Joomla 2.5.6 full package and install as you would an > >>>> extension. Then clear your Browser cash and check Joomla 'Database' > and > >>>> 'Discover' tabs.
> >>>> On Tuesday, 31 July 2012 16:32:12 UTC+1, bgruett wrote:
> >>>>> Yes. I initially tried using the in-engine update function, which > up > >>>>> until this situation has worked well. However, in this case I could > not use > >>>>> it for the following reasons:
> >>>>> When upgrading from v2.5.4 to v2.5.5, the updater kept downloading > the > >>>>> full v2.5.5 package, not the update package. After doing so, the > install > >>>>> would consistently fail. Initially I did not realize that it was > grabbing > >>>>> the wrong package, and so I tried several times to update, but each > time an > >>>>> error ensued. When I finally took a look at the file that it was > >>>>> downloading I immediately realized it was the wrong packge, and > therefore I > >>>>> manually downloaded the update package and extracted it on top of my > >>>>> existing install. > >>>>> After upgrading to v2.5.5, the update function on the main control > >>>>> panel in Joomla no longer showed that an update was available, even > though > >>>>> v2.5.6 was being advertised on the JOOMLA.ORG site. Since the > updater > >>>>> apparently had no idea that a newer version existed, I again had to > manually > >>>>> download the update package and extract it.
> >>>>> If the updater was working then yes, the update process itself would > >>>>> have gone much more smoothly. However, I don't know if the problems > I'm > >>>>> seeing now would have been eliminated.
> >>>>> I'm thinking at this point that I will revert back to v2.5.4, since > it > >>>>> seemed to be the last stable version of the platform, and wait this > one out > >>>>> until I'm confident that I can upgrade without introducing problems.
> >>>>> -Bob
> >>>>> On Monday, July 30, 2012 6:56:41 PM UTC-5, Mark Dexter wrote:
> >>>>>> Any reason why you don't use the recommended auto-update feature? > If > >>>>>> you did that, I think you would save yourself a lot of work and it > >>>>>> would work correctly. Mark
> >>>>>> On Mon, Jul 30, 2012 at 2:54 PM, bgruett wrote: > >>>>>> > Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially > >>>>>> > attempted to > >>>>>> > perform the upgrade via the in-engine updater; however, after > >>>>>> > numerous > >>>>>> > failures I realized that while it was prompting for an upgrade > from > >>>>>> > v2.5.4 > >>>>>> > to v2.5.5, the updater was downloading the *full* v2.5.5 package > >>>>>> > (not the > >>>>>> > update package). After discovering this, I manually downloaded > the > >>>>>> > v2.5.5 > >>>>>> > upgrade and extracted it over my existing install. Sidenote > here: I > >>>>>> > did > >>>>>> > perform both file/folders and MYSQL backups before this step, so > I > >>>>>> > can > >>>>>> > always revert if needed.
> >>>>>> > This week I discovered that I was being affected by the > widespread > >>>>>> > 'Missing > >>>>>> > Save As Copy' article function. Read a bunch on that and > eventually > >>>>>> > decided > >>>>>> > to upgrade to v2.5.6, which supposedly fixed the issue. This > >>>>>> > afternoon I > >>>>>> > did so, again, by extracting the update files directly over my > >>>>>> > existing > >>>>>> > install, and only after backing up MySQL and my existing > >>>>>> > files/folder.
> >>>>>> > Amazingly, the upgrade fixed the problem, but now I've noticed > >>>>>> > another issue > >>>>>> > which may or may not have been present previously: When creating > a > >>>>>> > hyperlink > >>>>>> > from within an article, I am no longer able to choose anchor > >>>>>> > targets, page > >>>>>> > targets (new window, existing window, etc...), or a title. > >>>>>> > Basically > >>>>>> > anything on the 'General' tab with the exception of the link > itself > >>>>>> > is > >>>>>> > non-functional. This issue may have existed the moment I > upgraded > >>>>>> > to > >>>>>> > v2.5.5, but I hadn't noticed. It's definitely present under > v2.5.6. > >>>>>> > Anyone > >>>>>> > run into this problem?
> >>>>>> > Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA > version > >>>>>> > which > >>>>>> > displays in the footer of the main Control Panel page still shows > >>>>>> > v2.5.5. > >>>>>> > Very odd.
> >>>>>> > Again, any thoughts? I've tried to provide some thorough > background > >>>>>> > info, > >>>>>> > but if anything else is needed, please ask.
> >>>>>> > Thanks, > >>>>>> > Bob
> > -- > > You received this message because you are subscribed to the Google > Groups > > "Joomla! bug Squad" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/joomlabugsquad/-/kG1F8JWpWD0J. > > To post to this group, send email to joomlabugsquad@googlegroups.com. > > To unsubscribe from this group, send email to > > joomlabugsquad+unsubscribe@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/joomlabugsquad?hl=en.
On Tuesday, July 31, 2012 5:08:36 PM UTC-5, Elin wrote:
> Right it is server to server not a download in the sense we usually mean > (server to desktop).
> Do you have caching on?
> Elin > On Tuesday, July 31, 2012 5:42:38 PM UTC-4, Mark Dexter wrote:
>> You should be seeing 2.5.6, not 2.5.5. I wonder if that is part of the >> problem? Mark
>> On Tue, Jul 31, 2012 at 2:37 PM, bgruett wrote: >> > I just ran through the procedure again to make sure I wasn't missing >> > anything, and here's the overview. Keep in mind that the current >> version is >> > 2.5.4.
>> > I log into the Joomla back end, and on the Control Panel I see the >> udpate >> > icon showing the following message: 'Joomla! 2.5.5 Update now!' >> > Before doing anything more, I check the \tmp\ subfolder in my Joomla >> > installation and verify that the only file in there is an index.html >> file. >> > Nothing else. >> > I click the aforementioned update icon in the Control Panel. This >> takes me >> > to the Joomla! Update page, where the following update package URL is >> > displayed:
>> > Pay special attention to the fact that despite my current version being >> > 2.5.4, this patch is the v2.5.0-to-2.5.6 update, and despite the update >> > button telling me that v2.5.5 was avilable, this link is clearly >> pointing me >> > to a 2.5.6 package. Two oddities there, not sure if they are >> noteworthy or >> > not. >> > I click the Install the update button the Joomla! Update page. I >> > immediately get the following error: 'The archive file is corrupt, >> truncated >> > or archive parts are missing', and at the same time, I see the file >> > Joomla_2.5.0_to_2.5.6-Stable-Patch_Package.zip appear in the \tmp\ >> folder >> > which I earlier checked.
>> > The reason I've been assuming the updater downloads the new version is >> > because when I tell it to install, the file mentioned above suddenly >> appears >> > in the \tmp\ folder. I didn't put it there, so I'm guessing the >> updater is >> > responsible for obtaining and placing it.
>> > To help clarify, I've attached five screenshots to this post. These >> > correspond to the points notated above. Hopefully they'll make clear >> what >> > I'm trying to relay through words.
>> > Thanks, >> > Bob
>> > On Tuesday, July 31, 2012 2:27:08 PM UTC-5, Elin wrote:
>> >> I'm a little confused because the updater doesn't do any downloading.
>> >> Elin
>> >> On Tuesday, July 31, 2012 2:36:37 PM UTC-4, bgruett wrote:
>> >>> Unless I misunderstood your recommendation, I did download and >> attempt to >> >>> install the full v2.5.6 package via the extension installer (browsing >> for a >> >>> ZIP package), but this resulted in an error. Therefore I restored >> to my >> >>> earlier v2.5.4 version of the platform for the time being - so far >> things >> >>> look good.
>> >>> On a related note, when I restored back to the v2.5.4 version of the >> >>> engine I did not touch the corresponding MySQL database. To be >> honest I >> >>> wasn't sure if I had to in this particular instance, and the upside >> is that >> >>> I haven't lost any of the articles published after the v2.5.5 upgrade >> last >> >>> week. Not sure if I'm asking for trouble here and if I should >> re-restore to >> >>> v2.5.4 while also reverting to the old copy of the database, but I >> don't >> >>> think it's necessary. Correct me if I'm wrong on this.
>> >>> Thanks for the help.
>> >>> -Bob
>> >>> On Tuesday, July 31, 2012 10:52:30 AM UTC-5, Kevin wrote:
>> >>>> Try >> >>>> Download the Joomla 2.5.6 full package and install as you would an >> >>>> extension. Then clear your Browser cash and check Joomla 'Database' >> and >> >>>> 'Discover' tabs.
>> >>>> On Tuesday, 31 July 2012 16:32:12 UTC+1, bgruett wrote:
>> >>>>> Yes. I initially tried using the in-engine update function, which >> up >> >>>>> until this situation has worked well. However, in this case I >> could not use >> >>>>> it for the following reasons:
>> >>>>> When upgrading from v2.5.4 to v2.5.5, the updater kept downloading >> the >> >>>>> full v2.5.5 package, not the update package. After doing so, the >> install >> >>>>> would consistently fail. Initially I did not realize that it was >> grabbing >> >>>>> the wrong package, and so I tried several times to update, but each >> time an >> >>>>> error ensued. When I finally took a look at the file that it was >> >>>>> downloading I immediately realized it was the wrong packge, and >> therefore I >> >>>>> manually downloaded the update package and extracted it on top of >> my >> >>>>> existing install. >> >>>>> After upgrading to v2.5.5, the update function on the main control >> >>>>> panel in Joomla no longer showed that an update was available, even >> though >> >>>>> v2.5.6 was being advertised on the JOOMLA.ORG site. Since the >> updater >> >>>>> apparently had no idea that a newer version existed, I again had to >> manually >> >>>>> download the update package and extract it.
>> >>>>> If the updater was working then yes, the update process itself >> would >> >>>>> have gone much more smoothly. However, I don't know if the >> problems I'm >> >>>>> seeing now would have been eliminated.
>> >>>>> I'm thinking at this point that I will revert back to v2.5.4, since >> it >> >>>>> seemed to be the last stable version of the platform, and wait this >> one out >> >>>>> until I'm confident that I can upgrade without introducing >> problems.
>> >>>>> -Bob
>> >>>>> On Monday, July 30, 2012 6:56:41 PM UTC-5, Mark Dexter wrote:
>> >>>>>> Any reason why you don't use the recommended auto-update feature? >> If >> >>>>>> you did that, I think you would save yourself a lot of work and it >> >>>>>> would work correctly. Mark
>> >>>>>> On Mon, Jul 30, 2012 at 2:54 PM, bgruett wrote: >> >>>>>> > Last week I upgarded from Joomla v2.5.4 to v2.5.5. I initially >> >>>>>> > attempted to >> >>>>>> > perform the upgrade via the in-engine updater; however, after >> >>>>>> > numerous >> >>>>>> > failures I realized that while it was prompting for an upgrade >> from >> >>>>>> > v2.5.4 >> >>>>>> > to v2.5.5, the updater was downloading the *full* v2.5.5 package >> >>>>>> > (not the >> >>>>>> > update package). After discovering this, I manually downloaded >> the >> >>>>>> > v2.5.5 >> >>>>>> > upgrade and extracted it over my existing install. Sidenote >> here: I >> >>>>>> > did >> >>>>>> > perform both file/folders and MYSQL backups before this step, so >> I >> >>>>>> > can >> >>>>>> > always revert if needed.
>> >>>>>> > This week I discovered that I was being affected by the >> widespread >> >>>>>> > 'Missing >> >>>>>> > Save As Copy' article function. Read a bunch on that and >> eventually >> >>>>>> > decided >> >>>>>> > to upgrade to v2.5.6, which supposedly fixed the issue. This >> >>>>>> > afternoon I >> >>>>>> > did so, again, by extracting the update files directly over my >> >>>>>> > existing >> >>>>>> > install, and only after backing up MySQL and my existing >> >>>>>> > files/folder.
>> >>>>>> > Amazingly, the upgrade fixed the problem, but now I've noticed >> >>>>>> > another issue >> >>>>>> > which may or may not have been present previously: When creating >> a >> >>>>>> > hyperlink >> >>>>>> > from within an article, I am no longer able to choose anchor >> >>>>>> > targets, page >> >>>>>> > targets (new window, existing window, etc...), or a title. >> >>>>>> > Basically >> >>>>>> > anything on the 'General' tab with the exception of the link >> itself >> >>>>>> > is >> >>>>>> > non-functional. This issue may have existed the moment I >> upgraded >> >>>>>> > to >> >>>>>> > v2.5.5, but I hadn't noticed. It's definitely present under >> v2.5.6. >> >>>>>> > Anyone >> >>>>>> > run into this problem?
>> >>>>>> > Oh, one more thing: despite my upgrade to v2.5.6, the JOOMLA >> version >> >>>>>> > which >> >>>>>> > displays in the footer of the main Control Panel page still >> shows >> >>>>>> > v2.5.5. >> >>>>>> > Very odd.
>> >>>>>> > Again, any thoughts? I've tried to provide some thorough >> background >> >>>>>> > info, >> >>>>>> > but if anything else is needed, please ask.
>> >>>>>> > Thanks, >> >>>>>> > Bob
>> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "Joomla! bug Squad" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/joomlabugsquad/-/kG1F8JWpWD0J. >> > To post to this group, send email to joomlabugsquad@googlegroups.com. >> > To unsubscribe from this group, send email to >> > joomlabugsquad+unsubscribe@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/joomlabugsquad?hl=en.
