Nabble - TYPO3 Dev

BE RTE questions

2009-12-08T12:14:22Z

For an extension I am writing I used the hooks in class.tx_rtehtmlarea_pi3 to
add a new tab to the link browser, looking at the mod3 php I can see how
the title box and width and height are made and have added those to my tab,
now I want to show records from my extension.

1> Is there away of making a page tree that allows you to select records? I
see how the page tree is added but looking in the API I can't see how I can
tell it to allow me to select db records.

I started trying to build my own interface, getting the records my self and
creating the fields from scratch. I have a record (a book), and each book
has associated pages (records from a second table). I want to just show
books that the backend user is allowed to see (because he is the author),
the BE user then selects a book and then I want to show pages that are part
of the selected book. Then when you click on the page a link to it is
created.

Is there some kind of function that allows you to control the creation of
the tree or specify that you want to select records with it?

If this is not possible, I shall keep going with my own approach - I have
learnt quite a lot about the rte and how parts of TYPO3 function :-)

What would be good, if I have to build my own record selector, is to know
what page is the site root. I have the content element id and from this I
have found the page that the rte is on, but how can I find the site root
from this page? I need to know it so that I can use the uid in my queries.

2> My classes modifyMenuDefinition method looks like this at the moment:

public function modifyMenuDefinition($menuDefinition) {
// Menus seem to be the tabs at the tob of the popup. Array keys:
// sActive - 1 marks tab as active, otherwise empty. Still can't get it
to add the correct class to the td
// label - The tabs title Text
// url - defaut seems to be #.
// addParams - seems to be an onclick event handler, example:
onclick="jumpToUrl('?act=page&editorNo=data[tt_content][166][bodytext]&contentTypo3Language=false&contentTypo3Charset=utf-8');return
false;"

$active = false;

// Set active status of the tab of it is selected
if ($this->parentObj->act == 'gamebook') {
$active = 1;
}

$menuDefinition['gamebook'] = array(
'sActive' => $active,
'label' => 'Gamebook',
'url' => '#',
'addParams' =>
'onclick="jumpToUrl(\'?act=gamebook&editorNo=data[tt_content][166][bodytext]&contentTypo3Language=false&contentTypo3Charset=utf-8\');return
false;"'
);
return $menuDefinition;
}

I check to see if it is active and set the sActive ele to 1, like I saw
other tabs in the link browser doing, but my tab, even when selected, is
never has the correct class. Other tabs when selected have the class
'tabSelected' (if I remember correctly) and mine always has just 'tab', so
it never looks selected, even though it is. What do I have to do in addition
to what I have already done to get the class changing when my tab is
selected?

-----
--
Stephen Bungert
--
View this message in context: http://old.nabble.com/BE-RTE-questions-tp26699970p26699970.html
Sent from the TYPO3 Dev mailing list archive at Nabble.com.

_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev

--
Stephen Bungert

BE RTE questions

2009-12-08T12:14:21Z

For an extension I am writing I used the hooks in class.tx_rtehtmlarea_pi3 to add a new tab to the link browser, looking at the mod3 php I can see how the title box and width and height are made and have added those to my tab, now I want to show records from my extension.

1> Is there away of making a page tree that allows you to select records? I see how the page tree is added but looking in the API I can't see how I can tell it to allow me to select db records.

I started trying to build my own interface, getting the records my self and creating the fields from scratch. I have a record (a book), and each book has associated pages (records from a second table). I want to just show books that the backend user is allowed to see (because he is the author), the BE user then selects a book and then I want to show pages that are part of the selected book. Then when you click on the page a link to it is created.

Is there some kind of function that allows you to control the creation of the tree or specify that you want to select records with it?

If this is not possible, I shall keep going with my own approach - I have learnt quite a lot about the rte and how parts of TYPO3 function :-)

What would be good, if I have to build my own record selector, is to know what page is the site root. I have the content element id and from this I have found the page that the rte is on, but how can I find the site root from this page? I need to know it so that I can use the uid in my queries.

2> My classes modifyMenuDefinition method looks like this at the moment:

public function modifyMenuDefinition($menuDefinition) {
// Menus seem to be the tabs at the tob of the popup. Array keys:
// sActive - 1 marks tab as active, otherwise empty. Still can't get it to add the correct class to the td
// label - The tabs title Text
// url - defaut seems to be #.
// addParams - seems to be an onclick event handler, example: onclick="jumpToUrl('?act=page&editorNo=data[tt_content][166][bodytext]&contentTypo3Language=false&contentTypo3Charset=utf-8');return false;"

$active = false;

// Set active status of the tab of it is selected
if ($this->parentObj->act == 'gamebook') {
$active = 1;
}

$menuDefinition['gamebook'] = array(
'sActive' => $active,
'label' => 'Gamebook',
'url' => '#',
'addParams' => 'onclick="jumpToUrl(\'?act=gamebook&editorNo=data[tt_content][166][bodytext]&contentTypo3Language=false&contentTypo3Charset=utf-8\');return false;"'
);
return $menuDefinition;
}

I check to see if it is active and set the sActive ele to 1, like I saw other tabs in the link browser doing, but my tab, even when selected, is never has the correct class. Other tabs when selected have the class 'tabSelected' (if I remember correctly) and mine always has just 'tab', so it never looks selected, even though it is. What do I have to do in addition to what I have already done to get the class changing when my tab is selected?

--
Stephen Bungert

Bugfix 12428 is buggy for me: 'No TypoScript template found!'

2009-11-09T04:12:35Z

After svn update to R6389, I get
'No TypoScript template found!'
in FE.

When I clear the cache (the red one: clear ALL caches),
1) I get the correct paged rendered in the frontend
at the 'first' time
2) After every reload I get
'No TypoScript template found!'
in the FE until I clear all caches again; then
the page will be rendered _once_ correctly.

Even with
page.config.no_cache = 1
set, the FE only shows content on _first_ call after clear cache ...

Notes:
Latest working Revison was 6364;
Error occurs in Revisions 6365+;
Latest trunk (6389) with t3lib_tstemplate from R6364 works as expected.

So it seems, Bugfix 12428 has introduced this new bug ... but why ?

/Stefan

_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev

Installtool / defaultTypoScript_constants

2009-11-09T03:32:48Z

Hi Devs,

maybe this is a problem with 'Install Tool' / 'All Configuration'
in beta3:

- I have pdf_generator2 installed, that does
t3lib_extMgm::addTypoScriptConstants('extension.pdf_gene...
in ext_localconf.php

- When I save 'Install Tool' / 'All Configuration', I get
(while not having changed anything !):

$TYPO3_CONF_VARS['FE']['defaultTypoScript_constants'] =
'[GLOBAL]'.chr(10).'extension.pdf_generator2.typeNum =
123'.chr(10).'[GLOBAL]'.chr(10).'extension.pdf_generator2.typeNum = 1234'

- When I repeat this, the string in 'defaultTypoScript_constants'
gets duplicated with every save ...

Can anybody confirm this ?
Could not find a bugtracker-entry yet ...

/Stefan

_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev

Deprecation Log problems

2009-11-09T00:05:34Z

Hi,

at high traffic sites, the deprecation log quickly increases and reaches
file sizes of multiple Gigabytes.
Wouldn't it be better, to just log a one time instead of all time it has
been called?

Best wishes
Sebastian
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev

Over 2Million images rendering using GIFBUILDER (but not all at once...)

2009-11-05T15:57:10Z

Hey All,

I have an interesting problem at hand..
I have a database with over 2 million images and these images will
get rendered using GIFBUILDER.

Using some quick debugging I did see that all images will get
generated under typo3temp/GB/

Is it possible to let TYPO3 generate sub-directories for the images?
Something in line like

typo3temp/GB/a/b/9/hgj543jhg5.jpg

the only solution I currently see is XCLASS tslib_gifbuilder,
am I over looking something? maby?

regards, Ries van Twisk

-------------------------------------------------------------------------------------------------
tags: Freelance TYPO3 Glassfish JasperReports JasperETL Flex Blaze-DS
WebORB PostgreSQL DB-Architect
email: ries@... web: http://www.rvantwisk.nl/
skype: callto://r.vantwisk
Phone: +1-810-476-4196 Cell: +593 9901 7694 SIP:
+1-747-690-5133

_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev

Mailinglist server scheduled maintenance

2009-10-16T10:33:39Z

Dear mailinglist and newsgroup users,

as announced earlier at [1], the mailinglist and newsgroup server at
lists.netfielders.de will be unavailable from Friday, 16th October,
20:00 CEST until Sunday, 18th October, 20:00 CEST due to moving the
server to a new hosting provider.

We apologize for any inconvenience and hope for your patience. If
necessary, we will provide status updates on http://twitter.com/typo3
and will issue an announcement once the server is running again at
http://news.typo3.org.

- The server admin team (Sebastian, Michael and Ingmar)

[1]
http://news.typo3.org/news/article/mailinglist-server-scheduled-maintenance/
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: KickStarter RTE field(backEnd) to HTML code (FrontEnd)

2009-10-16T09:51:38Z

Sebastiaan van Parijs schrieb:
> Anybody know the function?

$this->pi_RTEcssText($text)
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: T3X snaphots available

2009-10-16T05:57:39Z

Hi,

Bernhard Kraft schrieb:
> This feature should probably get announced at some more prominent place,
> than just in this mailinglist!!!
>

absolutely - should be on forge startpage!

vg Steffen
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: T3X snaphots available

2009-10-16T05:42:29Z

Andreas schrieb:

> for TYPO3 extensions developed on forge.typo3.org development snaphots
> are available as T3X packages now.
>
> The packages are created for each project's trunk and branches.
>
> The packages will be created once a week during the weekend.
>
> The packages are available on
> http://sourceforge.net/projects/typo3xdev/files/T3X/

Hi Andreas!

Also thanks for this service. I had such a service up and running back
some years ago, when extension development was still done on sourceforge
/ typo3xdev.

But at some time I had to close it down, cause sourceforge blocked my IP
for the CVS services ;) Hope this wont happen for forge.

How do you create the T3X files out of the svn checkout? I created php
script called "extension-packager" at those times which did the job.

This feature should probably get announced at some more prominent place,
than just in this mailinglist!!!

greets,
Bernhard
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: Clearing the cache of a single instance of a page (single view) instead of the whole page

2009-10-16T04:58:21Z

Hi.

On 15.10.2009 11:42 Ernesto Baschny [cron IT] wrote:
>
> in the new caching framework (starting with 4.3), tt_news could "tag"
> his single views with certain key e.g. (tt_news:<uid>) and then hook
> into the processdatamap of TCEmain to delete these cache entries when a
> tt_news record is modified.
>

I just read through the classes t3lib_TCEmain and tslib_fe and the
caching framework interface. This is the result of my exploration:

1) When using the caching framework, tslib_fe also supports reg1. The
reg1 value (integer) is used as a tag of the cache entry.

For example this can be used by
$GLOBALS['TSFE']->page_cache_reg1 = $this->piVars['tt_news']; // Example
GETvar: &tx_ttnews[tt_news]=123

Without caching framework:
field reg1=123 in table cache_pages

With caching framework:
cache entry has tag: reg1_123

This preserves backward compatibility.

2) When using the caching framework, tslib_fe allows to add tags to
$this->pageCacheTags by using $this->addCacheTags(array $tags)

That means one can use
$GLOBALS['TSFE']->addCacheTags(array('tx_ttnews_' .
$this->piVars['tt_news']); // Example GETvar: &tx_ttnews[tt_news]=123

The result is an additional tag in the cache entry: tx_ttnews_123

3) The t3lib_TCEmain API does not (yet) support clearing cache entries
by tag. But it could be enhanced with a function clear_cache_by_tags()

public function clear_cache_by_tags(array $tags=array()) {
if (TYPO3_UseCachingFramework) {
$pageCache = $GLOBALS['typo3CacheManager']->getCache(
'cache_pages'
);
$pageSectionCache = $GLOBALS['typo3CacheManager']->getCache(
'cache_pagesection'
);
$pageCache->flushByTags($tags);
$pageSectionCache->flushByTags($tags);
}
}
}

4) Hooking into processdatamap could then call clear_cache_by_tags() to
flush the appropriate cache entries.

What do you think?

--
cheers,
Steffen

TYPO3 Blog: http://www.t3node.com/
Blubber on Twitter: http://twitter.com/t3node
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: Clearing the cache of a single instance of a page (single view) instead of the whole page

2009-10-16T03:18:21Z

Hi.

On 15.10.2009 17:24 Steffen Gebert wrote:
>
> This would be really interesting. I found out, how to get out sth. by a
> tag, but not how to store it using a tag.
>

For general use have a look at the cache frontend interface:
http://flow3.typo3.org/fileadmin/API/FLOW3/F3/FLOW3/Cache/Frontend/interface-FrontendInterface.html

set(string $entryIdentifier, mixed $data, array $tags=array(), integer
$lifetime=NULL)

$tags array is used to add tags to the cache entry.

You can find an example in t3lib_TStemplate->start() where set() is
using two tags:
array(
'pageId_' . intval($GLOBALS['TSFE']->id),
'mpvarHash_' . $mpvarHash
)

--
cheers,
Steffen

TYPO3 Blog: http://www.t3node.com/
Blubber on Twitter: http://twitter.com/t3node
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: How to handle debug()

2009-10-16T03:00:48Z

Oliver Klee schrieb:
> Hi,
>
> Steffen Kamper schrieb:
>> Mathias Schreiber [wmdb >] schrieb:
>>> You echo stuff out on live client projects?
>>> That's so Rambo... respect :)
>> be aware of the austrian rambo :)
>
> Thanks, guys, you've just put a big grin on my face. :-))

And I'll wipe it off your face ;)

Masi
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: How to handle debug()

2009-10-16T02:55:50Z

Hi,

Steffen Kamper schrieb:
> Mathias Schreiber [wmdb >] schrieb:
>> You echo stuff out on live client projects?
>> That's so Rambo... respect :)
>
> be aware of the austrian rambo :)

Thanks, guys, you've just put a big grin on my face. :-))

Oli
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: How to handle debug()

2009-10-16T02:55:31Z

Mathias Schreiber [wmdb >] schrieb:
> Martin Kutschker schrieb:
>> * Actually I never use it. I usually make manually calls to
>> t3lib_div::print_array as I am too lazy
>> to setup the devIP :)
>
> You echo stuff out on live client projects?
> That's so Rambo... respect :)

No, not live sites. Though on a live sites you can embed th output of print_r() within an HTML comment.

Masi
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: How to handle debug()

2009-10-16T02:21:09Z

Hi,

Mathias Schreiber [wmdb >] schrieb:
> You echo stuff out on live client projects?
> That's so Rambo... respect :)
>

be aware of the austrian rambo :)

vg Steffen
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: How to handle debug()

2009-10-16T01:53:46Z

Mathias Schreiber [wmdb >] schrieb:
> Martin Kutschker schrieb:
>> * Actually I never use it. I usually make manually calls to
>> t3lib_div::print_array as I am too lazy
>> to setup the devIP :)
>
> You echo stuff out on live client projects?
> That's so Rambo... respect :)

maybe all his live client projects are bugfree? ;)
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: How to handle debug()

2009-10-16T01:48:23Z

Martin Kutschker schrieb:
> * Actually I never use it. I usually make manually calls to t3lib_div::print_array as I am too lazy
> to setup the devIP :)

You echo stuff out on live client projects?
That's so Rambo... respect :)

--
TYPO3 certified interogator
T3DD09 Entertainer
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: How to handle debug()

2009-10-15T13:44:32Z

Steffen Kamper schrieb:
>
> debug has to be initialized that early to allow debug extensions to hook
> in, so config_default is a good place for.

I see no good reason to have a function in config_default.php. There are other ways to have it
available early. And the fact that it isn't scoped in a class or at least prefix (eg t3_debug)
doesn't make it more attractive to me. *

But the whole config_default.php stinks and should be refactored. There's too much code in ot that's
not configuration, let alone a default configuration.

Masi

* Actually I never use it. I usually make manually calls to t3lib_div::print_array as I am too lazy
to setup the devIP :)
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: How to handle debug()

2009-10-15T13:34:22Z

Hi,

Felix Oertel schrieb:

> Hi everyone,
>
> as I can see, the debug() function in config_default is the one to be
> used by now. It checks for global errorhandling
> ($GLOABALS['error']->debug()) and provides a fallback to
> t3lib_div::debug().
>
> I think it would be a good idea to move debug() into a namespace
> (providing a dummy-function for compatibility reasons) and remove all
> direct usage of t3lib_div::debug() from the code.
>
> I would do that, just wondred what you guys are thinking.
>
> Regards, Felix

i don't see a need for. And where is t3lib_div::debug() used in core?

debug has to be initialized that early to allow debug extensions to hook
in, so config_default is a good place for.

vg Steffen
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

How to handle debug()

2009-10-15T13:05:31Z

Hi everyone,

as I can see, the debug() function in config_default is the one to be
used by now. It checks for global errorhandling
($GLOABALS['error']->debug()) and provides a fallback to t3lib_div::debug().

I think it would be a good idea to move debug() into a namespace
(providing a dummy-function for compatibility reasons) and remove all
direct usage of t3lib_div::debug() from the code.

I would do that, just wondred what you guys are thinking.

Regards, Felix
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: can't select time in datepicker on pages?

2009-10-15T13:00:49Z

Am 15.10.2009, 21:55 Uhr, schrieb Georg Ringer <mail-spam@...>:

> Wiel, J.A.M. van de schrieb:
>> Just my 2 cts: I have quite a few pages with a very short cache
>> lifetime of just a few minutes. A date-time field could be beneficial
>> in this situation, I've even patched my core for this purpose
>> sometimes. Making this field more precise would get a big +1 from me.
>> If it would be at all possible to fire a clearCacheCmd when the time
>> comes it would be really great (I vaguely remember reading something
>> about events being a feature in 4.3).
>
> ext nf_date2datetime

Anybody willing to provide a patch?
IMHO this is a missing mini-mini-feature we could get into 4.3?

Steffen
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: can't select time in datepicker on pages?

2009-10-15T12:55:50Z

Wiel, J.A.M. van de schrieb:
> Just my 2 cts: I have quite a few pages with a very short cache lifetime of just a few minutes. A date-time field could be beneficial in this situation, I've even patched my core for this purpose sometimes. Making this field more precise would get a big +1 from me. If it would be at all possible to fire a clearCacheCmd when the time comes it would be really great (I vaguely remember reading something about events being a feature in 4.3).

ext nf_date2datetime

georg
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: can't select time in datepicker on pages?

2009-10-15T12:48:05Z

Just my 2 cts: I have quite a few pages with a very short cache lifetime of just a few minutes. A date-time field could be beneficial in this situation, I've even patched my core for this purpose sometimes. Making this field more precise would get a big +1 from me. If it would be at all possible to fire a clearCacheCmd when the time comes it would be really great (I vaguely remember reading something about events being a feature in 4.3).

Bas
________________________________________
From: typo3-dev-bounces@... [typo3-dev-bounces@...] On Behalf Of Steffen Gebert [steffen@...]
Sent: Thursday, October 15, 2009 9:38 PM
To: typo3-dev@...
Subject: Re: [TYPO3-dev] can't select time in datepicker on pages?

Am 15.10.2009, 21:24 Uhr, schrieb Martin Holtz <typo3@...>:

>>> in 4.3-trunk i am not able to select a time in starttime/stoptime of
>>> pages.
>>>
>>> Is that intentional?
>>
>> Yes, because it's a date field (and not a date-time filed).
> ah. i thought it is an date-time field by default in pages and wondered
> why
> it has been changed to an date field in 4.3...

What question remains is: Why is it only a date field?

I know that (thanks to caching) TYPO3 wouldn't exactly adopt the access
limitations at the set minute - but there's also no guarantee that it atm
does it at exactly 0:00 h.

So why not change it to date-time?

Steffen
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: can't select time in datepicker on pages?

2009-10-15T12:38:21Z

Am 15.10.2009, 21:24 Uhr, schrieb Martin Holtz <typo3@...>:

>>> in 4.3-trunk i am not able to select a time in starttime/stoptime of
>>> pages.
>>>
>>> Is that intentional?
>>
>> Yes, because it's a date field (and not a date-time filed).
> ah. i thought it is an date-time field by default in pages and wondered
> why
> it has been changed to an date field in 4.3...

What question remains is: Why is it only a date field?

I know that (thanks to caching) TYPO3 wouldn't exactly adopt the access
limitations at the set minute - but there's also no guarantee that it atm
does it at exactly 0:00 h.

So why not change it to date-time?

Steffen
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: can't select time in datepicker on pages?

2009-10-15T12:24:08Z

Hi,

>> in 4.3-trunk i am not able to select a time in starttime/stoptime of
>> pages.
>>
>> Is that intentional?
>
> Yes, because it's a date field (and not a date-time filed).
ah. i thought it is an date-time field by default in pages and wondered why
it has been changed to an date field in 4.3...

thanks,
martin
--
http://wiki.typo3.org/Ts45min - TypoScript in "45" Minutes
http://wiki.typo3.org/De:ts45min - (auch in Deutsch)

_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: [TYPO3-english] Closedown bugs.typo3.org

2009-10-15T09:35:20Z

Hi,

> there is no subproject th_mailformplus. The bugs regarding
> th_mailformplus are filed under "other extensions", so I would have to
> subscribe to the RSS feed of the whole subproject and receive approx.
> 98.5% irrelevant infos :-)

Sorry, I misunderstood what you meant. I had forgotten about that "catch
all" project. I agree that it should actually be closed now that we have
Forge, but the cleanup might not be so easy.

One thing to write down in the TODO list for after the 4.3 release ;-)

Cheers

--

Francois Suter
Cobweb Development Sarl - http://www.cobweb.ch
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: [TYPO3-english] Closedown bugs.typo3.org

2009-10-15T09:02:40Z

Francois Suter schrieb:

> Hi Reinhard,
>
>> In my opinion, bugs.typo3.org should be ONLY for core related bugs
>> like the core itself and sysexts.
>> Any community extension should use Forge for this because this is what
>> Forge is for.
>
> bugs.typo3.org existed way before Forge. At the time it was convenient -
> for ext developers who wanted it - to share the TYPO3 bugtracker for
> their own extensions. It is entirely possible to close down the
> th_mailformplus subproject on bugs.typo3.org, but you would first have
> to make sure that all bugs on bugs.typo3.org related to th_mailformplus
> either exist on Forge too or can be closed.
>
> We can't force extension developers to move to Forge and - for some
> extensions - it is really difficult because there's such a history on
> bugs.typo3.org.
>
> And about being warned about new bugs, I miss that too, but found that
> there's a RSS feed for each project/subproject. You can subscribe to
> that, it's better than nothing.
>
> HTH
>

Hi Francois,

there is no subproject th_mailformplus. The bugs regarding
th_mailformplus are filed under "other extensions", so I would have to
subscribe to the RSS feed of the whole subproject and receive approx.
98.5% irrelevant infos :-)

Of course bugs.typo3.org existed way before Forge, I know. But it would
be nice to some kind of cleanup and move projects from bugs.typo3.org to
Forge. And I am aware of the fact, that this is no easy task, but the
authors of the extension could be contacted and asked (not forced) to do
that.
I am sure there are many subprojects on bugs.typo3.org which have a
bugtracker on Forge too, so it should be possible to manually move bugs
to Forge.

Cheers

--
mit freundlichen Grüßen,

Reinhard Führicht MSc
Entwickler

---------------------------------------------------

TYPOHEADS
WEB ENGINEERING
www.typoheads.at
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: [TYPO3-english] Closedown bugs.typo3.org

2009-10-15T08:55:07Z

Hi Reinhard,

> In my opinion, bugs.typo3.org should be ONLY for core related bugs like
> the core itself and sysexts.
> Any community extension should use Forge for this because this is what
> Forge is for.

bugs.typo3.org existed way before Forge. At the time it was convenient -
for ext developers who wanted it - to share the TYPO3 bugtracker for
their own extensions. It is entirely possible to close down the
th_mailformplus subproject on bugs.typo3.org, but you would first have
to make sure that all bugs on bugs.typo3.org related to th_mailformplus
either exist on Forge too or can be closed.

We can't force extension developers to move to Forge and - for some
extensions - it is really difficult because there's such a history on
bugs.typo3.org.

And about being warned about new bugs, I miss that too, but found that
there's a RSS feed for each project/subproject. You can subscribe to
that, it's better than nothing.

HTH

--

Francois Suter
Cobweb Development Sarl - http://www.cobweb.ch
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: [TYPO3-english] Closedown bugs.typo3.org

2009-10-15T08:49:06Z

Mathias Schreiber [wmdb >] schrieb:

> Staffan Ericsson schrieb:
>> Hi!
>>
>> I suggest that bugs.typo3.org is closed down as soon as possible. As I
>> watch the summary page I notice 3648 open bugs! In the core there is
>> 1971 open bugs alone and 1202 resolved but unclosed bugs.
>
> This is because we set bugs to "resolved" first and then close them down
> lateron (which is only a usability thing).
>
> Next up I walked through the bugtracker and would close down at least
> 50% of all reported bugs with the remark "user generated error".
> Guess what: They are open less than 24 hrs later :)
> Reason: folks unlikely see that things are their mistake.
>
>> As it is apparent that bugs.typo3 is not used and bugs reported thru
>> that medium is not handled by the typo3 community. As bugs.typo3.org is
>> a blackhole when it comes to bugs it's better to simply close it down
>> that give false hope to all bug reporters.
>
> To the outside this might be true.
> It is very difficult to communicate how bugs are handled within the
> TYPO3 project.
> Bugs are reported.
> Bugs are then either taken up by some of the cool folks at the bug days
> (thank you guys btw.) and provided with patches or the one who found the
> bug supplies a patch.
> These bugs are then transmitted to the Core Mailing List where they need
> positive reviews so we can circumvent that patch A brings up bugs B, C
> and D.
> This works in 95% of all cases (which is pretty good, compared to other
> systems).
>
>> There is an unhealthy rush in the TYPO3 development team towards new
>> functionality and gold plating. The community needs to change focus
>> towards usablitity and bug fixing. Stop all new development until the
>> number of open bugs is below 100!
>
> I think you might not have attended the TYPO3 Developer Days or whatched
> the videos so I won't blame you for not knowing:
> The next TYPO3 releases will:
> a) have a far quicker release cycle (6 months)
> b) focus on 90% bugfixing and "convinience things" and 10% new features
>
> These are of course estimates and only a future plan but all in all it
> should satisfy your demand.
>
> If you have any ideas how to improve outside communication or make the
> current ways to handle things more transparent you can either get in
> touch with Peter Pröll (peter@...) or me (who will then forward a
> digest of your ideas to Peter).
>
> Just a sidenote:
> TYPO3 people are very much like surfers - if you rant in their place you
> might get a bloody nose, even if the rant was not your intention.
>
> Constructive criticism is always (!) welcome.
>
> cheers
> Mathias
>

What "bugs" me about the current appearance of the bugtracker is, that
it seems fairly unorganized.

Example:

There is a project "other extensions" where people report bugs about
specific extensions, in my case th_mailformplus. The problem is that the
extension author isn't informed about this bug in any way. I, for my
part, do not want people to file bugs about my extensions on
bugs.typo3.org because I have bugtrackers for my extensions on Forge.

In my opinion, bugs.typo3.org should be ONLY for core related bugs like
the core itself and sysexts.
Any community extension should use Forge for this because this is what
Forge is for.

In my view, making bugs.typo3.org only for core related bugs will result
in less bugs and a better overview.

Just my 2 cents

--
mit freundlichen Grüßen,

Reinhard Führicht MSc
Entwickler

---------------------------------------------------

TYPOHEADS
WEB ENGINEERING
www.typoheads.at
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: Clearing the cache of a single instance of a page (single view) instead of the whole page

2009-10-15T08:24:17Z

Am 15.10.2009, 17:20 Uhr, schrieb Steffen Müller <typo3@...>:

> Hi.
>
> Thank you all for your input.
>
> On 15.10.2009 11:42 Ernesto Baschny [cron IT] wrote:
>> in the new caching framework (starting with 4.3), tt_news could "tag"
>> his single views with certain key e.g. (tt_news:<uid>)
>
> Do you have an example how tagging is done in the CF?
> Are there some docs on the CF API? (beside phpdoc comments)
>

This would be really interesting. I found out, how to get out sth. by a
tag, but not how to store it using a tag.

Steffen
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: Clearing the cache of a single instance of a page (single view) instead of the whole page

2009-10-15T08:20:17Z

Hi.

Thank you all for your input.

On 15.10.2009 11:42 Ernesto Baschny [cron IT] wrote:
> in the new caching framework (starting with 4.3), tt_news could "tag"
> his single views with certain key e.g. (tt_news:<uid>)

Do you have an example how tagging is done in the CF?
Are there some docs on the CF API? (beside phpdoc comments)

--
cheers,
Steffen

TYPO3 Blog: http://www.t3node.com/
Blubber on Twitter: http://twitter.com/t3node
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: [TYPO3-english] Closedown bugs.typo3.org

2009-10-15T07:20:37Z

Nice answer, Mattes, thanks.

--

Francois Suter
Cobweb Development Sarl - http://www.cobweb.ch
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: [TYPO3-english] Closedown bugs.typo3.org

2009-10-15T06:55:57Z

Staffan Ericsson schrieb:
> Hi!
>
> I suggest that bugs.typo3.org is closed down as soon as possible. As I
> watch the summary page I notice 3648 open bugs! In the core there is
> 1971 open bugs alone and 1202 resolved but unclosed bugs.

This is because we set bugs to "resolved" first and then close them down
lateron (which is only a usability thing).

Next up I walked through the bugtracker and would close down at least
50% of all reported bugs with the remark "user generated error".
Guess what: They are open less than 24 hrs later :)
Reason: folks unlikely see that things are their mistake.

> As it is apparent that bugs.typo3 is not used and bugs reported thru
> that medium is not handled by the typo3 community. As bugs.typo3.org is
> a blackhole when it comes to bugs it's better to simply close it down
> that give false hope to all bug reporters.

To the outside this might be true.
It is very difficult to communicate how bugs are handled within the
TYPO3 project.
Bugs are reported.
Bugs are then either taken up by some of the cool folks at the bug days
(thank you guys btw.) and provided with patches or the one who found the
bug supplies a patch.
These bugs are then transmitted to the Core Mailing List where they need
positive reviews so we can circumvent that patch A brings up bugs B, C
and D.
This works in 95% of all cases (which is pretty good, compared to other
systems).

> There is an unhealthy rush in the TYPO3 development team towards new
> functionality and gold plating. The community needs to change focus
> towards usablitity and bug fixing. Stop all new development until the
> number of open bugs is below 100!

I think you might not have attended the TYPO3 Developer Days or whatched
the videos so I won't blame you for not knowing:
The next TYPO3 releases will:
a) have a far quicker release cycle (6 months)
b) focus on 90% bugfixing and "convinience things" and 10% new features

These are of course estimates and only a future plan but all in all it
should satisfy your demand.

If you have any ideas how to improve outside communication or make the
current ways to handle things more transparent you can either get in
touch with Peter Pröll (peter@...) or me (who will then forward a
digest of your ideas to Peter).

Just a sidenote:
TYPO3 people are very much like surfers - if you rant in their place you
might get a bloody nose, even if the rant was not your intention.

Constructive criticism is always (!) welcome.

cheers
Mathias

--
TYPO3 certified interogator
T3DD09 Entertainer
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

Re: sorting tt_content

2009-10-15T06:43:02Z

Christian Kartnig wrote:
> I want to move lots of content of a site from the right column
> (colPos=2) to the bottom of the normal column (colPos=0) via a database
> query or a script.
>
> Now I'm not sure how the sorting is done in the sorting column of
> tt_content. I want the new content to be always at the bottom.

A deleted item gets sorting value 1000000000
If a record is added to the bottom of a list it will get the highest
sorting value (of a not deleted record) + 256.
If a record is added to the top of a list it will get the lowest sorting
value devided by 2.
If...

If the algorithm runs into problems it calls a resorting function.

You can find the algorithm and functions in
t3lib/class.t3lib_tcemain.php, t3lib_TCEmain::getSortNumber() and
t3lib_TCEmain::resorting().

Regards, Jigal.
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev