Author Topic: Moving install to another account - asking for field that isn't there? (Read 1645 times)

jsimonis · February 28, 2010, 11:11:02 pm

So I just upgraded my base account to use the newest version of CiviCRM (3.1.3).

I then duplicated it to a new account so I can use the base setup I have as a beginning point for a new site.

I ran through all my typical steps for making the site point to its new location: I edit the civicrm.settings.php file; delete the templates_c folder; make the config_backend in the civicrm_domain table null.

I get to the config backend page (http:/www.mysite.com/civicrm/admin/setting/updateConfigBackend) and I submit the page so it'll recognize the new location.

But then I get this error on the page:

Code: [Select]

Please correct the following errors in the form fields below:

    * New Site Name is a required field.

There isn't a "New Site Name" field on that page - only Base URL and Base Directory fields.

Kurund Jalmi · March 01, 2010, 02:50:04 am

Check http://drupal.demo.civicrm.org/civicrm/admin/setting/updateConfigBackend?reset=1

There is "New Site Name". Note that demo is on 3.1.3

Kurund

jsimonis · March 01, 2010, 03:56:48 am

Very odd. I went and looked at the site I copied this install from and sure enough, that field is there. But it isn't in the duplicate of that install.

jsimonis · March 01, 2010, 08:07:04 pm

Ran through everything a third time and it did the trick. Now I have the new field and I am able to submit the page.

Dave Greenberg · March 02, 2010, 03:20:52 pm

Probably a template caching issue. For others encountering something like this, best to delete all files in the template cache folder (templates_c) if you hit situations like this where displayed form fields are not what you (or the code) expects.

pdowling · March 08, 2010, 05:51:43 pm

I hit the exact same problem on a straight drupal civi upgrade from 3.0.x to 3.1.3. Tried the template_c thing and refreshed a couple of times. No dice so far.

Dave Greenberg · March 09, 2010, 04:35:24 pm

This is a bug. Fix will be part of 3.1.4 release and has been checked into SVN if you want to grab the diffs:
http://issues.civicrm.org/jira/browse/CRM-5910

pdowling · March 09, 2010, 06:31:03 pm

Interesting. Question about the bug report.

Quote

...a multi-site element which doesn't appear if you're not doing multi-site

Is that referring to Drupal multisite or some sort of civi multisite? My site is in a multisite drupal install, but it is the only site that is using civicrm.

Anyway, nothing's really broken so I'll probably wait for the version upgrade.

CiviCRM Community Forums (archive)

News:

Author Topic: Moving install to another account - asking for field that isn't there? (Read 1645 times)

jsimonis

Moving install to another account - asking for field that isn't there?

Kurund Jalmi

Re: Moving install to another account - asking for field that isn't there?

jsimonis

Re: Moving install to another account - asking for field that isn't there?

jsimonis

Re: Moving install to another account - asking for field that isn't there?

Dave Greenberg

Re: Moving install to another account - asking for field that isn't there?

pdowling

Re: Moving install to another account - asking for field that isn't there?

Dave Greenberg

Re: Moving install to another account - asking for field that isn't there?

pdowling

Re: Moving install to another account - asking for field that isn't there?