[TYPO3-mvc] Disable Language Overlay

[Thomas Hucke]

Hi Till,

I struggled the same behaviour and found the only solution in using the 
"old" way in my repository class:

  $where = 'stepconf='.$stepname->getStepconf()->getUid() . 
tslib_cObj::enableFields('tx_thrating_domain_model_stepname');
  $queryResult = $GLOBALS['TYPO3_DB']->exec_SELECTgetRows('*', 
'tx_thrating_domain_model_stepname', $where);


Hope it helps
Thomas


schrieb im Newsbeitrag 
news:mailman.340.1385987055.629.typo3-project-typo3v4mvc at lists.typo3.org...

Hi Rob

Thanks for your reply.

I didn't test check it yet...
So what you are saying is, that using a SQL statement without any WHERE
sys_language_id IN (...) wouldn't return all entries, neither? That's
really a bad thing. I.e. there is no work arround other than disableing
the overlay in TCA and writing something of my own?

I was thinking about dynamically changing TCA before the DB queries, but
that's a really ugly approach.

Together strong! :-)

Till



On 12/02/2013 01:05 PM, Rob De Vries wrote:
> Hey Till,
>
> I'm trying to get exactly the same result:
>
> writing a plugin that extends tx_news so people can submit news
> articles via the frontend.
> All new items are then listed out, so translators can start
> translating a news item.
>
> and this is were is fails: i'm not able to get the original and the
> translated version of 2 news items on 1 page.
> This has to do with a 'missing' feature in extabse (some call it a bug)
> http://forge.typo3.org/issues/47192
>
> So your idea to write our own query won't help.
> You can so something like:
>
>
>  public function needTranslation($translation) {
>        $query = $this->createQuery();
>        $query->getQuerySettings()->setRespectStoragePage(FALSE);
>        $query->getQuerySettings()->setRespectSysLanguage(FALSE);
>        $query->matching( $query->equals('uid', $translation));
>        return $query->execute();
>    }
>
> were  $query->getQuerySettings()->setRespectSysLanguage(FALSE);
> would normaly prevent getting the translated version of the object,
> but it doesn't.
>
> So i'm not handling you a solution for now, but a direction were to
> look at.
> If you find a solution, i'll be glad to hear from you, i'll do the same.
>
> together strong, right? :)
>
> greetings
> Rob
> _______________________________________________
> TYPO3-project-typo3v4mvc mailing list
> TYPO3-project-typo3v4mvc at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc