#2 ednong 13 Dec 2015 15:46

@ednong it looks like a serious html layout issue. Do you use html in your posts and edit it directly?
Can you try to edit it by going to an URL like this: http://example.com/admin.php?ctrl=items&action=edit&p=[postID]&blog=[blogID] ?
Hi mgsolipa,
@mgsolipa wrote earlier:
@ednong it looks like a serious html layout issue. Do you use html in your posts and edit it directly?Can you try to edit it by going to an URL like this: http://example.com/admin.php?ctrl=items&action=edit&p=[postID]&blog=[blogID] ?
there is/was no HTML in it. It was only text and an image. That's all.
I couldn't reach the post, so I modified the database. I changed the status from "publish" to "draft" for this post only. I cannot edit it in the backend, only the delete button will be there. And it seems, that all posts before it (and under this post in the display in the backend) are yellow like the draft status itself has. But it is only in the backend.
And yes, I guess, there is a HTML error which make this confusion. But as I said - no HTML in the post. Crazy.
And now a correction:
this post is on status "draft" and only visible in the backend. If this post is on the page, the sidebar will be under the last post of the page. If the post is not visible - in case of less numbers of post per page for example - all things are okay.
How can I extract the post of the database? Or: in which table the content of the post will be saved?
@ednong the posts' content is saved into the table: evo_items__item
. Look for the field: post_content
and try to see if there is some broken html code in it (maybe introduced by the wysiwyg editor and broken by mistake).
Ok,
I have looked there - nothing broken there. So it is crazy. I have changed its level to misbilled, so I don't see it normally (I filtered this level out).
I only see 3 or 4 words of the content - more are not there. And the delete button. That's all. I have written the the text again in the db field and saved it - no change.
Crazy.
Form is loading...
And now the screenshots.
First in the backend - the only and one option is to delete it: