Closed (duplicate)
Project:
Drupal core
Version:
7.34
Component:
install system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Apr 2013 at 19:01 UTC
Updated:
14 Jun 2018 at 10:02 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
David_Rothstein commentedSee #1170362: Install profile is disabled for lots of different reasons and core doesn't allow for that.
Comment #2
sadashiv commentedHi @zet,
I faced the same issue after upgrading from drupal 6 to 7. On debugging I found that when we install drupal 7 as a fresh install then it makes a entry in system tables as a "standard" module installed with the path of installation profile so the code in install.inc loads it but when we upgrade from drupal 6 to 7 then the standard module status is 0 so it throws error, changing it 1 didn't fix my error.
I made the attached patch as a workaround.
Hth,
Sadashiv.
Comment #3
mskicker commenteddrush rr
worked for me
Comment #4
summit commentedHi,
This is still not incorperated in Drupal 7.34 ... I do not see the duplicated issue somewhere linked to.
I will set this to active and tested by community if this is ok. Otherwise sorry to interfere.
Greetings, Martijn
Comment #5
summit commentedComment #6
mspikes commentedWhen I apply this patch, I get a "Parse error: syntax error, unexpected T_IF in ~/docroot/includes/install.inc on line 207"
Ideas?
Comment #8
David_Rothstein commentedThe issue this is a duplicate of is mentioned in comment #1 (also linking it to it here now, so it's attached to the issue).
Comment #9
johnsonroots.com commentedI am a novice and having this same issue. How do I apply the patch. I have no idea.
Comment #10
dscoop commentedI am getting the same error in Drupal 7.50
Comment #11
kris77 commentedRun this command in phpmyadmin:
UPDATE system SET status=1 WHERE name='standard';
Its same to works.
Comment #12
ronald commentedWhat do I do if there's no row in the 'system' table where name = 'standard'?
Can I create it?
Comment #13
ronald commentedFor the record and in case this helps anyone with the same issue.
What I did to fix this is:
* created a fresh Drupal 7 install, then
* copied the above record from the database (SELECT * from system WHERE name = 'standard';), and
* inserted it into the system table on my upgraded system.