Ok...
Lets say our normal url for content is :
index.php?option=com_content&task=view&id=116&Itemid=21
which will be :
option,com_content/task,view/id,116/Itemid,21 in core sef
The content is in a category named cıntent under a section named content. So joomsef tries to have an url like :
/content/somecontent.html
but due to the if statement to get URL in sef.php (starting line 63) :
if (strstr($_SERVER['REQUEST_URI'], 'index.php/content/')
|| strstr($_SERVER['REQUEST_URI'], '/content/')
|| strstr($_SERVER['REQUEST_URI'], 'index.php/component/option,')
|| strstr($_SERVER['REQUEST_URI'], '/component/option,')) {
require_once('functions.php');
decodeurls_mambo();
}
the section or category or anything named as content tried to be published as a directory messes all around and makes php to get url as index.php?option=com_content&task=somecontent.html and the site gives 404 for pages with artio joomsef. Open sef shouts restricted access for the same reason. Solution was to remove content including cases from if statement or to change the section and category names. I preferred second as i dont have time to read through all code and understand why it has that statement (for url having /content/ in it). But as my content writers did that mistake having a section or category named as content i can tell you many are doing so. So it may be considered as a bug or should be staeted in documentation to warn people.
May the force be with you :)