There is small issue in the link to backwards compatibility information, it should probably be http://ez.no/download/ez_publish/...kwards_compatibility_for_4_3_0alpha1

There is small issue in the link to backwards compatibility information, it should probably be http://ez.no/download/ez_publish/...kwards_compatibility_for_4_3_0alpha1

Thanks Damien, this is fixed now.

Have a good afternoon !

Hi,

I made a short test for eZ Publish 4.3 beta http://bit.ly/9KpzH7 , on the first view nice, but admin2 should use sprites http://developer.yahoo.com/performance/rules.html#opt_sprites or nice approach http://jqueryui.com/themeroller/ and the sprite:

colored:

http://jqueryui.com/themeroller/i...p;w=256&h=240&f=png&fltr[]=rcd|256&fltr[]=mask|icons/icons.png

or

http://jqueryui.com/themeroller/images/icons/icons.png

Greetings, ekke

For a more optimized admin2 interface, you can use the admin2pp extension [1]. I planned to release a version for this beta this week (I hope...). It overrides the admin2 design to use sprites and some others improvements to improve loading performances.

[1] http://projects.ez.no/admin2pp

Hi Damien,

looks good, there are still a lot of class icons in different sizes :

 

    this.iconsList['article'] = wwwDirPrefix + "mimetypes/document.png";
Greetings, ekke

I know but those images are not used as background but directly in <img /> tags so there's more work to include them in a sprite because you also need to override a lots of templates and change logic in them.

That's why there are only preloaded for the moment in the login page. It's on my TODO list though.

Cheers

Hi,

The eZ publish roadmap http://ez.no/ezpublish/roadmap mentions for the eZ Publish 4.3 release - March 30th, 2010:
AWS support Amazon S3 and Cloudfront native support

Where I can find more info on this?

The eZ publish roadmap http://ez.no/ezpublish/roadmap mentions for the eZ Publish 4.3 release - March 30th, 2010:

AWS support Amazon S3 and Cloudfront native support

Where I can find more info on this?

Hi.

Well, you can view the list of resolved issues by version in the roadmap on the eZ publish issue tracker:

• 4.3.0
• 4.3.0rc1
• 4.3.0beta2

But this will only cover bugfixes. You're left with the sourcecode, and trying the beta / rc versions.

You're left with the sourcecode, and trying the beta / rc versions.

Hi Bertrand,

Could not find anything for "AWS, Amazon S3, Cloudfront" in the source code of ezpublish-4.3.0-beta1-with_ezc-gpl. I've searched and browsed through the "kernel", "lib"and "settings" directories.
Where should I look?

Thanks!

There isn't feature about a new PDF export system ? I waiting this feature with impatience.

There isn't feature about a new PDF export system ? I waiting this feature with impatience.

Have you looked at this extension? http://projects.ez.no/paradoxpdf

Holy crap!

"All menu entries from design tab except Template, has been moved to setup tab".

Where's Template tab?

Answer: "If you want to enable design tab and / or Template link, see menu.ini".

It is one of the most useful admin area, I think it would be enabled by default. It is a big step to a less user-friend admin area.

Modified on Monday 01 March 2010 7:48:35 pm by Thiago Campos Viana

The very last stage of 4.3.0 b1 install ends in a blank page after a 10 second load or so. Both external and included ezc versions were tested. There is nothing indicating a error in php error log or site error log. Server is successfully running number of 4.0 and 4.1 sites. Im at loss, any ideas?

Environment:

Ubuntu 8.04 LTS , PHP 5.2.4-2ubuntu5.6 , mysql 5.0.51a-3ubuntu5.4 , Apache/2.2.8

The very last stage of 4.3.0 b1 install ends in a blank page after a 10 second load or so. Both external and included ezc versions were tested. There is nothing indicating a error in php error log or site error log. Server is successfully running number of 4.0 and 4.1 sites. Im at loss, any ideas?

Environment:

Ubuntu 8.04 LTS , PHP 5.2.4-2ubuntu5.6 , mysql 5.0.51a-3ubuntu5.4 , Apache/2.2.8

Haven't experienced this in our test environments though, but we have tested PHP5.2.12

You could try to increase max_execution_time and/or memory_limit to see if it helps, or try xdebug.

But a blank page usually means a seg fault, which should be reported in apache's error log

Hi..!

I appreciate the hard work put to bring this framework! But I must be honest! Things like removing the most used tab in the site and not even mentioning it on the release notes is absolute rubbish! Why would they remove design tab and shop??? I mean I have to spend hours on hours for every upgrade searching through google results to get what I need is a load of rubbish,

I am very frustrated because I have only installed the new version recently and am already sitting with hours spent on figuring out why the tabs don't work or why the virtual hosts don't work etc etc...

What else have they removed without mentioning. Maybe I should check the most common used feature! I am sure they have been removed in some other ini setting.

Guys come on...!

@Mihai007 Pop

- one user's most used feature is another one's least used; I have never seen a single site where those tabs where in use (except the webshop of course)

- it is mentioned in the changelog; maybe not a very visible place, but upgrading without reading changelog and bc (BINARY COMPATIBILITY) file is your responsibility

Modified on Thursday 04 March 2010 2:21:34 pm by Gaetano Giunta

Mihai,

first, I really think you're overdoing it a bit. If webshop is the most useful feature of eZ publish, something is wrong, isn't it ?

That aside, even though this was not written in the release notes, and that really is a mistake, it is not that hard to find:

• changelog_4_2_0_to_4_3_0alpha1:
  Implemented enhancement #15670: Hide webshop tab by default
  Implemented enhancement #15671: Hide Design tab by default
• There is also a paragraph in the article you commented on (this one ), called "Notes on backward compatibility", that links to this document: backwards_compatibility_for_4_3_0alpha1. In this document, you can see this:
  - Webshop tab hidden by default [...] see menu.ini
  - Design tab hidden by default [...] see menu.ini

Now two more things:

• if you setup an unstable version, do not expect the final documentation, release notes and quality you would expect from a stable version. If you choose to test it, you have to be ready for incomplete feature. So yes, it is good that you are providing feedback about it, but bashing an unstable version instead of trying to be constructive isn't what I, on a personal level, would expect. But that is just me.
• regarding the removal of the webshop tab, the reason is simple, and it is part of a larger change; the webshop, as good as it is, doesn't match everybody's need, and some users like to replace the webshop with their own solution, either completely new, or as an evolution of the existing module. This change will make it possible for these to better integrate their solutions without the default webshop standing in the way.

I hope this helps make you feel better at least a little

The eZ publish roadmap http://ez.no/ezpublish/roadmap mentions for the eZ Publish 4.3 release - March 30th, 2010:
AWS support Amazon S3 and Cloudfront native support

Where I can find more info on this?

You can't, none of the Others ( PDF export, Large File uploa, Flash http streaming, AWS support) parts have been implemented. Thats part of scrum, you take things out if new stuff comes in or takes longer time then expected, like comment system. Unfortunately roadmap page has not been maintained to reflect that.

Modified on Monday 29 March 2010 3:49:11 pm by André R.

ekke: but admin2 should use sprites

It does, and I had actually added a couple of new once and merged some changes from admin2pp for beta1 on 20th of February improving YSlow grading for HTTP requests 2-3 grades..

What we did not do for 4.3.0 and probably will not do when we start to merge admin2pp stuff back to admin2, is to use mega sprites, as in images from all over the place merged into one sprite even if those images comes from completely different components and are totally unrelated.
That would make sense to do on a custom multi million dollar web site, but not the back end where we on top it all try to be expendable / customizable / skinable.

Ref: http://www.smashingmagazine.com/2...ful-technique-or-potential-nuisance/

Modified on Monday 29 March 2010 3:59:03 pm by André R.