as a temp fix I reverted it back to
$data['scriptText'] = \JText::script();

github.com/joomla/joomla-cms/commit/0531...039de7e125ee3c4658ba

rkriver wrote:

same here but depends on the template too. Old yootheme_nano_2 throws out that error while T3 blank from joomlart is working fine.

you are aware that JoomSEF does not work under 3.7.x either?

waiting for a 3.7.x compatible version for months now, there is still no public comment/ETA. I highly doubt this will change soon.

thanks, will send you a mail in a few minutes with necessary data.

sorry to bring this back but it's still happening. But we were able to find the source, its only happening when you edit an article (backend at least). Once you save the links come up. Not every time but it only affects edited articles (we use latest JCE-editor). Haven't noticed before cause we have several active writers. Thats even explains why we never see an issue with auto-generated domains in backend.

And another issue we found:
Joomsef is not able to switch by given domains anymore. With JS3 (&Joomfish @J1.5) we used
domain.com/english.html and domain.de/english.html (cause translating urls was broken sometimes in the past...)

with he new one we like to use translated urls (cause even disabling that option does not work, it still translates) but it's not able to determine that
content on .de has to be german. Instead
domain.de/english.html redirects to domain.com/english.html instead of domain.de/german.html
the setting is set to 'redirect to correct domain'
it only works if the category is translated too.

furthermore paginations are broken. Had to disable this cause sometimes page 1 got page 3, page 1 got left out, page 2 is actually page 3 aso. Fully unreliable.

Language Switcher is often given completely wrong links. Even if all links are correct in backend it sometimes fetches another link from the same component as translation.

thanks, will think about it when this continues.

Maybe too early to party but I've changed
Set page base href value: only base to full seo

now and since yesterday theres no new wrong link popping up or any other visible sideeffect.

thx dajo, we use
joomla 2.5.8, Joomsef 4.2.9, Falang 1.1.7
should be always the latest version

some more popping up while just browsing main language. Still seems to be completely random.

no subdomains here, just www.xy.com and www.xy.de
config-settings attached

no, these posted traces are only from wrong urls.

some more

ok, will try to record some.
While they seem to be random, they never have been seen on default language (en) and never when URLs are updated in backend (&task=updateurls).

just happend after a translation was edited in falang. Before it was working correctly. Sadly isn't reproducable, next edit still keeps the working url.

and it does, perfect thanks!

sometimes we see newly generated URLs that include the whole domain and the wrong (default) language so in frontend the generated link is:
wj15.domain.dehttp://wj15.domain.de/category/requirements

SEF: wj15.domain.de/category/requirements
Real. index.php?option=com_content&catid=55&id=400&lang=de&view=article&Itemid=183

after deleting this one it gets correctly regenerated:
wj15.domain.de/Kategorie/systemanforderungen

SEF: Kategorie/systemanforderungen
Real: index.php?option=com_content&catid=55&id=400&lang=de&view=article&Itemid=183

can't a find a pattern when this happens, seems to be fully random

great dajo, thanks!
Will this be 'soon' or can you give a short hint/file where to fix?

Hi with Falang enabled, translation works fine except for modules that contain time/date-informations like a news-module (Display News 2.0 / Latest News + aso).Using two languages, each with a unique domains.
.de domain shows just the dates in english (Thursday, 29 November 2012), .com in german (Donnerstag, 29. November 2012). Titles are perfectly translated. So are dates in other places than modules.
With Joomsef disabled (/de & /en used) everythings as it should be.

thanks dajo, can we expect this to be fixed in next version?

thanks dajo! As a fast workaround I've adjusted the .xml to J2.5-format and so far the old -3-versions seems to be still working fine (at least with our settings).

are there any news on a 4 compatible version?