TYPO3 Core

there is an error in 0012094.patch - so i just uploaded 0012094_v2.patch

add &parameter=te'st

page = PAGE
page.5 = TEXT
page.5.data = GPvar:parameter
page.5.wrap = <h2>|</h2>
page.6 = TEXT
page.6.data = GPvar:parameter
page.6.wrap = <h2>|</h2>
page.6.fullQuoteStr = tt_content

just uploaded enhanced patch from Bastian Waidelich

patch works:)

v3 ships two options: quoteStr and fullQuoteStr

Usecases are demonstrated in the following two examples:

1. 1) quoteStr
   page = PAGE
   page.10 = CONTENT
   page.10 {
   table = tt_content
   select {
   andWhere.cObject = TEXT
   andWhere.cObject {
   data = GPvar:parameter
   quoteStr = tt_content
   wrap = header LIKE "|%"
   }
   }
   }

1. 2) fullQuoteStr
   page.20 = CONTENT
   page.20 {
   table = tt_content
   select {
   andWhere.cObject = TEXT
   andWhere.cObject {
   data = GPvar:parameter
   fullQuoteStr = tt_content
   wrap = header=|
   }
   }
   }

I have added an extension which provides the two functions for 4.2. It also works with 4.3 in case the patch will not make it into 4.3

The extension and the corresponding manual can now be found in TER:
http://typo3.org/extensions/repository/view/sm_stdwrapquote/current/

Hi,

Without testing, I guess your first example with quoteStr will fail when using DBAL and having an Oracle database. I'm pretty sure it will lead to same bug as #12721.

I guess solution would be not to use quoteStr() at all, only rely on fullQuoteStr() and "construct" the

header LIKE "|%"

either with toying with all available wrap's or with COA.

I don't have Oracle. Would you be so kind and test this?

The first example could be replaced by this:

page.10 = CONTENT
page.10 {
table = tt_content
select {
andWhere.cObject = TEXT
andWhere.cObject {
value = {GPvar:parameter}
insertData = 1
fullQuoteStr = tt_content
noTrimWrap = |header LIKE ||
}
}
}

Although it works fine, it looks a bit ugly.

There still might be some case where quoteStr is needed. Does anyone know a useful example?

well, IMHO it should not hurt to have the possibility to use quoteStr.

related to #22338

With #22338 it is possible to use markers which are processed via fullQuoteStr.

So this bug can be closed

"With #22338 it is possible to use markers which are processed via fullQuoteStr." --> closed