Able 7.0.4 Proper Patch Sequence
Able 7.0.4 Proper Patch Sequence
Purchased 7.0.4 last week and wanting to know proper patch sequence for clean install on Windows Server 2008, IIS7, SQL 2008.
the release is ac_7_0_4_stable_b13424 of course
there is also a link to CommerceBuilderSource_704_PayPalPatch folder with 2 subset folders: 13453 and 13454 AND
there is the new Service Release: AC704_SP1_13936
So my question is:
Will the Service Release take care of the PayPalPatch as well or do I need to apply that first and if so which folder (13453 or 13454) do I apply before moving onto the SP1 Service Release?
the release is ac_7_0_4_stable_b13424 of course
there is also a link to CommerceBuilderSource_704_PayPalPatch folder with 2 subset folders: 13453 and 13454 AND
there is the new Service Release: AC704_SP1_13936
So my question is:
Will the Service Release take care of the PayPalPatch as well or do I need to apply that first and if so which folder (13453 or 13454) do I apply before moving onto the SP1 Service Release?
Re: Able 7.0.4 Proper Patch Sequence
Where is the link to PayPalPatch? If its download is provided in bug system then see its Bug# and then try to locate it in Service Release 1 A change log. If change log has bug number in it then it means that changes are present in service release.
Re: Able 7.0.4 Proper Patch Sequence
Well it came along with my order in a separate zip file and contains 13453 and 13544 folders and were sent with the AbleCommerce 7.0.4 purchase last week. I don't know or understand them. Perhaps you can guide me to more information on this?
Thanks much,
Phil
Thanks much,
Phil
- Shopping Cart Admin
- AbleCommerce Admin
- Posts: 3055
- Joined: Mon Dec 01, 2003 8:41 pm
- Location: Vancouver, WA
- Contact:
Re: Able 7.0.4 Proper Patch Sequence
Hello Phil,
The source code file isn't needed for the install, that was attached to your order because you purchased the source. (I've remove the source file from your post as it shouldn't be retransmitted in any form per the license agreement). Just install 13424 and apply the service release.
The only reason you'd need the paypal source is if you'd (or will be) customized the PayPal module in your B13424 source.
The source code file isn't needed for the install, that was attached to your order because you purchased the source. (I've remove the source file from your post as it shouldn't be retransmitted in any form per the license agreement). Just install 13424 and apply the service release.
The only reason you'd need the paypal source is if you'd (or will be) customized the PayPal module in your B13424 source.
Re: Able 7.0.4 Proper Patch Sequence
Mike,
Thank you for quick response and for taking down the file. I really thought it was a simple PayPal patch as the file indicated. The 7.03 and 7.04 stores are running great for the new clients.
Thanks,
Phil
P.S. Where can I obtain one of those cool avatars?
Thank you for quick response and for taking down the file. I really thought it was a simple PayPal patch as the file indicated. The 7.03 and 7.04 stores are running great for the new clients.
Thanks,
Phil
P.S. Where can I obtain one of those cool avatars?
- Shopping Cart Admin
- AbleCommerce Admin
- Posts: 3055
- Joined: Mon Dec 01, 2003 8:41 pm
- Location: Vancouver, WA
- Contact:
Re: Able 7.0.4 Proper Patch Sequence
Hello Phil,
It's in the 'User Control panel' which is in the upper left of all the pages in the forums.
ucp.php?i=profile&mode=avatar
It's in the 'User Control panel' which is in the upper left of all the pages in the forums.
ucp.php?i=profile&mode=avatar
Re: Able 7.0.4 Proper Patch Sequence
Oh yeah, I know that. I am more interested in the actual image source. I will find one to challenge the green one eye.
Thanks,
Phil
Thanks,
Phil
-
- Lieutenant, Jr. Grade (LT JG)
- Posts: 47
- Joined: Thu Jun 03, 2010 1:48 pm
Re: Able 7.0.4 Proper Patch Sequence
I have a related question and apologize if I misunderstood some of the earlier posts:
We just purchased 7.0.4 as well along with the CommerceBuilder source and also got the PayPal patch along with the CommerceBuilder source package.
Since we'll have to implement a truckload of modifications to the code for integrations and additions (likely some to the CommerceBuilder source) that will be deployed over time to several dozen customer sites, I need to have very clean version control for both the website code as well as the associated CommerceBuilder file revisions. I am working on getting the code organized for the initial import into Subversion so I can tag/branch it for future updates and customization work with possibly multiple developers working in parallel. If I don't get this cleanly set up, future merges will be disastrous.
In our processes it is very important that development site(s) for code changes are directly linked back into the repository, i.e., a development website is running in an actual sandbox so developers do not have to copy/paste files all over the place.
To allow for tagging across the whole code base in one action (to logically link both website code and associated CommerceBuilder files) we were planning on placing the website code into the folder "Website" in the CommerceBuilder source folder. Since that has a Bin folder with the dlls' delivered with the source they will be overwritten by the Website and SP1 basecode DLLs. And that seems like a dangerous thing since the versions in the CommerceBilder/Website/Bin folder do not go along with the DLL versions from the base 7.0.4 or the SP1 (example CommerceBuilder.dll). Could you please let me know how to best handle this?
Another thing that puzzles me is that the CB Source PayPal patch has two "patches" that clobber each other and the order.cs file modifications dates in the first are *before* the modification date of the full base code package while the other one is after that. Which one needs to be applied in which order to the source code directories to have the correct code that corresponds to the DLL needed on the website?
Here are some other minor questions. Please forgive me if I miss something really obvious.:
1. I assume the numbers (13453 and 13544) are build numbers, not bug numbers? Is that assumption correct?
2. How can this be linked back to Issue [bug] numbers?
3. Why are both builds included in the patch? Is there any reference anywhere which product release/SP/Issue fix they belong to? I would assume that one of the folders corresponds to issue 8663 but what about the other?
Checking the SP1 files, I can see that the build of CommerceBuilder.PayPal.dll is 13453 as well, so I'd assume the PayPal patch folder 13453 corresponds to the dll delivered in SP1. So, what is 13544 in the PayPal patch? The file's modification dates are from back in January (12 and 29). Is that code not included in SP1 and if yes, why?
As you can see, I've been very successful in driving myself nuts here and as long as I don't get the code into Subversion we can't get our code changes managed with any degree of process. Can somebody please help?
Your patience and support for a complete "Newbie" is greatly appreciated! I hope to pass these growing pains very soon and hopefully we'll be able to contribute positively in the future as well.
Best Regards and Thanks in advance,
-- Karin Stevenson
We just purchased 7.0.4 as well along with the CommerceBuilder source and also got the PayPal patch along with the CommerceBuilder source package.
Since we'll have to implement a truckload of modifications to the code for integrations and additions (likely some to the CommerceBuilder source) that will be deployed over time to several dozen customer sites, I need to have very clean version control for both the website code as well as the associated CommerceBuilder file revisions. I am working on getting the code organized for the initial import into Subversion so I can tag/branch it for future updates and customization work with possibly multiple developers working in parallel. If I don't get this cleanly set up, future merges will be disastrous.
In our processes it is very important that development site(s) for code changes are directly linked back into the repository, i.e., a development website is running in an actual sandbox so developers do not have to copy/paste files all over the place.
To allow for tagging across the whole code base in one action (to logically link both website code and associated CommerceBuilder files) we were planning on placing the website code into the folder "Website" in the CommerceBuilder source folder. Since that has a Bin folder with the dlls' delivered with the source they will be overwritten by the Website and SP1 basecode DLLs. And that seems like a dangerous thing since the versions in the CommerceBilder/Website/Bin folder do not go along with the DLL versions from the base 7.0.4 or the SP1 (example CommerceBuilder.dll). Could you please let me know how to best handle this?
Another thing that puzzles me is that the CB Source PayPal patch has two "patches" that clobber each other and the order.cs file modifications dates in the first are *before* the modification date of the full base code package while the other one is after that. Which one needs to be applied in which order to the source code directories to have the correct code that corresponds to the DLL needed on the website?
Here are some other minor questions. Please forgive me if I miss something really obvious.:
1. I assume the numbers (13453 and 13544) are build numbers, not bug numbers? Is that assumption correct?
2. How can this be linked back to Issue [bug] numbers?
3. Why are both builds included in the patch? Is there any reference anywhere which product release/SP/Issue fix they belong to? I would assume that one of the folders corresponds to issue 8663 but what about the other?
Checking the SP1 files, I can see that the build of CommerceBuilder.PayPal.dll is 13453 as well, so I'd assume the PayPal patch folder 13453 corresponds to the dll delivered in SP1. So, what is 13544 in the PayPal patch? The file's modification dates are from back in January (12 and 29). Is that code not included in SP1 and if yes, why?
As you can see, I've been very successful in driving myself nuts here and as long as I don't get the code into Subversion we can't get our code changes managed with any degree of process. Can somebody please help?
Your patience and support for a complete "Newbie" is greatly appreciated! I hope to pass these growing pains very soon and hopefully we'll be able to contribute positively in the future as well.
Best Regards and Thanks in advance,
-- Karin Stevenson
Re: Able 7.0.4 Proper Patch Sequence
Hi Karin, since we seem to be on the same page. I would love to offer my help and perhaps MasterMind together on building our respective stores? I could use some "mind share". I have a Go To Meeting license.
All the best,
Phil Chrisman
312-446-8993 cell
All the best,
Phil Chrisman
312-446-8993 cell
-
- Lieutenant, Jr. Grade (LT JG)
- Posts: 47
- Joined: Thu Jun 03, 2010 1:48 pm
Re: Able 7.0.4 Proper Patch Sequence
Hi Phil!
That sounds marvelous. My internet provider, in their infinite wisdom, have knocked me back to dial-up again this morning, so I'm just limping along right now. I'll give you a call later when I'm back up and running . Hopefully, it won't take too long. I really need to get this code imported today. I'm on MDT time.
Thanks again and talk to you later!
-- Karin
(505-231-3130 cell)
That sounds marvelous. My internet provider, in their infinite wisdom, have knocked me back to dial-up again this morning, so I'm just limping along right now. I'll give you a call later when I'm back up and running . Hopefully, it won't take too long. I really need to get this code imported today. I'm on MDT time.
Thanks again and talk to you later!
-- Karin
(505-231-3130 cell)
Re: Able 7.0.4 Proper Patch Sequence
There was an error in the patches for normal search or product finder so just to keep the posts accurate refer to here as well.
viewtopic.php?f=42&t=13869
Good Luck,
Phil Chrisman
viewtopic.php?f=42&t=13869
Good Luck,
Phil Chrisman