I have been checking expressionengine.com 2 or 3 times a day for news about EE 2.0… Is anyone else doing the same?
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
August 14, 2008 3:48pm
Subscribe [6]#1 / Aug 14, 2008 3:48pm
I have been checking expressionengine.com 2 or 3 times a day for news about EE 2.0… Is anyone else doing the same?
#2 / Aug 14, 2008 4:03pm
I have been checking expressionengine.com 2 or 3 times a day for news about EE 2.0… Is anyone else doing the same?
You’re quietly going mad aren’t you? 😉
But then aren’t we all? 😊
Best wishes,
Mark
#3 / Aug 14, 2008 4:23pm
It’s bad, but I feel with you.
#4 / Aug 14, 2008 5:21pm
I have been checking expressionengine.com 2 or 3 times a day for news about EE 2.0… Is anyone else doing the same?
I’ve been learning javascript just so I can write an applet to do the checking for me automatically. Maybe I can port it into a Firefox extension.
If I ever figure out javascript.
#5 / Aug 14, 2008 5:31pm
‘ve been learning javascript just so I can write an applet to do the checking for me automatically.
Me too - learning JS that is. I’m trying to get it to show me a secret download location for EE 2.0 but to no avail as of yet!! 😉
#6 / Aug 14, 2008 5:44pm
Things to do while waiting for EE 2.0:
1. Back up your databases and those of your clients.
2. Make a list of the plugins, modules, and extensions that you use on your site or others. Contact the authors to see if they will be upgrading their offerings for 2.0.
3. Prioritize which installs will be upgraded to 2.0, and make a to do list for yourself.
4. Evaluate existing plugins, modules, and extensions on a per site basis. Determine if you really need them for that particular site or not. (I know I’ve been guilty of that in the past.)
5. Consider deleting old content if possible. It depends on the site, of course.
6. Relax. 😊 Read a book, find a site to put your first brand new install of 2.0 on.
#7 / Aug 14, 2008 8:02pm
Things to do while waiting for EE 2.0:
1. Back up your databases and those of your clients.
What is this backing up people keep going on about? 😉
2. Make a list of the plugins, modules, and extensions that you use on your site or others. Contact the authors to see if they will be upgrading their offerings for 2.0.
I think I’ll have to contact myself in that case then. Here’s hoping that I can move them all across to 2.0!!
3. Prioritize which installs will be upgraded to 2.0, and make a to do list for yourself.
All of them and there’s another one - To Do Lists? What are these things people keep mentioning 😉
4. Evaluate existing plugins, modules, and extensions on a per site basis. Determine if you really need them for that particular site or not. (I know I’ve been guilty of that in the past.)
I need every plugin out there. I currently have over 300 of them on each site. I just love to scroll!! 😊
5. Consider deleting old content if possible. It depends on the site, of course.
Delete content. Hmm that parts easy. Now how do you get content in the first place?
6. Relax. 😊 Read a book, find a site to put your first brand new install of 2.0 on.
Read? There’s another one. What is that?
Footnote - It’s been a long day so just jesting a bit. 😊
Just like everyone else I can’t wait for 2.0 but know that I have to so do so.
Best wishes,
Mark
#8 / Aug 14, 2008 10:45pm
Hey, Mark! Will you be upgrading your offerings for EE 2.0? 😊 Put the answer in your sig. 😊
#9 / Aug 14, 2008 11:15pm
Ok, so planning my EE 2.0 upgrade is already complete. I have no sites posted live. 😉
I have them all locally to test, I am really just waiting for 2.0 to be released before I post the sites live. The clients really liked them but I do not want to go live now to possibly have a bad upgrade/lose content in a month or two. So I explained the situation to them and now I am just waiting on the 2.0 release to go live. Not saying that I have no faith in Ellis Lab, because I think Ellis is one of the best companies I’ve ever seen… But I think it’s bad business to build the site, give it to my clients and then when they get used to the 1.6.4 control panel… Upgrade to 2.0 and they have to relearn it. It does look fairly simple to use… but there is always that 10 percent rule…
Bottom Line:
For my situation, having no sites live that run EE, it seems like more work to post them and then upgrade to 2.0. So using my sharply tuned Military training attitude… Smarter not Harder.
#10 / Aug 15, 2008 2:31am
No, I am busy earning a living with EE 1.6 😊
#11 / Aug 15, 2008 5:04am
I spend a few pageviews every day to check for news about 2.0, indeed I do : ) .
#12 / Aug 15, 2008 3:19pm
Hey, Mark! Will you be upgrading your offerings for EE 2.0? 😊 Put the answer in your sig. 😊
Hmmm, don’t know about that one - how much are people willing to pay for my natty offerings!! 😉
Can’t really answer as I don’t know how 2.0 works yet but I’m sure I will do for anyone that’s interested. That is once I get someone who needs 2.0 or I can afford to purchase myself.
Best wishes,
Mark
#13 / Aug 18, 2008 1:13pm
Ok, so planning my EE 2.0 upgrade is already complete. I have no sites posted live. 😉
I have them all locally to test, I am really just waiting for 2.0 to be released before I post the sites live. The clients really liked them but I do not want to go live now to possibly have a bad upgrade/lose content in a month or two. So I explained the situation to them and now I am just waiting on the 2.0 release to go live. Not saying that I have no faith in Ellis Lab, because I think Ellis is one of the best companies I’ve ever seen… But I think it’s bad business to build the site, give it to my clients and then when they get used to the 1.6.4 control panel… Upgrade to 2.0 and they have to relearn it. It does look fairly simple to use… but there is always that 10 percent rule…
Bottom Line:
For my situation, having no sites live that run EE, it seems like more work to post them and then upgrade to 2.0. So using my sharply tuned Military training attitude… Smarter not Harder.
There is always the breaking in time for a new version. I’ll be installing locally first.
I test on two different sites:
An existing 1.6.4 site to test upgrades
A new install, to test new installs.
I test what is important to me first. Then I test other aspects of the program.
I test new functionality, bug fixes, and basic functionality. (To make sure new stuff didn’t break old stuff.)
So after a shake down period, I’ll start updating client sites where it makes sense. Some will never need any new functionality.
As far as the backend goes, I’m going to be making some client videos I’ll share. 😊