I think I have a workaround. It will involve some editing of PHP code though, so if that sounds too onerous, you might have to find someone to try it for you.
The idea is to not enable path.module until later in the Installation process.
In the file .../profiles/prosepoint/prosepoint.profile,
1.
In the function prosepoint_profile_modules(), at approximately line 597, comment out the line 'path' so it looks like:
// other drupal core
'contact',
// 'path',
'tracker',
'search',
2.
In the function prosepoint_profile_install(), add a single line: module_enable(array('path')); to the beginning of that function (approx line 707), so it looks like:
function prosepoint_profile_install($variant) {
module_enable(array('path'));
global $node_table;
variable_set('prosepoint_state', 'install');
3.
Completely clear out your database and restart from anew.
I think I have a workaround. It will involve some editing of PHP code though, so if that sounds too onerous, you might have to find someone to try it for you.
The idea is to not enable path.module until later in the Installation process.
In the file .../profiles/ prosepoint/ prosepoint. profile,
1. profile_ modules( ), at approximately line 597, comment out the line 'path' so it looks like:
In the function prosepoint_
// other drupal core
'contact',
// 'path',
'tracker',
'search',
2. profile_ install( ), add a single line: module_ enable( array(' path')) ; to the beginning of that function (approx line 707), so it looks like:
In the function prosepoint_
function prosepoint_ profile_ install( $variant) { enable( array(' path')) ; set('prosepoint _state' , 'install');
module_
global $node_table;
variable_
3.
Completely clear out your database and restart from anew.
Let me know how you go.
Thank you.