Message from discussion
Field imagepos on #__contact_details
Date: Mon, 16 Apr 2012 00:31:52 -0700 (PDT)
From: elin <elin.war...@gmail.com>
To: joomla-dev-cms@googlegroups.com
Message-ID: <28719055.5.1334561512022.JavaMail.geo-discussion-forums@vbda10>
In-Reply-To: <CAHtW0Z-M4GEQ+p0G3NXJZ=9byhASFKQ0DP9TRCf4jn+13VYc4A@mail.gmail.com>
References: <CAHtW0Z9RZFkZxaqPJc1rDXdEReG5n5gP0D6R01_6k2L49iTjeA@mail.gmail.com>
<CABYB9+DyB4Sw=01LYYZQrazCRQnrQDaHwLX_Si0UcTCDYz2s5g@mail.gmail.com>
<CAHtW0Z-M4GEQ+p0G3NXJZ=9byhASFKQ0DP9TRCf4jn+13VYc4A@mail.gmail.com>
Subject: Re: [jcms] Field imagepos on #__contact_details
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_3_11382729.1334561512020"
------=_Part_3_11382729.1334561512020
Content-Type: multipart/alternative;
boundary="----=_Part_4_15709822.1334561512020"
------=_Part_4_15709822.1334561512020
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
What is the problem it is causing?
Elin
On Sunday, April 15, 2012 5:23:31 PM UTC-4, Gabriele Pongelli wrote:
>
> Il 15 aprile 2012 23:17, Sam Moffatt <pasa...@gmail.com> ha scritto:
> > It may not be used in the core but as the field hasn't been marked for
> > removal or flagged for removal it may be used by third party
> > extensions which could break with it's removal in general. Probably
> > just needs to be flagged for deletion and scheduled for removal with
> > CMS 3.0 since it permits backwards incompatible changes.
>
>
> How is it possible to schedule that removal ?
>
>
> Eng. Gabriele Pongelli
>
>
------=_Part_4_15709822.1334561512020
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
What is the problem it is causing?<div><br></div><div>Elin<br><br>On Sunday, April 15, 2012 5:23:31 PM UTC-4, Gabriele Pongelli wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Il 15 aprile 2012 23:17, Sam Moffatt <<a href="mailto:pasa...@gmail.com" target="_blank">pasa...@gmail.com</a>> ha scritto:<br>> It may not be used in the core but as the field hasn't been marked for<br>> removal or flagged for removal it may be used by third party<br>> extensions which could break with it's removal in general. Probably<br>> just needs to be flagged for deletion and scheduled for removal with<br>> CMS 3.0 since it permits backwards incompatible changes.<p><br>How is it possible to schedule that removal ?</p><p><br>Eng. Gabriele Pongelli<br></p><p></p></blockquote></div>
------=_Part_4_15709822.1334561512020--
------=_Part_3_11382729.1334561512020--