By Richard on Monday, 02 November 2015
Replies 13
Likes 0
Views 1K
Votes 0
I am adding new blog entries using the Composer on the latest version of EB5.

I have new content that is fully formatted with html that i wish to copy direct into composer.

If it was a Joomla article or custom html module I could toggle the editor content area to the coded section and paste my coded content, then toggle back to see the finished output in a few seconds.

How do I do this in composer (toggle between code and finished output) as I would need access to the code during editing.
Hey Richard,

Actually that was a little bit different with Joomla default editor. Regarding the HTML block, when you edit any content in the right HTML panel, it will display the result immediately, you can take a look of my screenshot below.
·
Monday, 02 November 2015 12:20
·
0 Likes
·
0 Votes
·
0 Comments
·
All the other blocks work for me but not the HTML block (see screencast), it just disappears as soon as it is placed in the blog area.

http://www.screencast.com/t/1hXg8l7Vuk

I have added access details in case you need to check anything, you can use any of the 3 draft posts as they will be changed later anyway before publication.
·
Monday, 02 November 2015 17:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Richard,

It seems like you are using older version of easyblog. We have addressed several issue with html block in version 5.0.30. Perhaps you can try to update your easyblog to latest version first and see how it goes?
·
Monday, 02 November 2015 17:33
·
0 Likes
·
0 Votes
·
0 Comments
·
I had not noticed there was a new update, my apologies.

I tried to update from EB5.0.29 to EB5.0.30 but it is stuck at the download/installation stage (yet again.........i really do dread updates since EB5 and ES1.4 as they never work first time anymore, used to be a 15 second run every time on SiteGround).

I tried all the usual suggestions from the previous support tickets (mine and others with similar update problems) but no success. The launcher and full download options from the dashboard get stuck at the same place as the auto update from my EB5 admin area - the download/installation stage.

I received the following error message (see image) when installing the full version of EB5.0.30 (as happened before but was told to ignore it).

Please fix this recurring update issue as it is becoming very annoying now and i noticed there is a new EasySocial update and it will probably get stuck as well, resulting in another ticket.
·
Tuesday, 03 November 2015 01:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Richard,

I am sorry for the delay of this reply,

I've tried to update your Easyblog to 5.0.30, it seems work fine.

May i know previously how to update your Easyblog in your site?

By the way, can you give it a try click and drag the HTML block into composer is it work fine now?
·
Tuesday, 03 November 2015 12:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you for completing the update to EB5.0.30 Arlex, much appreciated.

May i know previously how to update your Easyblog in your site?


Please refer to the following threads: Easy Social Update and EasyBlog Update and First EasyBlog Update issue

After the update to ES1.4 and EB5 I noticed forum posts about update issues with the admin update process and recommendations to download and update the full package, so that is what I did until it was also causing problems. It became a hit or miss affair each time to update ES or EB, with the process stalling at the same place as today every time.

I would refer to the forum in case of any new solutions, try and update again using the launcher, full package and admin process (all via the network option) and eventually it would work or I would open a forum post and Stackideas support would update for me.

I would also raise a ticket with SiteGround (as I did today, because the site went down with a 500 error after trying to update with EasyBlog and was down until you fixed the update) but SiteGround could not see a quick fix (normally they fix any hosting issue within a few minutes) and needed to turn off all plugins and change the template theme to look at the problem.

I asked them to wait until Stackideas responded to this thread, hoping you could complete the update and allow the site to be visible again (and you did, thank you).

EasySocial now requires an update and I expect the same issue to arise again when I start the process, so it is a common problem for all updates on EB/ES, not just on my site but with other Stackideas customers and is not a hosting issue (SiteGround have never actually had to do anything).

If there is a very slow update speed (instead of the 15 secs it normally takes for my updates) there must be a blockage on the Stackideas server (too many trying to update at once shortly after a release?) that eventually clears when the load on the server falls, allowing a smooth update, or perhaps a different issue blocking customers accessing the server at the correct download speed but not blocking access for Stackideas to perform the same process.

Anyway, that is the background to the issue, it is a puzzle that has not been solved as the update does not work and then works later on or Stackideas support do the update.

By the way, can you give it a try click and drag the HTML block into composer is it work fine now?


I tried to use the html block again on the drafts I created and the drafts you created but it did not work, the same thing happened as in the screencast video on my first post.
·
Tuesday, 03 November 2015 14:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Richard,

You're welcome.

Thanks for take your time described again with you installation process, I will consult with our server administrator regarding this as you mention that is it all the customer update at the same time then causing this issue.

Regarding with your main issue, it seems like something is not right for the compiler, I have temporary set to environment mode to use `development` , can you give it a try now?
·
Tuesday, 03 November 2015 17:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you Arlex.

I tried the HTML block on one of your revision draft posts and it worked. I clicked on 'Apply' and it saved (slowly, but it is development mode so no problem), then save for later and closed the composer.

The draft post automatically posted on the front page even though i did not hit publish (it could be my EB5 admin settings, not sure), so I changed it to unpublish.

You can find the post at ID 40.
·
Tuesday, 03 November 2015 19:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Richard,

I am sorry for the delay of this reply,

We will fix that HTML block issue in next release version.

Regarding with your draft issue, I've tried to edit the content from ID40 post and save as draft it seems work fine for me without auto publish it, you can take a look of my video here and see is it I missed something here?
-> http://screencast.com/t/ljTdZKN7
·
Wednesday, 04 November 2015 12:07
·
0 Likes
·
0 Votes
·
0 Comments
·
It is a slightly different step process that is causing the problem (see screencast):

http://www.screencast.com/t/l9HKKpvlSd

I ran a test on one of the other revisions (Draft Post 2 Apply Only) and it also published.

I ran a test on a completely new post (New Post 1 and Click on Apply) with the Development mode changed back to Static and it also published.

In Draft Post 2 and New Post 1 the process is:

1. Edit Post with title and more than 50 characters.
2. Click on Apply (the post saves)
3. Click on Close in the popup after the save (not return to page)
4. Click on Save for Later (the post saves)
6. Close composer
7. The post is auto published.

(I have changed them back to not published).

I also created a new post (New Post 4) and only clicked on Save for Later and it was fine, staying in Draft mode.

Therefore the problem seems to be if I click on apply to save it, then click on save for later (perhaps I should not do that?)

Feel free to test this with a new post as I can change it and use it as a real post later.

On a different note, as I have ES, EB, ED and K, should I have the settings at optimised instead of static for all components - basically what are the correct settings for each?
·
Wednesday, 04 November 2015 16:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Richard,

Oh actually that `Apply` button is one of the publish purpose but what this `Apply` button task is when the user click on this `Apply` button, it will pop up a message you want to continue modify the post or close it and redirect to post listing.

Seems like this `Apply` button quite confusing, because a few customer already asked for that in our forums, we will discuss with our developer regarding this and see is it can remove this apply button in 5.1 version.

On a different note, as I have ES, EB, ED and K, should I have the settings at optimised instead of static for all components - basically what are the correct settings for each?

Actually that was no correct settings for that, if you set to `static` environment mode, it will loads a single script file containing Foundry & EasyBlog scripts on the Easyblog page, the single script file is generated from Easyblog installation builder, it compile all the Easyblog script file into 1 script file.

So you can just set back to use `Static` environment mode for ED/ES/KT from your site. But since Easyblog HTML block issue, you have to temporary set `development` mode first, because sometime is not right from the script is not passed into single script file, we are still investigate on this and will fix this in next release version.
·
Wednesday, 04 November 2015 17:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you Arlex, the help and explanation is much appreciated, I will use Static mode in EB5 (dev mode for any html block) and wait for the html fix in a later update.

Ref the Save/Apply/Publish buttons, yes you only need 2 buttons, for example:

1. Publish
2. Save

When you click on the 'Save' button, a popup asks do you wish to 'Save and Continue' or 'Save and Exit'. There is no need to include a publish option with Save, the Green 'Publish' button is there for that purpose.

If we do not wish to save any changes made, we just exit the composer without saving.

The apply button can go, it does not serve any useful purpose.
·
Wednesday, 04 November 2015 22:05
·
0 Likes
·
0 Votes
·
0 Comments
·
You're welcome Richard

Thanks for your feedback, I will discuss with our developer regarding this user usability as well.

I will mark this thread as resolved and lock it to avoid any confusions in the future, but if you need any help please feel free to start a new thread in our forums.
·
Wednesday, 04 November 2015 23:00
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post