M5 Beta 2 is ready.

Before we begin the final stages, we have released the Beta 2 version.

We made various improvements: Worked on UX topics like the page editor, context menu and keyboard shortcuts, but had also a special focus on the iPad version which we polished dramatically. And to make sure we ship not less features as we had in 4.5 we added the deletion process and version/restore.

All that is summarised and demonstrated in the following video.

Now we have 4 weeks left until the release date. We are getting exited ;-)

14 thoughts on “M5 Beta 2 is ready.

  1. For all that want’s to test an update from an existing 4.5 Project. The Data module will ask for a updateDataItemNodeDefinition.py. This is only included in the addons folder of the bundle version.

  2. Tried the latest beta 2 on Mac OS X 10.8.3 with jdk 1.7.0_21. Got a jvm crash as soon as the site update was started after starting the magnolia bundled tomcat.

    The stack is as follows:

    Stack: [0x0000000144a60000,0x0000000144b60000], sp=0x0000000144b4ed90, free space=955k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    C [libjava.dylib+0x934c] JNU_NewStringPlatform+0x1c8
    C [libjava.dylib+0x94c9] JNU_ThrowByNameWithLastError+0x4b
    C [libnet.dylib+0x62fa] NET_ThrowByNameWithLastError+0×64

    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    j java.net.SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[BIII)I+0
    j java.net.SocketInputStream.read([BIII)I+79
    j java.net.SocketInputStream.read([BII)I+11
    j org.apache.coyote.http11.InternalInputBuffer.fill(Z)Z+59
    j org.apache.coyote.http11.InternalInputBuffer.fill()Z+2
    j org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(Z)Z+16
    j org.apache.coyote.http11.AbstractHttp11Processor.process(Lorg/apache/tomcat/util/net/SocketWrapper;)Lorg/apache/tomcat/util/net/AbstractEndpoint$Handler$SocketState;+167
    j org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(Lorg/apache/tomcat/util/net/SocketWrapper;Lorg/apache/tomcat/util/net/SocketStatus;)Lorg/apache/tomcat/util/net/AbstractEndpoint$Handler$SocketState;+158
    j org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run()V+106
    j java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V+95
    j java.util.concurrent.ThreadPoolExecutor$Worker.run()V+5
    j java.lang.Thread.run()V+11
    v ~StubRoutines::call_stub

    • No, it’s a wrong configuration from our part. This rendererClass should be configured by STK (override) and not directly configured by the DAM module. Thanks for the hint.

  3. In my oppinion the fullscreen view of the page editor would be better if it has no grey padding/margin on the left, top and bottom.

    • We’ll take this one step at the time. The current full screen view focuses on making more screen estate available to apps by retracting the header, while still letting you work regularly with apps: you can still open tabs and switch apps without dropping out of full screen view.

      My current plan calls to selectively expand full screen support by not only removing the borders, but also make the Action bar float on top and retracting into the right edge. That’s at least one of the ideas I’d like to verify and test. This won’t make sense everywhere, but it could make quite a difference in editors – I completely agree with you there.

  4. Looks and feels very nice. Two things though:

    1. I would like to see a right-click menu for the configuration tree.

    2. I would also like to see that when I add a new “Property” in the JCR-tree, I would automatically be able to set the name instead of it defaulting to “Untitled”. When I then press Enter (to save the new name) it should automatically jump so that I can set a value as-well. Those two actions are something I actually do a lot and if I didn’t have to use the mouse for that then that would be awesome! :-)

    Also a question: What about STK/Templating-Kit?

    • One more thing, in Asset view if I search for something with a space character in it, for example: “Test Search” then it stucks in an infinite javascript redirect loop on my computer (Uses Google Chrome 27.0.1453.110 for Ubuntu Linux)

Leave a Reply

Your email address will not be published. Required fields are marked *


− six = 1

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>