Hi all, i need to upgrade a template for a client from 4.7 to 5.3.
Swapping old versions of modules with 5.3-compatible ones is pretty straightforward. however, I am not super-confident with php, and this page has me worried:
Can I reasonably expect that if I go through all the template files in /themes/clienttemplate, and replace any of the functions the upgrade node says are new, that the upgrade will work?
what i want to avoid is getting in over my head, or causing the client's site to go down as I scramble to get someone to help me with an upgrade that I can't pull off. Also, i need to give the client a reasonable estimate of how much work the upgrade will take.
thanks!
will
Hello, Will,
RE: "
causing the client's site to go down as I scramble to get someone to help me with an upgrade that I can't pull off."
You should definitely do this work on a test site first, prior to porting the upgrades to the live site. This way, your client always has a presence, and you can test your work at your leisure knowing that his web presence is intact.
Cheers,
Bill will hall wrote:
Hi all, i need to upgrade a template for a client from 4.7 to 5.3.
Swapping old versions of modules with 5.3-compatible ones is pretty straightforward. however, I am not super-confident with php, and this page has me worried:
Can I reasonably expect that if I go through all the template files in /themes/clienttemplate, and replace any of the functions the upgrade node says are new, that the upgrade will work?
what i want to avoid is getting in over my head, or causing the client's site to go down as I scramble to get someone to help me with an upgrade that I can't pull off. Also, i need to give the client a reasonable estimate of how much work the upgrade will take.
thanks!
will
thanks, my plan is to install a sandbox site, thanks for the reminder. if there are any tricks to a 4.7-5.3 install i would appreciate.
this thread is also concerning...
Bill Fitzgerald wrote:
Hello, Will,
RE: "
causing the client's site to go down as I scramble to get someone to help me with an upgrade that I can't pull off."
You should definitely do this work on a test site first, prior to porting the upgrades to the live site. This way, your client always has a presence, and you can test your work at your leisure knowing that his web presence is intact.
Cheers,
Bill will hall wrote:
Hi all, i need to upgrade a template for a client from 4.7 to 5.3.
Swapping old versions of modules with 5.3-compatible ones is pretty straightforward. however, I am not super-confident with php, and this page has me worried:
Can I reasonably expect that if I go through all the template files in /themes/clienttemplate, and replace any of the functions the upgrade node says are new, that the upgrade will work?
what i want to avoid is getting in over my head, or causing the client's site to go down as I scramble to get someone to help me with an upgrade that I can't pull off. Also, i need to give the client a reasonable estimate of how much work the upgrade will take.
thanks!
will
will hall ha scritto:
thanks, my plan is to install a sandbox site, thanks for the reminder. if there are any tricks to a 4.7-5.3 install i would appreciate.
this thread is also concerning...
Hi, I have do it one week ago for my site (www.ziobudda.net). Remember to disable all non core module and follow the UPGRADE.txt file. After the upgrade see drupal's log for any tipe of problem.
M.
I recently did a 4.5.2 to 4.6.11 to 4.7.6 to 5.3 upgrade without having problems by carefully following instructions.
The thread in 114459 is probably because there were a couple of security "point" releases which changed the database, necessitating upgrades to them.
Which version of 4.7 are you on? I'd suggest going to 4.7.6 or better (4.7.7 or 4.7.8) first, before going to 5.3, if you are on a release before 4.7.6, but that's just being extra cautious.
thanks for the advice, i'll take the cautious route!
Chris Johnson wrote:
I recently did a 4.5.2 to 4.6.11 to 4.7.6 to 5.3 upgrade without having problems by carefully following instructions.
The thread in 114459 is probably because there were a couple of security "point" releases which changed the database, necessitating upgrades to them.
Which version of 4.7 are you on? I'd suggest going to 4.7.6 or better (4.7.7 or 4.7.8) first, before going to 5.3, if you are on a release before 4.7.6, but that's just being extra cautious.