After installating the module Commerce_price_table, the admin panel breaks down.
I thought it was this module but after a clean install i tried to install the module path auto and token, and again de admin panels is broken.
And i get also this error after installing a module.
Warning: Illegal offset type in isset or empty in commerce_tax_type_load() (regel 108 van /var/www/commerce/profiles/commerce_kickstart/modules/commerce/modules/tax/commerce_tax.module).
Warning: Illegal offset type in isset or empty in commerce_tax_type_load() (regel 108 van /var/www/commerce/profiles/commerce_kickstart/modules/commerce/modules/tax/commerce_tax.module).
Warning: Illegal offset type in isset or empty in commerce_tax_type_load() (regel 108 van /var/www/commerce/profiles/commerce_kickstart/modules/commerce/modules/tax/commerce_tax.module).
Can someone help me?
Comment | File | Size | Author |
---|---|---|---|
#9 | 1538248-commerce-kickstart-shared-object.patch | 900 bytes | Damien Tournoud |
Comments
Comment #1
philpro CreditAttribution: philpro commentedTo recreate what we're both seeing, do a fresh install of kickstarter, go to the modules page and click 'submit'. After refresh most commerce modules are disabled as well as many core modules. If you try to enable and save again, you get the error below — the site generally implodes on itself and the only thing that loads on the page is the title and a few menu items and tabs. No body content. You cannot load anything —
FieldException: Attempt to create an instance of field commerce_line_items on bundle commerce_order that already has an instance of that field. in field_create_instance() (line 490 of /[...]/site/modules/field/field.crud.inc).
Comment #2
vaccinemedia CreditAttribution: vaccinemedia commentedJust to confirm that this is happening on a fresh vm, fresh kickstart and simply visiting modules and submitting is giving the same error message as above with most of the modules disabling themselves.
Comment #3
Bronwyn Mc CreditAttribution: Bronwyn Mc commentedI have this error too. I've installed this profile successfully just in the past few days. Today I did a fresh new install with the same steps, simple enough. But I received this error after using module page.
Comment #4
Bronwyn Mc CreditAttribution: Bronwyn Mc commentedUpdate: I just did a fresh install with the Zip instead of the .tar and it's working again.If it matters, I'm running a Mac OS 10.7.3 and using Acquia Dev Desktop.Spoke too soon. Went to add install a module and as soon as I save the configuration, the Commerce Modules were all disabled. Tried to re-enable, one by one and save but each time one or another was in turn disabled again.This happens as soon as any other newly installed module is enabled and "configuration" is clicked.
Comment #5
Heorhi Lazarevich CreditAttribution: Heorhi Lazarevich commentedThis is happening for me too on Webenabled virtual hosting with fresh Kickstart after visiting modules page and clicking Save configuration buttom.
Comment #6
Connie Chen CreditAttribution: Connie Chen commentedI have experienced the same problem too. Where is the best place to get help??
Comment #7
knitfreedom CreditAttribution: knitfreedom commentedI am having the same issue.
Comment #8
mikez93 CreditAttribution: mikez93 commentedExact same issue here on clean install of kickstart 7.x-1.5.
Comment #9
Damien Tournoud CreditAttribution: Damien Tournoud commentedWe are hitting a silly case of shared objects. We are tweaking the information generated by the update module so that it returns information that makes sense to the user, but in the process we are modifying an object that is going to be misinterpreted by the modules page. This bug in Drupal core results in all the modules directly required by Kickstart being disabled when you submit the module page. Ooops.
Here is a patch that solves this issue. After applying it (or disabling the update module) you can follow this procedure to re-enable all the standard modules:
profiles/commerce_kickstart/commerce_kickstart.info
file and addhidden = FALSE
at the bottom of itadmin/modules
) and re-submit it (no need to change anything)profiles/commerce_kickstart/commerce_kickstart.info
I'm going to release a Kickstart 1.6 containing this fix shortly.
Comment #10
Bronwyn Mc CreditAttribution: Bronwyn Mc commentedPatch works for me! Thanks!
Comment #11
Connie Chen CreditAttribution: Connie Chen commentedI am new to Drupal and Commerce Kickstart, would you please advise how to apply the patch or disable the update module?
Comment #12
davidmedinamx CreditAttribution: davidmedinamx commentedHi,
I have the same question than Connie Chen.
Where do I have to apply the patch?
I tried on 14 clean installations with commerce kickstart to activate new modules with the same error.
Could you explain how to fix that?
THANKS
Comment #13
Bronwyn Mc CreditAttribution: Bronwyn Mc commentedI applied the patch within the profile folder at; (Sitename)/profiles/commerce_kickstart.
For more about how to apply patches see this page, Applying Patches in Drupal
Comment #14
davidmedinamx CreditAttribution: davidmedinamx commentedBronwyn Mc THANK YOU VERY MUCH
I don't know what I would have done it without your help.
I will still trying to create my own e-commerce site
Comment #15
Damien Tournoud CreditAttribution: Damien Tournoud commentedCommerce Kickstart 1.6 has been released this morning.
Comment #16
Connie Chen CreditAttribution: Connie Chen commentedThanks Damien! That's brilliant! I am happily adding new modules now.
Comment #18
mahesh kataari CreditAttribution: mahesh kataari commentedHello Damien Tournoud,
After I placing hidden = false my site complete looks different. The theme look was disappear and now I am getting many issues.
Thanks.