fileName for Types doesnt work about typo3-realurl HOT 34 CLOSED

fileName for Types doesnt work

I really cannot fix "does not work" because this does not tell me anything. What exactly happens? Does the computer die? Do you see any exceptions? Do you see errors?

Without RealUrl and with RealUrl 1.x it works

Do you mean the file name work without realurl?

from typo3-realurl.

The URL example.com/robots.txt or example.com/sitemap.xml have a Error 404. That is mean with "doesnt work".

from typo3-realurl.

Is it a TYPO3 404 error?

from typo3-realurl.

Yes a 404 Error.

from typo3-realurl.

example.com/index.php?id=1&type=841231 show the robots.txt File korrekt

from typo3-realurl.

example.com/robots.txt with RealUrl 1.x shows the robots.txt File korrekt as well

from typo3-realurl.

But my Computer does not die! ;-)

from typo3-realurl.

Is it a TYPO3 404 error or your web server 404 error?

from typo3-realurl.

It displays the configured page for 404Errors (in Install Tool => "[FE][pageNotFound_handling] = index.php?id=34" ).
What is the different, I thought that TYPO3 just handle the Webserver Error? Sorry

from typo3-realurl.

Could you temporarily remove that setting for pageNotFound_handling and see what TYPO3 tells you? It will give you a specific error message.

from typo3-realurl.

"[FE][pageNotFound_handling] = " value is now empty. The result is a 404 Error as well, but with the TYPO3 404Error Page.

The message is:
"Page Not Found
Reason: Segment "" was not a keyword for a postVarSet as expected on page with id=1."

from typo3-realurl.

Currently unable to reproduce :(

from typo3-realurl.

Many thanks sofar, but I think it will be fixed ;-)

from typo3-realurl.

I keep it open in case of anybody else have the issue too. Than we can figure out what is wrong. I tried various ways to reproduce it but could not. Possibly it is related to configuration or page tree structure or page settings. I am not sure.

Btw, for the sitemap, you will not be able to set vars as they are described in your configuration because id will always be set by realurl on the later stage. I think you do not really need it there 😄

from typo3-realurl.

Has something changed for the .htaccess?

from typo3-realurl.

No.

from typo3-realurl.

I can confirm this problem!

For example: http: //localhost/robots.txt
Here is an error message
"Reason: Segment" "was not a keyword for a postVarSet as expected on page with id = 1".

When I go to another level - for example, http: //localhost/komponenten/robots.txt

then it works ?! The robots.txt is displayed! Until realurl version 1.13.6 there was NEVER problems !!!

I can be the cause not locate and think there is an error in the new version of realurl ?!

thank you

Harald

from typo3-realurl.

Guys, please, post your full realurl config.

from typo3-realurl.

Hello!

I send my complete realurl_conf. However, I had the file only after realurl_conf.php realurl_conf.txt rename so I can upload it.

realurl_conf.txt
The typoscript I send with as file.
robots.txt

Thank you very much

Harald

from typo3-realurl.

@Gorli Does any other file name (like atom.xml) work?

from typo3-realurl.

I can not say there is not currently in use unfortunately. In use are currently sitemap.xml (typo3 105) and robots.txt (type 106). In both there is a problem.

Page Not Found
Reason: Segment "" was not a keyword for a postVarSet as expected on page with id =. 1

I am also feverishly on Search. Unfortunately no solution.

from typo3-realurl.

Stupid question.
Is the point after id in order?

with id=1.

from typo3-realurl.

I send a picture

from typo3-realurl.

Are you using latest realurl (2.0.5)?

from typo3-realurl.

Yes

from typo3-realurl.

Hi Dimitry,
is your script from the current docu correct working?

Script means:
https://github.com/dmitryd/typo3-realurl/wiki/Configuration-reference#filenameindexkeyvalues

'fileName' => array (
'index' => array(
'print.html' => array(
'keyValues' => array(
'type' => 98
)
),
'rss.xml' => array(
'keyValues' => array(
'type' => 76
)
)
)
)

Cheers
Thomas

from typo3-realurl.

I can confirm that the problem appears NOT on the next level. Working with realurl 2.0.5.

example.com/robots.txt - dont work (Code 404)
example.com/level1/robots.txt - is working (shows robots.txt correct)

doesnt matter what filename it is.

Adding my real_conf.php (as txt)
realurl_conf.txt

from typo3-realurl.

I finally was able to reproduce and fix it.

Problem happened with a preVar, which had noMatch=bypass.

from typo3-realurl.

yipie, Thanks

from typo3-realurl.

Ok, the fileName is working correct now.

from typo3-realurl.

But in the rootpage are 2 Slashes now.

This appears only in the "fileName"-Files like sitemap.xml

Sorry, add a file is a mess in github.

The code:
<urlset> <url> <loc>http://domain.com//</loc> <lastmod>2016-03-04</lastmod> </url> <url> <loc>http://domain.com/level1/</loc> <lastmod>2016-03-04</lastmod> </url> </urlset>

from typo3-realurl.

You want a new issue for the "doubleslash thing"

from typo3-realurl.

I had a similar issue with TYPO3 6.2.21 since updating to realURL 2.x
I've solved the problem in modifying function decodePostVarSets. I just added a verification to verify if $postVarSetKey is not empty :

while (count($pathSegments) > 0) { $postVarSetKey = array_shift($pathSegments); if ($postVarSetKey!="") { if (!isset($postVarSets[$postVarSetKey]) || !is_array($postVarSets[$postVarSetKey])) { $this->handleNonExistingPostVarSet($pageId, $postVarSetKey, $pathSegments); } else { $postVarSetConfiguration = $postVarSets[$postVarSetKey]; // Note: we do not support aliases for postVarSets! if (is_array($postVarSetConfiguration)) { foreach ($postVarSetConfiguration as $postVarConfiguration) { $this->decodeSingleVariable($postVarConfiguration, $pathSegments, $requestVariables, $previousValue); } } } } }

from typo3-realurl.

I have a similar problem with Typo3 7.6.9 and realURL 2.0.14.

The url /?type=841132 works.
The url /sitemap.xml only works if i am logged in in the backend otherwise i get "page does not exist".
My realURL configuration is similar to kakuschke.

Ist this problem already fixed in the new version 2.1.0 ?

from typo3-realurl.