So I read the previous post which was caused by a memory issue.

I am getting a

"Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request."

On the server log, I have the error "Premature end of script headers: index.php"

I've only been working with this module, here is what I did leading up to this.

1. Created a line-item type with custom line items. Ticked for the fields to be available on add to cart form.
2. Created a product-type
3. Created a product.
4. Created a product display type and under manage display referenced the custom line-item that I created in step 1.
5. Created a product display.
6. Added item to cart.
7. Clicked on cart
8. Got error.

Any ideas on what this might be?

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

There was an error yesterday when adding to cart. If you're using the packaged dev version perhaps it's not the latest.

Use git to grab current, or wait for the repackaging (every 12 hours). Or, if you still have an old version (old == yesterday :-) then get the latest dev.

ryan.ryan’s picture

ryan.ryan commented

Ah okay, well I just installed the module this morning. But I can give this a shot anyway.

ryan.ryan’s picture

ryan.ryan commented

Okay, disabling the module fixed it. I'm going to try the latest release to see if that was indeed the problem.

willkaxu’s picture

willkaxu commented
Priority: Normal » Major

I've tested it in my local site, just installed the modules required by Commerce Custom Line Items (Types). The Drupal core is 7.9.
The same steps after installing the latest release, click the cart, it still worked. But after clicking "your cart", I got the 502 server error.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

I'm able to replicate this now, so should be able to sort it out.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Fixed

Oh dear.

I am so sorry.

The two important commits that I knew fixed this yesterday never got pushed.

Apologies to all.

You should be able to pull from git now, or it will be repackaged in the dev release within 12 hours.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

I recommend this procedure:

1. Disable Commerce Custom Line Items
2. Uninstall Commerce Custom Line Items (This will remove all traces of the configuration)
3. Enable it

Then begin the configuration process again. The field you created earlier will still be available to place on the new custom line item. Don't forget to configure the display settings of your content type to use the newly created line item.

I recommend not using the same line item type name you used before (as you still have a couple of those perhaps laying around)

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

Alex writes on Commerceguys.com:

Trying your approach, I'm facing a WSOD caused by an infinite loop when viewing a cart containing a donation line item. My custom line item type tries to load its title with a wrong callback : commerce_line_item_title().
A quick and dirty fix is to alter the field "base" in the table "commerce_custom_line_items_commerce_line_item_type" from "commerce_line_item" to "commerce_product_line_item" in order to use callbacks of the built-in product line item type.
I suspect this bug belongs to the custom line item module, but I need more research to affirm that...

I suspect just fixing base as he suggests is the way to fix any existing line item types that were created with the bad module.

Gauntlet-1’s picture

Gauntlet-1 commented

Just as a suggestion, I think the date of the version might be an unreliable way to refer to versions. I was logged out, and saw it as Nov 2. When I logged in, I saw it as Nov 1.

alex.druhet’s picture

alex.druhet
Primary language French
Location Toulouse
commented

Thanks Randy for pushing up my quick fix!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.