Joomla! bug Squad Google Group

Re: [jbs] Re: Auto Update and GoDaddy.com

dextercow...@gmail.com (Mark Dexter) — Fri, 10 Feb 2012 00:03:36 UT

I think we are waiting for a test plan for it. This is not going to be a
quick change. It involves a lot of code and we need to be thorough in
testing and also reviewing the code. Mark

Re: [jbs] Re: Auto Update and GoDaddy.com

i...@weblinksonline.co.uk (Kevin) — Thu, 09 Feb 2012 21:28:10 UT

Hi mark
Well if it works then why is it not set RTC in the tracker ? If we now
have something that works then why is it not being used ?
Is there something I'm missing here ? People are commenting on the tracker
but no tests are being run, why not ?

Re: [jbs] Re: Auto Update and GoDaddy.com

dextercow...@gmail.com (Mark Dexter) — Thu, 09 Feb 2012 21:05:51 UT

@Kevin: I haven't tested the patch, but it uses the same technique that
Nicolas' extension (Admin Tools) uses. I have tested Admin Tools with
Godaddy and it worked perfectly for me (3 or 4 different tries). Also,
Admin Tools has been used successfully for 1.5 years on many sites with
iffy hosts.
With the current core update process, the entire job of downloading the

Re: [jbs] Re: Auto Update and GoDaddy.com

winte...@gmail.com (Russ Winter) — Thu, 09 Feb 2012 20:44:32 UT

If.... the upgrades do actually work in their environment and it is purely
down to timing, I would guess that this timer-pop includes the period of
time from finding the update server, through download and installation.
Maybe GoDaddy need to run their own update server from within the network
to reduce peripheral time.

Re: Auto Update and GoDaddy.com

i...@weblinksonline.co.uk (Kevin) — Thu, 09 Feb 2012 19:39:16 UT

Does the patch work well on Gddy ?

Auto Update and GoDaddy.com

dextercow...@gmail.com (Mark Dexter) — Thu, 09 Feb 2012 19:16:37 UT

Hi everyone. I was working with Godaddy support today to figure out why the
update from 1.7 to 2.5 often fails on godaddy.com.
Here is what we learned. They have a 2-minute limit on the Apache module
mod_fcgid. So, if the update can complete in under 2 minutes, you are OK.
Otherwise, the process is killed after 2 minutes and you are left with a

Re: [jbs] Bug in banner model

wr.richard...@btinternet.com (WR RICHARDSON) — Thu, 09 Feb 2012 17:30:51 UT

description is used in the component
To: "Joomla! bug Squad" <joomlabugsquad@googlegroups.c om>
Hi
I found one bug in components/com_banners/models/ banners.php
In the table there is a description column, but does not appear in the
same module and not by var_dump ($ item).
Line added between the 74 and 75 the following information

Bug in banner model

paulo8...@gmail.com (Paulo Martins) — Thu, 09 Feb 2012 17:06:33 UT

I found one bug in components/com_banners/models/ banners.php

In the table there is a description column, but does not appear in the
same module and not by var_dump ($ item).

Line added between the 74 and 75 the following information
'a.description the description,'.
and then managed to make the call in the module. I hope this can help

AW: [jbs] Opinions please: #27932 - {loadposition} not validate - paragraph imbrication problem

ern...@vogelsinger.at (Ernest E Vogelsinger) — Wed, 08 Feb 2012 21:11:06 UT

Ah ok, I have no knowledge about planned 3.0 features. I will provide a
patch to the loadmodule plugin to catch at least most of non-validating HTML
issues, and hope 3.0 will eventually get rid of that stuff ;-)

Ernest

Von: joomlabugsquad@googlegroups.co m
[mailto:joomlabugsquad@googleg roups.com] Im Auftrag von Elin

Re: [jbs] Opinions please: #27932 - {loadposition} not validate - paragraph imbrication problem

elin.war...@gmail.com (Elin) — Wed, 08 Feb 2012 18:36:57 UT

Oh you are talking about if there is a second instance? Yes if there are
two of the same modules loaded they must use the same style. This has been
in the tracker since before 1.5 was released and is much more complicated
than it appears on the surface. I hope that this whole method of inserting

AW: [jbs] Opinions please: #27932 - {loadposition} not validate - paragraph imbrication problem

ern...@vogelsinger.at (Ernest E Vogelsinger) — Wed, 08 Feb 2012 17:53:05 UT

Hi Matt,

did you have the time to check this? As of now the plugin will insert
anything that's rendered "as is" at the very same context. Plugin styles, as
set in the backend, are ignored as I pointed out to Elin, only a style given
in the {loadposition} command will be honored.

However the inserting "as is" without any care will break validation if not

Re: [jbs] Worried about all the Fix button approach

i...@weblinksonline.co.uk (Kevin) — Wed, 08 Feb 2012 16:29:12 UT

Hi Matt
Yes, the easier the better. There is a patch now
[link]
have you seen it ?

Re: [jbs] Version 2.5.1 On the Way

elin.war...@gmail.com (Elin) — Tue, 07 Feb 2012 12:36:50 UT

Basically the version of 11.4 in the CMS *is* a release branch of the
platform. That's exactly what we are talking about.
Mark I think we need to know that some CMS people go straight to the
platform partly because for 6 months that is what we have been telling them
to do. We should monitor the commits to the platform and use our discretion

Re: JModel::getInstance path not taking prefox into account

pbr...@softwaresolutions.com.au (Phil Brown) — Tue, 07 Feb 2012 06:51:29 UT

I should note I had a typo above. However that was only in this
example - the error still occurs

On Jan 20, 4:04 pm, Phil Brown <pbr...@softwaresolutions.com. au>
wrote:

Re: [jbs] Version 2.5.1 On the Way

oferc...@gmail.com (Ofer Cohen) — Tue, 07 Feb 2012 02:20:40 UT

Hey
If we're require to support J! 2.5.x until Dec 2013, we must
update the J!Platform 11.4 (unfortunately, there are bugs
there...).

IMHO, we should open 11.4.x platform branch for fixing critical
bugs for J!2.5. If we're taking this way, we need to stick Joomla