TYPO3 Core

anchoring corrected:

corrected anchor link

function printResultSectionLinks() {
$lines=array();
reset($this->resultSections);
while(list($id,$dat)=each($this->resultSections)) {

// added '.$this > pi_getPageLink($GLOBALS["TSFE"] -> id).' if you have a <base> it doesn't work without
$lines[]='<li><a href="'.$this -> pi_getPageLink($GLOBALS["TSFE"] -> id).'#'.md5($id).'">'.(trim($dat⁰)?htmlspecialchars(trim($dat⁰)):$this>pi_getLL("unnamedSection")).' ('.$dat¹.' '.$this->pi_getLL("word_page".($dat¹>1?"s":"")).')</a></li>';
}
$out = '<ul>'.implode(chr(10),$lines).'</ul>';
return '<div'.$this->pi_classParam("sectionlinks").'>'.$this->cObj->stdWrap($out, $this->conf["sectionlinks_stdWrap."]).'</div>';
}

mrmodulo, i've tried that piece of code and it generates an PHP error on line 921, so something is wrong with it.

Check to see if you're using language detection, and if you are, try with it uninstalled? (See 0000139)

please don't post PHP code directly in here anymore, I just dicovered mantis doesn't properly htmlspecialchars() and thus the code isn't output correctly... Better make attachments.

the attacment you attached just does not work, it even makes the problem worse, now the section header links dont even jump to right location one page.

and page 1 - page 2 - page 3 still dont work!

don't have language detection, whatever that is

well i've tried it again , and i do not have language detection.

the piece of code only makes it worse, now the section header links dont work also.

The search at http://Typo3.org does only work for the first page of results.

When you hit
Page 2 Page 3 Page 4 Page 5 Page 6 Page 7 Page 8 Next >

nothing works.

This is related to the extension RealURL being installed on Typo3.org.

@Ingmar: Did you refer to Franz' comment or on this bug?

The search at http://Typo3.org works now. Great and important!
@Michael Stucki : He has answered to my question.

With your changes to indexed search, is this fixed as well?

I didn't touch this function but I think it is fixed because it works on typo3.org and I've never heard of similar problems since then.

Otherwise, just reopen.