I went from 4.7 to 5.1, then from 5.1 to 4.7. Now I'm back to 5.1.
It's on a test site. Originally in 5.1, I was having problems with Subscriptions and then the patch to Community Tags didn't work. I wasn't sure if maybe I would be going with a Theme only available in 4.7. "Comment Notify" which I was thinking of using was only available in 4.7, etc.
So I switched back to 4.7. But then after a little more work, I decided that I could do without a couple of features at the moment (eg. Community Tags or Taxonomy User, VoteAPI working properly with Views, etc.) and that the advantage lay with 5.1.
So now I'm back again with 5.1.
I figured that once I got Project X into production that upgrades would be far easier.
Going back and forth like this has made be good at:
Doing installations in record time.
Backing up and restoring MySQL Databases in my sleep
'Multi-domain sites' is my middle-name.
Reply
Drupal4libcamp
February 27, 2009, Darien Public Library, Darien, CT
This work is licensed under a Creative Commons Attribution- NonCommercial- ShareAlike 2.5 License.
Now I Switched Back to 5.1!
Yes, I know, schizophrenia...
I went from 4.7 to 5.1, then from 5.1 to 4.7. Now I'm back to 5.1.
It's on a test site. Originally in 5.1, I was having problems with Subscriptions and then the patch to Community Tags didn't work. I wasn't sure if maybe I would be going with a Theme only available in 4.7. "Comment Notify" which I was thinking of using was only available in 4.7, etc.
So I switched back to 4.7. But then after a little more work, I decided that I could do without a couple of features at the moment (eg. Community Tags or Taxonomy User, VoteAPI working properly with Views, etc.) and that the advantage lay with 5.1.
So now I'm back again with 5.1.
I figured that once I got Project X into production that upgrades would be far easier.
Going back and forth like this has made be good at: