admin2++

Since this extension includes yui_menu.css, it disables the quickfix made for the create menu in this commit:

https://github.com/ezsystems/ezpu...b8a8e0f9c6462bcbdcc184e70a65ffc1e479

Any chances to fix it?

HI Marko,

Thanks for the report. (We definitively need of the bug tracker per project!)

I know admin2++ has some issues with the latest eZ Publish versions... I'm currently in a general movement to update my extensions to make them fully compatible with the latest eZ Publish versions. I released eZ Class Lists 1.2 some weeks ago, I'm working hard on autostatus (I hope to release it before the next week) and admin2pp is the next one on my TODO list...

In the mean time, you can also apply to be member of the project and fix it yourself (I think it's just a matter of synchronizing the CSS in admin2++ with the default one).

Cheers

Ok, did it.

Why is yui_menu.css even included in admin2pp? Couldn't we just remove it and let it use the default one from the admin2?

Hi Marko,

I fixed this issue and some others with the last versions of eZ Publish.

The reason to embed yui_menu.css is because the version from admin2pp brings some performance improvements (sprites, remove useless parth, ...)

Cheers

If it improves performance, then why not push it in the admin2?

I mean, using and maintaining two different versions of the same file is pretty much nonoptimal...

this is more or less the case of a lot of files in the extension (override with some minor changes) because I started this extension before being an eZ Systems employee and before the ability to easily provide contributions to eZ via github.

Btw, some of the changes made in earlier version of admin2pp had been reintegrated in eZ and like the icons-sprite.png use in this style sheet.

Cheers

When this extension is enabled and you go to the admin interface without being logged in (the user/login page is presented), a lot of unneeded .js files are loaded.

Among them also the .js files for OE are loaded and one of them causes a "Request-URI too large" error response. On some servers this triggers security mechanisms that block access from the user's computer.

This issue is also described here:

http://issues.ez.no/IssueView.php?Id=18628

Hi Marko,

<i>When this extension is enabled and you go to the admin interface without being logged in (the user/login page is presented), a lot of unneeded .js files are loaded.</i>

this is done on purpose. The idea is to asynchronously fill the browser's cache while the user is filling the login form (or trying to remember his password ) to speed up the admin interface page loadings.

<i>Among them also the .js files for OE are loaded and one of them causes a "Request-URI too large" error response. On some servers this triggers security mechanisms that block access from the user's computer.</i>

yeah I noticed this issue too, as a workaround, you can remove the guilty JavaScript file from [PreloadSettings]/OEJavaScriptFiles[] array in admin2pp.ini

Cheers

Is this a bug in admin2pp or a bug in ezoe?

From where is this large string generated?

Hi Marko,

I haven't checked in detail yet but it's more an admin2pp issue that comes from a change of behavior in TinyMCE/Online Editor. If I remember correctly, in earlier versions, preloading the JavaScript files in the login page did not generate any issue, it seems like now something is wrongly executed.

Cheers

Any chances to have this fixed?

I would propose a fix, but I have no idea where to start...

P.S. This was tested with the latest admin2pp from the trunk.

And I found what was the problem...

The admin2pp in it's ezjscore.ini.append.php includes jquery-ui-1.8.6.min.js which causes problem becazse jquery is already loaded.

Any chances to fix this?

And I found what was the problem...

The admin2pp in it's ezjscore.ini.append.php includes jquery-ui-1.8.6.min.js which causes problem because is already loaded by ezie extension.

The problem is actually in ezie, I'm making a pull request...

The code is in svn aka subversion. If you a have a svn client you can checkout the code and then export it to get it without the svn files in it. Some clients let you export directly as well.

If your on windows, try TortoiseSVN:

http://tortoisesvn.net/downloads