Drupal 10, the latest version of the open-source digital experience platform with even more features, is here.I'm basing this on the branch where I merged the backend in, so YMMV. Anyway, I used remote_import to pull a CiviCRM site between an Aegir2 server and an Aegir3 server. It worked quite well, except for some stale file paths. Specifically, files/civicrm/ConfigAndLog/Config.IDS.ini Interestingly, it contained the correct filter_path but tmp_path and HTML_Purifier_Cache both point to the old platform path.
I expected a 'Verify' task might re-write this file, but it didn't appear to. Perhaps these are set somewhere in the DB? Anyway we should probably look at having this file re-generated on 'Verify' tasks, if it isn't already.










Comments
Comment #2
bgm CreditAttribution: bgm commentedThe Config.IDS.ini should be deleted after such operations. CiviCRM will regenerate it on the next run. The file should normally be deleted if the cache was flushed. Sometimes permissions problems make it impossible to delete the file.
Comment #3
ergonlogicI ran into this again today. When we used remote_import to clone a site from another Aegir server. Config.IDS.ini is writeable by 'aegir'. Perhaps this path is cached somewhere in the database, and so the file gets re-written with stale data?
Anyway, neither verifying the site, nor clearing caches was sufficient to fix it. I had to manually update the paths to the correct ones.
One possible work-around for this would be to ensure that platforms on the sources and destination servers are identical. We'll test this, and report back results.
Comment #4
ergonlogicComment #5
josephleon CreditAttribution: josephleon as a volunteer commentedThere is a confirmed workaround for this, you have to make sure that both the platform and the site have the same names from where you are importing them.
Comment #6
ergonlogicThis is caused by an upstream change in CiviCRM that Aegir doesn't properly support yet. Basically, there's a setting that specifies the path for temporary files, and it isn't getting reset when we clone a site, nor does clearing caches help directly.
Assuming that the site is inaccessible, the initial work-around works like so:
files/civicrm/ConfigAndLog/Config.IDS.inichown aegir:www-data files/civicrm/upload/ -RNow the site ought to be accessible, and its upload temporary file directory ought to be writable by the web user. To ensure these settings remain, do the following:
civicrm/admin/setting/pathcivicrm/admin/setting/updateConfigBackendComment #7
ergonlogicRefer to this discussion: https://hefring.mig5.net/bot/log/aegir/2015-12-23#T603338
Comment #8
bgm CreditAttribution: bgm commentedIs it safe to close this issue? I feel like it has been fixed by other issues, including the work done to set proper permissions.