Wednesday 18 March 2009 11:14:33 am - 6 replies
André R.
Wednesday 18 March 2009 12:21:37 pm
To old eZ Components versions.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Piotrek Karaś
Wednesday 18 March 2009 12:53:46 pm
Why is an automated component check such a big problem? Why haven't you implemented it yet?
Of course, we could ask why is reading error messages and system requirements such a big problem, but that's whole another story... ;)
Cheers,Piotrek
-- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Wednesday 18 March 2009 2:40:08 pm
This has not been a issue before, as using ezc is quite new you know;)
But yes, it should be a check for it..
H-Works Agency
Thursday 19 March 2009 12:05:57 am
Ok but how this message can be avoid ?
In fact i have ezcomponents-2008.1 but what to do next ?
EZP is Great
Paul Borgermans
Thursday 19 March 2009 12:10:52 am
Hi Martin,
You will need to upgrade eZ Components to 2008.2 (or use the distribution that bundles it)
hthPaul
eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Thursday 19 March 2009 1:20:47 am
I'm sorry, you're right, even though we're used to it since 4.0.0, but I understand components evolve on their own as well.
Anyway, now that eZ becomes more and more eZC dependent, an automated check would save you lots of explaining, I believe ;)
You must be logged in to post messages in this topic!