Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • asifak Friend
    #169317

    I am using JA Telline IIIV2, however I know problem under here is not due to template, still I would like to get any idea from this forum to resolve this issue.

    I was using shared Linux hosting and every thing was working fine. I have taken now Virtual Dedicated Server which has Linux apache 2.0. When I save Global configurations in the back-end then it saves but at the same times it also gives following message

    JFolder::create: Infinite loop detected

    I have tried to search it in Google, joomla forums but no luck. I have tried many options but still no resolution. Any body having idea on this.??

    asifak Friend
    #417421

    I resolved this issue. It was a problem of ‘open_basedir’ parameter which restricts access to some directories on the server and this parameter is configured by some Linux hosting servers in file httpd.include. Normally, this file is not accessible to a user. There is a long procedure to resolve this issue. You have to create new file vhost.conf and place it in ‘conf’ folder normally available at site root. Inside this file, parameter ‘open_basedir’ is configured to null or modified.

    jooservices Friend
    #418845

    It’s nice you have solved yourself and thanks for the solution.

    Viet Vu

    jacqueline stott Friend
    #509963

    Hi Iam having a similar problem, moved multiple joomla sites to a new host (from cpanel to zpanel).

    Iam getting this error: JFolder::create: Infinite loop detected Failed deleting tmpgiXEvJ

    All other sites are not displaying the error except one site, I made sure that that the log and tmp directories are correct (/var/zpanel/hostdata/tvw/public_html/mydomain/tmp) and 777 but still getting the error.

    Please help.

    Saguaros Moderator
    #510192

    Hi jacquis,

    It seems to be a common issue of wrong path for tmp and log folders as described here: http://forum.joomla.org/viewtopic.php?f=470&t=266930

    I saw once case time ago that server turn on the safe mode and it caused the same error.

    Kindly check it again.

Viewing 5 posts - 1 through 5 (of 5 total)

This topic contains 5 replies, has 4 voices, and was last updated by  Saguaros 11 years, 1 month ago.

We moved to new unified forum. Please post all new support queries in our New Forum