TYPO3 Core

just checked, rebuilding from the doc-extension does not help.

I tried reproduce it on my 4.2RC1 and cannot do so. I get a proper ->CONFIG. Here are my extensions loaded with manuals:

Extension css_styled_content...0 sections
Extension rtehtmlarea...10 sections
Extension kb_unpack...0 sections
Extension doc_core_tsref...87 sections
Extension doc_core_tsconfig...17 sections
Extension static_info_tables...1 sections
Extension templavoila...3 sections
Extension ss_ldappasswd...1 sections
Extension eu_ldap...0 sections
Extension tt_news...0 sections
Extension felogin...1 sections
Extension doc_indexed_search...1 sections

attached is the screenshot. Plus, I looked it up in my static_tsconfig_help tables via PHPmyadmin

The DB entry looks like this... you can see that my DB somehow cuts off the string at some point and then cannot finish the serialized data (doesn't close the }}). Therefore the BE cannot deserialize it and cannot render it.

51 7389802 f98a9e5726c62fb08803c31cac589abb tsref:config/->CONFIG a:1:{s:4:"rows";a:109:{i:0;a:6:{s:8:"property";s:8:"linkVars";s:8:"datatype";s:4:"list";s:11:"description";s:1097:"HTTP_GET_VARS, which should be passed on with links in TYPO3. This is compiled into a string stored in $GLOBALS["TSFE"]->linkVars<br> <br>The values are rawurlencoded in PHP.<br> <br>You can specify a range of valid values by appending a () after each value. If this range does not match, the variable won't be appended to links. This is very important to prevent that the cache system gets flooded with forged values.<br> <br>The range may containing one of these values:<br> <b>[a]-[b]</b> - A range of allowed integer values<br> <b>int</b> - Only integer values are allowed<br> <b>[a]|[b]|[c]</b> - A list of allowed strings (whitespaces will be remove

Benni, does this still happen to you in 4.3? I thought I had come across some bugs, but I can't reproduce any now. I tested it with the latest version of doc_core_tsref from TER and had a complete reference available, including new properties for 4.2, meaning that the TSref was indeed parsed.

Hey Francois,

yes. it still occurs:

• I install doc_core_tsref (4.3.0)
• I first try with re-importing the static file data from the install tool
• all the other values are there except for the CONFIG object
• When I rebuild my documentation, CONFIG is still empty

I see. Sorry I had misunderstood what you meant. I thought the CONFIG object was just an example, but it's where the mistake actually happens.

So I will check. My guess is that it's because it's too large for the DB field. This already happened before when the field was just a BLOB. Many tables were too large for it and I changed it to MEDIUMBLOB. I can well imagine that CONFIG is even larger that this. Will check.