Make it possible to remove a line in the invoice without everything disappearing.

Definitely not the intended behaviour.

A neater way of doing the lines of the invoice would be to display one line, and add/remove lines via ajax or something similar.

I think this will solve it - but disclaimer, I haven't tested this yet.

Let's see first whether the testbot likes it, then whether it has the intended result.

Making sure this patch is still valid.

#2: storm--758974-2.patch queued for re-testing.

*Bump* for review.

I tried this.

warning: Invalid argument supplied for foreach() in /home/sites/example.co.uk/public_html/central/sites/all/modules/storm/storminvoice/storminvoice.module on line 727.

Everything still disappears.

Needs to be fixed in 2.x first.

Patch for review.

I believe from my tests that this now fixes the issue.

I will wait 1 week before committing to let others test.

As a bug, this would be backported to 1.x.

works for me.

Thanks for the feedback.

Marking for commit.

Committed to 2.x.

Retest on 1.x.

#7: storm--items-07.patch queued for re-testing.

Does not quite (completely) work for me...

I created a test invoice and posted three separate items. First Item I assigned a weight of 1, amount of $1000. 2nd a weight of 2, amount $2000. Then third item a weight of 3, amount of $3000. The printed invoice looked the way I expected.

Then I went and removed the third item (with weight of 3). And it removed that item leaving the other two.

However, when I removed just item with weight # 2 - by removing the description, price and weight - the last two items disappear.

And, starting over again with test items 1, 2 & 3 ... If I remove test item #1 - created 1st with weight of 1, it wipes out all three test items.

Am I doing doing something wrong? Do I need to enable ability to delete items from invoice in a preferences tab somewhere?

dbt102: thanks for testing. It should work out of the box. Did you apply the patch manually or test the 2.x-dev release? Might be worth double checking that the fix was contained in the version you tested - as it worked ok in my tests, which were very similar to yours.

Would you be able to check and report back?

I've retested this using the current 2.x-dev release without any modifications, and the setup described by dbt102 - all seems to now work. I suspect maybe the issue was that the -dev release hadn't been rebuilt when it was tested previously.

Given that, I have also committed to 1.x.