ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

System settings...keep resetting!

July 07, 2011 6:34pm

Subscribe [2]
  • #1 / Jul 07, 2011 6:34pm

    Aaron Lax

    11 posts

    Ok so I first noticed this a bit ago because the localization settings kept changing, and it was throwing the EE time back to default.  Now I have noticed that the general settings are also being reset, with the only real notable change being that the index.php is being readded to the “Name of your site’s index page” setting…
    Haven’t been able to lock down exactly when this happens, or what triggers it.

  • #2 / Jul 08, 2011 12:07pm

    Kevin Smith

    4784 posts

    Hi Aaron,

    We’ll need a lot more information about your EE and server environment before we’ll be able to help you hunt down the problem. Please review this article on how to post a support request, and follow the steps listed.

    Specifically for this problem, is this an installation that you set up or was it handed off to you? Are settings reset immediately or does it happen sometime later? Walk me through the process I would have to perform in order to see this issue. Let me know what you expect to happen and what happens instead.

    Thanks!

  • #3 / Jul 22, 2011 3:56pm

    Aaron Lax

    11 posts

    Sorry for the delayed response. We are currently hosted at enginehosting, and running v2.1.3
    I can’t upgrade currently due to scale of the site, but I did set up this installation. The EH guys have made some changes to the core to support a couple memory realated items, but after reviewing the affected files I dont believe this is what is causing the issue.

    The settings I notice that get reset are the localization settings, and the site home value resets to “index.php”

    Unfortunately since I dont know what is causing the change, it appears totally randomly at the moment, but I am trying to narrow down places I might look that would cause this kind of change outside of physically changing the settings in the CP

    thanks!

  • #4 / Jul 22, 2011 4:48pm

    Brandon Jones

    5500 posts

    Aaron,

    Have you checked config.php and index.php for any overrides that might be affecting these settings?

  • #5 / Jul 25, 2011 12:51am

    Aaron Lax

    11 posts

    the only reference to anything in config.php is “$config[‘time_reference’] = ‘local’;” which I dont think is to blame…and I don’t see any overrides in the index that would cause this kind of behavior…

  • #6 / Jul 25, 2011 5:20pm

    Brandon Jones

    5500 posts

    HI Aaron,

    In that case, keep us posted if it happens again, and see if you can spot a pattern. We’ll be here.

  • #7 / Jul 25, 2011 5:21pm

    Aaron Lax

    11 posts

    it happened again last night, no insight on any other operations that may hook into those settings?

  • #8 / Jul 25, 2011 5:24pm

    Brandon Jones

    5500 posts

    Aaron, were you accessing the EE control panel around this time?

  • #9 / Jul 25, 2011 5:25pm

    Aaron Lax

    11 posts

    no, there may have been editors on the site, but they would not be accessing any of the site settings.  Only publishing/editing content.

  • #10 / Jul 25, 2011 5:28pm

    Brandon Jones

    5500 posts

    Aaron,

    When the “Name of your site’s index page” gets reset to “index.php” (instead of blank), how do you go about fixing that?

  • #11 / Jul 25, 2011 5:29pm

    Aaron Lax

    11 posts

    I now have that setting overridden in the config.php, the localization is the only remaining strange spot.
    The admins on the site had been maually changing the site index page setting in the general settings page when they noticed the error, up until friday when I hardcoded the override
    thanks

  • #12 / Jul 26, 2011 1:40pm

    Brandon Jones

    5500 posts

    Aaron,

    I would check with EngineHosting to ensure there are no recurring processes that might be overwriting certain files or tables in your database (particularly exp_sites, which is where these preferences are stored). If that doesn’t turn up anything, my only remaining suggestion would be to upgrade to 2.2.1 so we’re sure we’re dealing with a fully intact set of files.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases