Check your permissions on the cache folder, make sure it is writable by the server (usually chmod 777).

I recently had this problem myself in XOOPS 2.0.14.

I had tried changing XOOPS_URL in mainfile.php to a relative URL, e.g. "/xoops".

That resulted in the same "looping" when I tried to enter the admin section.

I tracked the problem to this code in the method checkReferer() in class/xoopssecurity.php:



That method is called by xoops_refcheck() in include/functions.php, which is called by xoopsfwrite() in include/cp_functions.php, which is called by xoops_module_write_admin_menu() in include/cp_functions.php.

I resolved the issue by changing XOOPS_URL back to an absolute URL, e.g. "http://example.com/xoops".

I'm not sure if this is a bug. The problem doesn't occur in XOOPS 2.2.4. I haven't checked 2.0.15.

So I would change it to an absolute URLhttp://localhost/xoops/????

Is it a relative URL now? If so, try changing it to an absolute URL. Of course the URL I posted is only an example; you would use the URL of your site.

Thanks anyway but I found the problem. The suubdirectory was set to read only