Profit Margin Calculator Conflict with MAP pricing

[johnny roastbeef]

I'm setting up a new store, and I need to be able to track the cost of an item. I don't need a routine to calculate profit margin, I just need to have a field in the product editor to hold my cost. I also need to be able to do MAP pricing in some manner. A lot of the items in this store will have MAP pricing, and unless I can automate the process for a customer to see the actual sales price, those items will never sell.

So here's the issue. First I installed Profit Markup/Margin Calculator add on, and added a few products. It all worked fine. When I was satisfied that was working, I added MAP pricing, and of course, MAP overwrites some of the files that Profit Calculator installed. Obviously I cant have both running simultaneously without re-editing all the php myself.

How do others ensure that they dont delete old add ons when installing new ones. I would guess that after a few months or more, its hard to remember all the modifications made. Also, is there a way to get the dual functionality I need without this conflict?

[stevesh]

How do others ensure that they dont delete old add ons when installing new ones. I would guess that after a few months or more, its hard to remember all the modifications made. Also, is there a way to get the dual functionality I need without this conflict?

1. We check the files in the latest mod to see if we have already modified that file in another mod. If so, you need to compare the two files using something like Winmerge (I use Compare It!) to see where the respective mods altered the file and add (or remove) the latest mod's changes to the previous mod's file. (or vice-versa). Some times this is pretty simple, sometimes it's nearly impossible for a non-programmer.

2. A few months, or the next day - I don't think most of us can trust our memories for those kinds of things. I have a direcory 'tree' for each site I build on my local computer containing copies of all edited files for that store in their proper places.

3. No.