Update

It is post 575 and I can see it in the DB but it wont work in the front end. The author Shayne gets a 404 error that the post no longer exists so he cant go in and try to publish it again.

I cant make sense of the back end with regard to how to ensure that the latest version is there .

And I guess the other big issue here is that packet loss error when he posted which probably caused all these issues .

Thanks

Update:

I can see that all the revisions are present so something is just causing the system to think blog post 575 doesnt exist

https://vghl.myvirtualgaming.com/mvg-buzz/mvg-stories?view=entry&layout=preview&uid=575.1169

UPDATE:

I tried changing the status of post 575 from 1 to 0 and the status of revision 1174 to 1 from 0 but it didn't do anything.

Hey Fidel,

Unfortunately, I tried to reproduce the issue on your site but so far I am still not able to reproduce instances where the draft goes missing or encounter any packet loss error.

Upon checking the post which you mentioned, I noticed that the intro and content column is empty, which is why currently there is no content in post 575 when you open on of the revision posts: https://www.screencast.com/t/BFBuovuX

However, when I checked the document column, I noticed there is content in there: https://www.screencast.com/t/W7hfnqpBve

Since we are not able to determine the root of the issue currently, we are not able to provide a solid solution. If you or your users experience the packet loss error again, can you inform them to get a screenshot so we can see the error?

Ok we will.

In the meantime can you please fix that post so that it shows?

Thanks

Also could it maybe be because it was so long (34m read time) and had so many revisions? Cou)d this be where the glitch occurred? Or maybe because EB was updated while the post was still being created so maybe it was created as a draft in an older version of EB and then I updated and then the user went back and saw this issue now that it was a new version of EB?

Hey Fidel,

Unfortunately, I believe the post cannot be restored because the content itself is gone.

What I can do is supply you the text content that I have extracted from the raw data that is still in the database and then the author can create a new blog post using back this content. I have attached the text file below.

Also could it maybe be because it was so long (34m read time) and had so many revisions?

I suspect it may be due to the length of the content.

Anyway, I have helped you update the 'document' column in the post table because I noticed that it was not able to store the full content of the post resulting in unclosed tags(https://www.screencast.com/t/oEIHRJw3M7).

I have also helped you apply some codes in the following file to help log post data whenever authors save a post. That way, you can still retrieve the content in the event a similar issue occurs in the future. Basically it will generate a log file in the following directory.
JoomlaFolder/administrator/components/com_easyblog/includes/post/post.php

I was able to retrieve all of the content from all the revisions but it is in its full code so I guess there is no easy way to fix this?

https://docs.google.com/document/d/1vL2S7Pe0MMOCBxisIQSF7cWm-CoSmi3sZDE65EXG-uw/edit

Also, if i ask him to redo it, is he going to have the same issues because it will be long?

Hey Fidel,

Unfortunately, there is no way to properly restore the post. Having data from the revision table is not enough as we also need the proper data in the post table, which currently is empty/missing.

Using the text file which I provided in my previous reply, at least the user can copy back the content without having to retype them.

Also, if i ask him to redo it, is he going to have the same issues because it will be long?

Unfortunately, we cannot guarantee that he won't hit the packet issue because we do not know how the content was created initially(eg block structure etc). Which is why I attached a log generator in the file that I mentioned earlier.

If the user does hit the issue again, this time we will be better prepared when we get the error screenshot and the logged content that was trying to save.

EDIT: By the way, the log file will only work if the post is not published yet. So let your user know to save with drafts in the meantime.

OK thank you. I will use the corrupted data from the revision to properly rebuild it for the author.

Hi

I just spent 2 hours redoing the entire thing myself for the author and it is corrupted. It only posted one of the team write ups (out of 10) and it makes the webpage broken

https://vghl.myvirtualgaming.com/eb-vghl/21-questions-vgnhl-s16-edition

How can we fix this?

I have unpublished it for now because it is very bad. Please feel free to republish so that hoi can see it

I just tried again doing it as one block instead of 30, without images, and it still broke. This is very frustrating as I am trying to encourage the community to create content for me and this is making me look very bad

We just tried as an easyarticle and it also broke

I have other easyarticles that are long and don't break so I can't figure it out. We've never had a long easyblog post so I assumed that maybe it was the length . Seeing the same issue in easyarticles is mind boggling.

Hey Fidel,

I'm not sure what you mean by broken layout. If you are referring to the content being cut off after a certain point, then I am able to reproduce that on your site only. I have also reproduced your blog content in my local instance and the issue does not occur.

After investigating for some time, it appears this issue is occurring due to the emojis in the content: https://www.screencast.com/t/cuBnXlpo

The same issue is occuring in Joomla articles, when I create a Joomla article in the backend with the emoji included, the content after the emoji is stripped when I save the article.

I suspect this is because when trying to store the content into the database, your database do not support/recognize the emoji which leads to the rest of the content being ignored.

This can most likely be solved by changing your database(https://www.screencast.com/t/6Xe8lbzTJXt) to use utf8mb4 collation as this will support the emojis.

However, it looks like you won't be able to do so because your database version is not 5.5 at least.
https://support.plesk.com/hc/en-us/articles/213935405-Unable-to-import-a-database-UNKNOWN-CHARACTER-SET-utf8mb4

Perhaps you can consult your webhosting provider for assistance to upgrade your database version and change it to support utf8mb4?

Amazing guys, thanks so much. I will get on this now and try to fix it.

Have an awesome day!

You're most welcome Fidel.

Let us know how it goes once you have updated your database.