This is related to Word Press Install Missing civicrm.settings.php; dashboard unavailable; no menus
I suspect that the culprit is the userFrameworkResourceURL I would tray the overrides mentioned in the above thread
Based on Dan's pointer to https://issues.civicrm.org/jira/browse/CRM-15601 , it seems like this used to work. It probably regressed with https://github.com/civicrm/civicrm-core/commit/3fa9688a5 which introduced a very subtle change to how it ignores temp tables. Compare:
(Old) strpos($dao->Name, '_temp') !== FALSE
(New) TABLE_NAME NOT LIKE '%temp'
The answer is: bad upgrade from older database schema. Somewhere in the 4.5 alpha upgrade series something went wrong for me. I'm not sure what, exactly, but the answer was to verify the schema and to a clean install. Sad face.
I was having the same error message. Using Codedogs' change didn't work for me, not sure why.
In my case, I simply hardcoded the 'settingsFile' as follows:
'settingsFile' => /home/user/domains/domain.com/public_html/wp-content/uploads/civicrm/civicrm.settings.php',
Hope this helps someone!
In general, extensions marked as compatible with 4.6 will usually work with 4.7 as well. It may be that the extension author just hasn't had a chance to test it and tag a new release for 4.7. I recommend you:
Install the extension and try it out
Notice if it works correctly or not. Gather specific details of anything that may be amiss.
File an issue on the ...
If you are processing more records at the same time - you will run out of memory -
In order to prevent Out of Memory the best way is to process less records in a single go - civimail does process records in a batch (like 200 approx.) at a single go
Whenever we create PDF in bulk, mail in bulk always we use to end up in Out of memory even in local PC or ...
I may have found a solution elsewhere - which is ugly and requires editing the upgrade scripts. Database Error When Upgrading 4.6 to 4.7 on Drupal 7
So it's not really a solution for me - but maybe it will be a solution for others, as once I got past that issue the 4.6.20 to 4.7.0alpha3 portion failed with the following. Have not found that many google ...
I believe you're referring to CRM-19096 and/or CRM-19219, and possibly CRM-19272.
The first two are fixed with CiviCRM 4.7.11, which is officially released on September 7th, 2016. The third one has a fix available but hasn't been scheduled into a release.
If you can't wait, and you know how to patch your CiviCRM, you can get the fixes from Github; if you ...