[TYPO3-dev] TYPO3-dev Digest, Vol 43, Issue 40
Starlord
starlort at gmx.net
Thu Apr 19 21:49:11 CEST 2007
-----Ursprüngliche Nachricht-----
Von: typo3-dev-bounces at lists.netfielders.de
[mailto:typo3-dev-bounces at lists.netfielders.de] Im Auftrag von
typo3-dev-request at lists.netfielders.de
Gesendet: Donnerstag, 19. April 2007 12:00
An: typo3-dev at lists.netfielders.de
Betreff: TYPO3-dev Digest, Vol 43, Issue 40
Send TYPO3-dev mailing list submissions to
typo3-dev at lists.netfielders.de
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
or, via email, send a message with subject or body 'help' to
typo3-dev-request at lists.netfielders.de
You can reach the person managing the list at
typo3-dev-owner at lists.netfielders.de
When replying, please edit your Subject line so it is more specific
than "Re: Contents of TYPO3-dev digest..."
Today's Topics:
1. Re: confidential extension configuration options
(Nikolas Hagelstein)
2. Re: confidential extension configuration options (Steffen Kamper)
3. Quick fix for pop-up links (Tapio Markula)
4. Re: Review process nuisances (Christian Lerrahn (Cerebrum))
5. Re: Typo3 update packe generation (Til Obes)
6. Re: Typo3 update packe generation (Dmitry Dulepov)
7. Re: Review process nuisances (Martin Kutschker)
8. Making an inner join with pi_query_exec? (Brian Bendtsen)
9. Re: Setting a extension 'view' to not-cache without piVars,
cHash but with addPItoST43 cache=1 (Jonas D?bi)
10. Re: Typo3 update packe generation (Andreas Otto)
----------------------------------------------------------------------
Message: 1
Date: Wed, 18 Apr 2007 13:42:38 +0200
From: "Nikolas Hagelstein" <hagelstein at shr.cc>
Subject: Re: [TYPO3-dev] confidential extension configuration options
To: "List for Core-/Extension development"
<typo3-dev at lists.netfielders.de>
Message-ID:
<mailman.154495.1176896560.21067.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset="US-ASCII"
Hi,
>Serialize it and encode with any PHP encoding functions.
>Than put into extconf.
Not that much maintainable....
Bye,
Nikolas
------------------------------
Message: 2
Date: Wed, 18 Apr 2007 13:52:41 +0200
From: "Steffen Kamper" <steffen at dislabs.de>
Subject: Re: [TYPO3-dev] confidential extension configuration options
To: typo3-dev at lists.netfielders.de
Message-ID:
<mailman.1.1176897158.13572.typo3-dev at lists.netfielders.de>
"Nikolas Hagelstein" <hagelstein at shr.cc> schrieb im Newsbeitrag
news:mailman.154495.1176896560.21067.typo3-dev at lists.netfielders.de...
Hi,
>Serialize it and encode with any PHP encoding functions.
>Than put into extconf.
Not that much maintainable....
Bye,
Nikolas
Hi,
there is no real way to hide such informations. Anybody who can access the
localconf.php is possible to view DB password as well, so this is the place
to put confidential infomations into.
vg Steffen
------------------------------
Message: 3
Date: Wed, 18 Apr 2007 16:40:44 +0300
From: Tapio Markula <tapio.markula at atwebteam.com>
Subject: [TYPO3-dev] Quick fix for pop-up links
To: typo3-dev at lists.netfielders.de
Message-ID:
<mailman.1.1176903638.30850.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Hi
> Typo3 (used 4.0.x) has bug creating external links
> with certain window size.
> <a href="http://.../typo3/alt_doc.php#"
>
onclick="window.open('http://www....yleisesite.htm','popup','height=800,widt
h=600')"><strong>Virtuaaliesite</strong></a><br
/>
> if used onclick="... the *last* statement should be 'return false'
> Even if href="..." is not ok with 'return false' nothing happens.
> Where this is defined to make a quick fix or this already fixed.
> Uset tinyrte - is this the same also in rtehtmlare or is this just
> tinyrtebug?
Hi,
I can confirm this bug with FE-Editing. When deleting "return false"
with Firebug my editing window appears again. Before nothing happened at
all.
------------------------------
Message: 4
Date: Thu, 19 Apr 2007 14:53:47 +1000
From: Christian Lerrahn (Cerebrum) <christian.lerrahn at cerebrum.com.au>
Subject: Re: [TYPO3-dev] Review process nuisances
To: typo3-dev at lists.netfielders.de
Message-ID:
<mailman.1.1176958431.32026.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset=US-ASCII
Hi Masi,
> > I really appreciate the introduction of the review process. As
> > somebody with a strong security background, I do see the need for
> > that, particularly because I realise how hard it sometimes is to
> > judge where TYPO3 will do the security checks for you and where it
> > doesn't.
>
> To my knowledge the review process is dead. Too little resource to do
> new reviews of extensions and re-reviews of already reviewed
> extensions.
Hm, hadn't heard that before. Very sad. :( So why does the extension
manager's import function not default to 'all', now. This would be a
logical consequence of such a decision.
> > However, this whole idea can also be a great nuisance which actually
> > devalues the whole process again. Too often the reviewed versions
> > even of rather widespread extensions are immature while the major
> > bug fix releases have not been reviewed, yet.
>
> Note that the reviews promised a "basic security check". That means
> the code is checked if it contains any security problems. It was
> never the intention to have any quality testing of these extensions.
That's not what I was talking about. All I'm saying that it is no use
knowing that a version has been reviewed if it is just crap in any
other sense than basic security.
> I had this issue a while ago with
> > templavoila where the reviewed version was still beta while the
> > stable version was not reviewed. Today I stumbled over such a
> > problem again. The version of newloginbox which is currently
> > available as "reviewed" does not have the storagePID TS override
> > for the "General Root Storage Pid". This means that the reviewed
> > version is unusable with TV. As I use it on a TV site, I therefore
> > have to introduce an unreviewed extension because otherwise this
> > bug will affect me.
>
> To me this is a missing feature not a bug. Anyway the extension is
> usable if you store your users in the same folder as the TV records.
>
> I know this is a hassle, and to me the concept of the General Storage
> Pid is a failure.
I absolutely agree with this statement!
Cheers,
Christian
------------------------------
Message: 5
Date: Thu, 19 Apr 2007 08:58:40 +0200
From: Til Obes <til at rz.uni-karlsruhe.de>
Subject: Re: [TYPO3-dev] Typo3 update packe generation
To: typo3-dev at lists.netfielders.de
Message-ID:
<mailman.1.1176965947.16540.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Ok after some first tests, there occured some problems.
The versions in svn are not the versions being offered
for download as zip/tar.gz. It seems, that this packages
gain some manual correction by the dev team, but the
changes aren't given back to the svn.
For example:
Version 4.0.5 in the tags directory has some files
>from version 4.0.6. If you look into this file:
http://typo3.svn.sourceforge.net/viewvc/typo3/TYPO3core/tags/TYPO3_4-0-5/t3l
ib/config_default.php?view=log
You will find this line:
$TYPO_VERSION = '4.0.6-dev';
So this file isn't changed from version 4.0.5 to 4.0.6.
So maybe some devs with svn access can comment this?
Regards Til
------------------------------
Message: 6
Date: Thu, 19 Apr 2007 10:03:54 +0300
From: Dmitry Dulepov <9f4eetb02 at sneakemail.com>
Subject: Re: [TYPO3-dev] Typo3 update packe generation
To: typo3-dev at lists.netfielders.de
Message-ID:
<mailman.1.1176966231.16347.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Til Obes wrote:
> Ok after some first tests, there occured some problems.
> The versions in svn are not the versions being offered
> for download as zip/tar.gz. It seems, that this packages
> gain some manual correction by the dev team, but the
> changes aren't given back to the svn.
> For example:
> Version 4.0.5 in the tags directory has some files
> from version 4.0.6. If you look into this file:
>
http://typo3.svn.sourceforge.net/viewvc/typo3/TYPO3core/tags/TYPO3_4-0-5/t3l
ib/config_default.php?view=log
>
> You will find this line:
> $TYPO_VERSION = '4.0.6-dev';
> So this file isn't changed from version 4.0.5 to 4.0.6.
>
> So maybe some devs with svn access can comment this?
I thinks files are tagged after packages have been created.
--
Dmitry Dulepov
Web: http://typo3bloke.net/
Skype: callto:liels_bugs
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
------------------------------
Message: 7
Date: Thu, 19 Apr 2007 09:28:17 +0200
From: Martin Kutschker <Martin.Kutschker at n0spam-blackbox.net>
Subject: Re: [TYPO3-dev] Review process nuisances
To: typo3-dev at lists.netfielders.de
Message-ID:
<mailman.1.1176967692.20310.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Christian Lerrahn (Cerebrum) schrieb:
>>>However, this whole idea can also be a great nuisance which actually
>>>devalues the whole process again. Too often the reviewed versions
>>>even of rather widespread extensions are immature while the major
>>>bug fix releases have not been reviewed, yet.
>>
>>Note that the reviews promised a "basic security check". That means
>>the code is checked if it contains any security problems. It was
>>never the intention to have any quality testing of these extensions.
>
> That's not what I was talking about. All I'm saying that it is no use
> knowing that a version has been reviewed if it is just crap in any
> other sense than basic security.
Of course it is a nuisance. That's why I told you that "reviewed" in TER
doesn't mean what you think it does.
Masi
------------------------------
Message: 8
Date: Thu, 19 Apr 2007 11:07:28 +0200
From: Brian Bendtsen <nightowl at galnet.dk>
Subject: [TYPO3-dev] Making an inner join with pi_query_exec?
To: typo3-dev at lists.netfielders.de
Message-ID: <mailman.1.1176973637.7274.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
HI
Im new at extension programming and Im trying something like this:
$conf['where'] = "AND table1.value = 1 AND table2.value = 2"
$conf['query'] = "FROM [table1] INNER JOIN [table2] ON table1.id =
table2.foreignkeyid"
$this->pi_exec_query('table1', $addWhere = $conf['where'], $query =
$conf['query'])
- but im not getting the results I want, actually I think the $query
with the join is not working.
What is wrong with this?
By the way, the method description says that PID selecting clauses are
bybassed, what does that mean?
/Brian Bendtsen
------------------------------
Message: 9
Date: Thu, 19 Apr 2007 11:15:21 +0200
From: Jonas D?bi <admin at commandline.ch>
Subject: Re: [TYPO3-dev] Setting a extension 'view' to not-cache
without piVars, cHash but with addPItoST43 cache=1
To: typo3-dev at lists.netfielders.de
Message-ID: <mailman.1.1176974144.9392.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hello Elmar
Do you know if there is some download page for the extension which is
used on http://www.4any1.de/www.4any1.de?id=2346?
I would like to check out that source code.
Regards
Jonas
Elmar Hinz schrieb:
> Am Tue, 17 Apr 2007 10:54:48 +0200 schrieb Jonas D?bi:
>
>> Hello
>>
>> I'v got an extension with cache enabled.
>>
>> That works fine for all the views which should be cached, which get a
>> cHash or have special piVars.
>>
>> I have a flexform where you can select a view (List, Detal...) and one
>> of this views shouldn't be cached in any case. I tried to set
>> $this->pi_USER_INT_obj = 1 for this view, but it doesn't help.
>>
>> Is there any way to decide if a special view of an extension shouldn't
>> be cached in a special case which is not set by piVars or cHash? Or do I
>> have to make a separate pi2 for this view?
>>
>> Greetings Jonas
>
> Hi Jonas,
>
> well read some of the previous threads.
>
>
http://t3flyers.wordpress.com/2007/04/06/a-quick-guide-to-proper-caching-wit
h-tslib_pibase-episode-1/
>
http://typo3.org/extensions/repository/view/efaq/0.1.5/info/configurations%2
52Fsetup.txt
> http://www.4any1.de/www.4any1.de?id=2346
>
> Regards
>
> Elmar
>
------------------------------
Message: 10
Date: Thu, 19 Apr 2007 11:42:03 +0200
From: Andreas Otto <andreas.otto at dkd.de>
Subject: Re: [TYPO3-dev] Typo3 update packe generation
To: typo3-dev at lists.netfielders.de
Message-ID:
<mailman.1.1176975893.13680.typo3-dev at lists.netfielders.de>
Content-Type: text/plain; charset=us-ascii
Hi Til,
Til Obes wrote:
> So this file isn't changed from version 4.0.5 to 4.0.6.
>
> So maybe some devs with svn access can comment this?
This might result from creating the tags at the wrong time during the
project lifecycle.
The release process needs a bit optimization. We are working on this.
Cheers,
Andreas
------------------------------
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev at lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
End of TYPO3-dev Digest, Vol 43, Issue 40
*****************************************
More information about the TYPO3-dev
mailing list