Hey Gilles,

What do you mean by "move it lower within the text block"? Currently you can only position image blocks on the left or right of a text block.

Hi Mark,
So you mean you can not insert an image starting on say line 4 of a text block such as this (example below)?

jfdksa; fdjsak;f jkfdsal; fjfkdsal; j k;fdsa jkl; jfkdsasl;fd
jfkdla;sfds ajjfkd;a jk; jfkdsa; jfkdsla; fdsajkl;
jkfd;sajfkdas;fkdsa;jfkasd;fjkdsa;fjka ;jk;dsajkf;jk; fasd
-------------
image | jfkdsal;fjdksa;fjkasdlf;jdkas;fjs;j;ddjf
| fkdsal;fjdksa;fjkasdlf;jdkas;fjs;j;ddjf
| fkdsal;fjdksa;fjkasdlf;jdkas;fjs;j;ddjf
--------------- fkdsal;fjdksa;fjkasdlf;jdkas;fjs;j;ddjf

fkdsal;fjdksa;fjkasdlf;jdkas;fjs;j;ddjffkdsal;fjdksa;fjkasdlf;jdkas;fjs;j;ddjf

If what you want to achieve is as above, you should split your contents into 2 blocks?

[text block]
----
[
[image block] [nested text block]
]

So you`re agreeing that is impossible to add an image say halfway through a text block and have the text wrap around it? Just like in JCE and all other editors for instance?

You need to think of composing in a different way rather than thinking of how "JCE" works. This is not JCE and it was not invented to behave / work like JCE. If you want what JCE offers, you can just switch the editor to JCE

It's just the way you compose your blog post. If you need to insert an image in between text, split the text into 2 different blocks

Thanks. I understand.

It's unfortunately a very stringent limitation. Composer was touted as being superior, indeed it does have some nice feature but not having the flexibility of formatting text as in a previous way is a showstopper for us. The main user of the site expected the same/more features with this "composer" editor; not for features to be "taken away".

So... we'll switch back to JCE. Very disappointing.

It's just a matter of how you are treating the composer to compose your blog posts Why would you want to go through the hassle when you can just split the text by different blocks (Which also helps you achieve similar output)?

Simple, because my client wants to have text which wraps around an image when she wants to. The question to you is more, why take away a feature that existed in the previous editing method? Other than that perhaps it posed a challenge for you to implement, I don't see the reason, really.

It's about giving the EB uses flexibility in creating articles. The number One blogging platform is Wordpress and this feature has existed and I'm certain will continue to exist.

I shared this thread with my client and she's as astounded as I as to why you defend this position.
No need to respond. We know your stance although we don't agree with it.

By the way, please don't forget to respond to my other post re: inability to preview posts.
Cheers.

I can't force you or your client to change but we created the composer solely for this reason and we also allow you the option to switch back to the legacy editors should you choose to edit articles using the old WYSIWYG format