By Joachim B. Auster on Tuesday, 15 December 2015
Posted in General Issues
Replies 18
Likes 0
Views 847
Votes 0
I try to use HTML block, but does not work.
Tried serveral ways the last 45 minutes, now I give up. My time costs my money...
See screenshot attached
Another screenshot about the bad behavement of easyblog using html block
·
Tuesday, 15 December 2015 21:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Joachim,

May I know what version of easyblog you are using currently? Can you provide us with your Joomla backend and FTP access so we can check on the issue directly?
·
Wednesday, 16 December 2015 12:08
·
0 Likes
·
0 Votes
·
0 Comments
·
i can confirm too the missing language string "COM_EASYBLOG_COMPOSER_BLOCK_TEXT_FONT_HEADER"
·
Wednesday, 16 December 2015 15:41
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Noobster,

The language string issue is a known issue and it will be fix in the next release of easyblog.
·
Wednesday, 16 December 2015 16:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Of course, I use the actual newest version of easyblog, wich is 5.0.30
If you want to have access, please tell me where to send to these informations.
·
Wednesday, 16 December 2015 20:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Joachim,

Please edit your original post and include your site details
·
Thursday, 17 December 2015 21:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Did it ;-)
·
Thursday, 17 December 2015 23:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Joachim,

I am really sorry for the delay of this reply as it is a weekend for us here. I have fixed the translation issues that the composer is having but I can't seem to replicate this issue that you have mentioned with the html block. When I tried to drop a html block on the composer, this is what I see http://screencast.com/t/Pk2yk5gE

Can you please let me know how were you able to reproduce this issue?

By the way, if anyone else have similar issues with the language strings appearing on the composer, please download the attached file and upload it into /language/en-GB/
·
Saturday, 19 December 2015 16:24
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

Not sure I should make a new post or use an existing one, but I'm facing the same problem, with easyblog 5.0.31. It's not very recent, but I can remember it didn't happen on some of the first versions of EB5.

It's something you can even reproduce on the demo website. Here are the steps to reproduce :

1) Make a new post, using a blank template
2) Add a HTML block below the text block where there is "Enter your text here"
3) The block is properly added, but doesn't seems to work as intended. On my first picture, the block appears on the block list, but there is nothing else.
4) Select the text block where there is "Enter your text here". The block list on the right is now updated and shows the complete tree. On my second pic, you can see the block list on the right showing a text block, and a html block.
5) Select the html block on the block list. The field to enter your code appears, and the block is properly selected (3rd pic)
6) Type anything on the field. For my example, I typed "<p>This is a text that should appears on the HTML block</p>" (4th pic)
7) Select the text block on the block list again, then go back to the HTML block. The text previously typed disappeared. Works also if you select another block on the composer, or if you click on "Done editing". Basically, it happens if you unselect the block. The code I typed never appeared on the block that is on the composer.

You can still interact with the block, moving it, dropping it, etc... But you can't type anything on it, since it's just deleted when you unselect the block. After that also, there is some weird behavior of the composer when I try to re-add the block, like, It's not added the first time, or It's not displayed immediatly on the block list, and you must click on a block to refresh the list. Am I doing something wrong, or is there a real problem?
·
Wednesday, 23 December 2015 16:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey there,

Hm, I have been testing this on our demo and my local instance but I can't seem to reproduce the issue that you mentioned above. This is what I did,

1. Created a new blank post
2. Inserted a template block beneath the text block.
3. Saved the new template.
4. Closed the editor.
5. Re-opened the editor and clicked on the new template that I saved.
6. I am able to type the contents on the html block and I do see it as well.

Which browser are you using to test this?
·
Wednesday, 23 December 2015 18:07
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark wrote:

Hey there,

Hm, I have been testing this on our demo and my local instance but I can't seem to reproduce the issue that you mentioned above. This is what I did,

1. Created a new blank post
2. Inserted a template block beneath the text block.
3. Saved the new template.
4. Closed the editor.
5. Re-opened the editor and clicked on the new template that I saved.
6. I am able to type the contents on the html block and I do see it as well.


Which browser are you using to test this?


The steps I underlined are different from mine. I tried to do it, and yes, I can't reproduce the issue. So it means that to use the html block, you need first to save a new template, close the composer, then come back on it, using the template previously created?

It sounds weird. Also, if you try to add a html block on the created template, the problem I described on my post will not happen. The block will appears properly and the content will also immediatly appears on it.
·
Wednesday, 23 December 2015 18:30
·
0 Likes
·
0 Votes
·
0 Comments
·
I am not really sure if I understand you here. If you did not reload the composer, how were you able to select the new template that you saved to load it eh?

Did you mean after saving the template, you are hitting this issue?
·
Thursday, 24 December 2015 13:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark wrote:

I am not really sure if I understand you here. If you did not reload the composer, how were you able to select the new template that you saved to load it eh?

Did you mean after saving the template, you are hitting this issue?


I think we're talking about 2 different things. I'm talking about the html block (see my attachment), not about the template.

The problem happens when you choose a blank template, then try to put a html block somewhere on the post. If necessary, I can make a video to show you what's the problem?
·
Thursday, 24 December 2015 16:12
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Philidia,

I am sorry for the delay of this reply. I have just tested this locally but unable to reproduce this issue. Can you please start a new thread and provide the site access so that I can test this on your site?
·
Monday, 28 December 2015 00:43
·
0 Likes
·
0 Votes
·
0 Comments
·
It's possible to reproduce on the demo website. If necessary, I'll provide my site access, but before making a new thread, here is a video that will show you how to reproduce the bug.



Done on demo website. I hope this time it will be easily understandable

If you still can't reproduce, I did it with chrome 47.0.2526.106 on a Windows 10 computer. I'll also send all my site access on a new thread
·
Monday, 28 December 2015 06:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

I am really sorry for the delay of this reply as we have been heavily occupied with the development work of easydiscuss.

May I know what version of easyblog you are using currently? Our demo site are using easyblog version 5.0.28 which is not the latest version and that version is known to have some issue with html block. The fix has already been included in the latest version of easyblog 5.0.31 hence we are no longer able to replicate it in our local instance.

Try to update your easyblog to latest version and see how it goes.
·
Wednesday, 30 December 2015 16:13
·
0 Likes
·
0 Votes
·
0 Comments
·
I'm already using the 5.0.31

I did my video with the demo website because I didn't have access to my website at this moment, but I can reproduce exactly what you can see on the video on my own website. Should I open a new ticket with access to it?
·
Wednesday, 30 December 2015 16:25
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Philidia,

Yes it would be best if you start a new thread and provide us with your joomla backend and FTP access so we can test this out directly on your site.
·
Wednesday, 30 December 2015 16:47
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post