Hi Jackson,

It looks like it was cut off, try to click on it and you'll see the entire line, that should how it looks like, right?

I don't think that the composer should load with the post title fully visible as this may present an unpleasant view if the post title is long(http://take.ms/KtMl0).

Why does it use the default editor when I edit it?

Quickpost cannot be stored as built-in composer type, so they are being stored as legacy post.

It will use the legacy editor chosen in EasyBlog. If the built-in editor is selected, the system will use the legacy editor selected at global config.

Hi Raymond,

For the title, fair enough, I see your point.

As to the Quickpost, I see... It's just the switching of editors would confuse end users. Do you guys looking for a way for quickpost to use composer in the future? Or quickpost will never use composer at all?

Thanks,

Jackson

Hey Jackson,

Do you guys looking for a way for quickpost to use composer in the future? Or quickpost will never use composer at all?

Because the built-in composer uses blocks, it is not possible to implement this in the quickpost. Also, using the built-in editor defeats the purpose of the quickpost since authors have to add blocks.

Hi Raymond,

Because the built-in composer uses blocks, it is not possible to implement this in the quickpost. Also, using the built-in editor defeats the purpose of the quickpost since authors have to add blocks.

Well, you are right, no adding of blocks on quick post, that is why it is called quick post. I get that part! What I am saying is when editing a quick post, I guess it is no longer quickpost, right? So, blocks can be added. Logical? No?

Thanks,

Jackson

It is logical in that sense but unfortunately technology these days (especially with the specifications of textarea/textbox in html), there is only so much we can do.

To be able to compute a set of string into it's respective blocks is pretty much suicidal. To be able to render the blocks editor, we store a lot (and I mean a lot!) of hidden attributes on the HTML so that we can retrieve it later to be used on the composer.

Hi Mark,

I think I should say this first: this is just a creative conversation I'm not pushing that you should do what I am saying.

I understand your reason behind composer, but it is brilliant actually, another of your unique ideas which is very very cool! As end user, I don't care how composer works in the background for as long as it works You're talking as a developer and you know the issues that goes with it when coding.

- Quickpost does not use composer block and should not be, hence it's called quickpost. The way posts are saved, is there a difference with how quickpost and composer post are done? Of course composer posts will have extra data like blocks but the basics of saving an entry should just be the same for both right?

- With your statement above, you sounded like you are discouraging a blogger to use composer just because it's too complicated.

- My point is, end users does follow patterns in the UI. As a blogger, when I posts standard entry all the time and a fun of composer blocks it would disappoint me to see standard editor when editing quick post especially seeing it for the first time. Where is the cool editor, why am I seeing this.

- Does quickpost retain a certain behavior right after saving it? Or does it become just an ordinary post?

Thanks,

Jackson

Hey Jackson,

The way posts are saved, is there a difference with how quickpost and composer post are done?

Yes legacy posts and built-in composer posts are stored in a very different manner. As mentioned by Mark, the post content are stored inside the HTML of blocks whereas this is not the case for legacy posts.

After those quickposts are stored as legacy posts, there is no way to load the post with blocks(which the built-in editor does) because the content was not initially created in blocks. Hence, the transition is impossible.

Does quickpost retain a certain behavior right after saving it? Or does it become just an ordinary post?

Quickposts are stored as regular legacy post after being saved.