Apparently that Zend Optimizer issue is fixed in the latest trial. I still don’t understand the encoded trial, what happened to the Core?
My first impressions of EE 2.0 are flat out disappointing. The CP theme is an extremely weak design and it’s actually harder to do even simple tasks. It’s like they made the rarely hard things easier and the normal everyday easy things more difficult. The modules are weak and simply have just a different theme and you’d think after all the time they spent on it that it’d actually be better.
I’m constantly getting coding error notices on the template pages and it says that the weblog:entries tag is not a valid tag and I just think that it’s just not worth it right now.
EllisLab’s seems to be so focused on making money that they’ve dropped the ball. Frankly, that’s just really bad business and you almost wonder why did they destroy a good thing? I’m going to stick with 1.68 till I hear other wise.
I’d be interested to hear Joe’s take on EE and if we’re going to see EE 2.0 actions now that they’ve messed up the way template files are made.
Core has gone. ( Quote: Right now, we’re pretty certain there will be no free Core version of 2.0. http://eeinsider.com/blog/expressionengine-2-week-interview-with-leslie-camacho/ ) Weblog:entrees became channel as far as I know. I still have no trial running here, they answered me yesterday that Zend optimizer has to be present. I myself stopped experimenting. My plan is also to stick with 1.6.8 for my existing (and near future) sites. And maybe switch after a while when the dust has gone.
I tried installing the stupid trial and just got “500 Internal Server” errors. My host is running the old incompatible version of Zend and I’ve asked if it could be upgraded. I’m waiting on their response (it was the weekend, I’m not upset). Even the wizard EllisLab have that tells you if your server is compatible with EE2 threw the same errors. I’m quite disappointed that they didn’t test for the Zend optimizer first and return an error. It would have saved a lot of people a lot of trouble.
The lack of the free Core version is a disappointment. Believe it or not, I did all my initial development of the EE Action Suite on Core. This puts me in a catch-22. If the old methodology of the Action no longer works in EE2, I’ll have to pay for the new version to develop on. However, I don’t know if I’ll be able to get anything working at all in EE2. If that turns out to be the case, I’d be throwing my money away. It’s not a lot of money, but still, I might end up paying $99 to find out there’s no solution.
Yes, I could try to develop against the public beta trial, but I’d be limited to 30 days and you know how that can go.
Dan, if you’re right about the weblog:entries tag, I think that’s another poor judgement on their part. I understand the reasoning behind the name change from weblog to channel. However, if they expect to make the upgrade easy, then they should have provided backwards compatibility with the use of the word weblog. I can replace the word weblog with channel throughout the action, but then that version of the action would only work with 2.0. If that turns out to be the only change that’s needed, I’ll have to see if I can have a toggle so FW users can say which version of EE they are building against in the action.
I’m venting, sorry. I’ll keep you posted on what I find.
There does seem to be a lot of holes in v2 that have me scratching my
head but I’m willing to give them time to work it out since this is
still a beta release. I do think it wise to stick with 1.6.8 for a
It appears the new $99 Freelance license replaced the Core version.
At least in the beta version 2 of EE 2.0, Save Template As Files was changed to this rather rigorous folder structure with a .group suffix on the end and the files ended in .html. Instead of placing the template files by choosing where the template folder was (meaning it’d create a template group folder and then put the template file inside of that like in 1.68), now you chose where you want it to be and then inside of that, after checking ‘Save Template As Files’, it creates this longer folder structure that’d be hard to mimic in FW.
After reviewing the previous posts it appears that this feature of ‘Synchronize Templates’ wasn’t in 2.0b2 and that might explain somethings. However the first way of doing it was and it doesn’t work so well. I still get the group folders and nothing added to the folder I want even though the new template is made for that template group and the permissions are correct.
It looks like my shared host (Have Host) have upgraded the Zend Optimizer version. I’ve been able to successfully install the trial. However, I won’t be able to play with it until next week. But the 30-day countdown has already begun. I forgot about that when I saw the installer was working and excitedly completed the process. Duh.
Hm. I’m still waiting for my ISP…
A caveat for those that want to upgrade to a final build when the stable version has been released. Licence is per build, so once you have upgraded 1.6.8 to 2.1, you loose the licence for 1.6.8 They advise to purchase the so called Freelancer version for testing, and buying a full per project per client.
Quote: “The Freelancer License may only be used for your own professional web presence, and only be purchased by individuals or businesses with three employees or less. You will have to decide whether that describes your situation correctly, or not.” /quote They mean businness there.
I’m not crazy about these new licensing options. There were times when I started early development using a folder on my host with Core while I waited for the client to buy EE themselves, or maybe used it to show them what I can do.
Now, depending on how they incorporate the licensing and the limitations from that, we may not be able to use the copy of Freelancer we have to do a demo site like this.
I guess what I’m saying is that I miss the free Core version.
I agree, Joe. I do miss the Core version as it’s going to be harder to convince a client that this is the next best thing in CMS options, only to have to show them a few versions back. I downloaded the free Core for 1.68 right before they released 2.0, because I had a funny feeling I’d never see her again.
I have a few clients that won’t decide if they want to go this route within the 30 day trial period.
I was just playing around with it a little more. I’m in the CP, but I can’t get anywhere. The buttons along the top aren’t doing anything. I created a new entry, but I didn’t see anywhere that I could actually enter the body of the post. None of the tabs along the top of the Edit Entry worked for me either.
Does anyone have any ideas what’s wrong? I can’t enable save templates as files since I cannot access that page in the CP.
I’m working on it, Joe. My ISP said that on the server Zend Optimizer is running, but the trial fails nevertheless… In the mean time I have made a setup locally with XAMMP. Had no time yet to experiment, shall keep you informed asap.
Strange. My GoDaddy hosting seems to hold it’s own. I ended up getting 2.0 am and messing around with the ‘un-encoded’ version and am trying to adapt my site to run it.
I will admit it’s hard without your actions Joe, but if you cannot even get it loaded and working then I better wind up my egg timer some more until new actions are announced (if so).
While we are here talking about EE. If I create a new DB that is MySQL 5 and I import my existing database (4.1) into that, is that right to do? Should I have installed EE again on a fresh 5.0 DB and then imported my existing 4.1 DB over that? Am I missing out on any 5.0 features installed by a fresh EE install because of my existing 4.1 DB import and is there a better way to do that? I reconnected everything in the path and config files and it works, but I just want to make sure I did it correctly.
I have no idea if it’s my hosting or something in the install itself. I couldn’t find any similar issues reported on the EE forums. It could also be the trial being messed up somehow. Maybe I should see if there are later builds.
AFAIK, MySQL databases don’t change much, the features that change are more in the other bits that access the data. I would also think that if a format change to the data was needed, MySQL would do that or you could tell it to. You may want to check their site and see if they say anything.
I tried both last week on a local install: a clean install using MySQL
v5 and importing a v4 db and I noticed no difference at all. It would
seem to be good either way.
On Dec 16, 2009, at 4:50 PM, Dan J wrote:
If I create a new DB that is MySQL 5 and I import my existing
database (4.1) into that, is that right to do? Should I have
installed EE again on a fresh 5.0 DB and then imported my existing
4.1 DB over that?