Front page layout
By George Papadopoulos on Friday, 24 May 2019
Posted in General Issues
Likes 0
Views 568
Votes 0
Hi,
The front page of EasyBlog is displayed as I expected in PC mode, but in tablet mode the result is not what I have been expected
PC layout:

Tablet Layout:

As you can see, in the tablet mode, the cover image has been full scaled to full width of each entry, and the text does not flow around it.
As result the cover photos are too big.
Is there any way to have the table layout like the PC layout?
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

Hm it seems like both tablet user-agent just show this 'Linux; Android 7.0;', so the responsive library treat it as mobile.

Can you try download my attached file and replace into this file location then re-test again?

JoomlaFolder/administrator/components/com_easyblog/includes/responsive/responsive.php (Remember backup this file before you replace it)

Can do me a favor if you tested working correctly?

Because I am not sure whether other browser also use the same keyword 'Mobile' from the user-agent when they view on the website on mobile, and this 'Mobile' keyword will not show on the tablet device based on what you shared us that user-agent data.

1. Try using your tablet device view on different browser and see whether working correctly e.g. Chrome, Firefox, and Safari

2. Try using your mobile device view on different browser and see whether working correctly e.g. Chrome, Firefox and Safari

* If don't have safari app in android phone, then you can ignore this.
Arlex Wong
·
Saturday, 25 May 2019 09:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi George,

May I know what device you are currently using? Because the layout you are seeing is actually applicable for mobile devices or devices with small screen resolutions only.

For tablets, you should see something like the attached screenshot.
Raymond
·
Friday, 24 May 2019 12:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Raymond,
As a case in point, please take a look to the following video:

The tables I use are:
Asus 8''
and
Samsung Galaxy Tab S2 9.7
George Papadopoulos
·
Friday, 24 May 2019 15:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey George,

I would like to know the user agent for these device. In order to retrieve the user agent, can you help us do the following?

The code will render EasyBlog's frontend temporarily unusable. So apply the code at your most convenient time.

1. Place the following code in the following file. https://take.ms/0NI8Vo
JoomlaFolder/components/com_easyblog/easyblog.php
[gist type="php"]
$agent = @$_SERVER['HTTP_USER_AGENT'];
var_dump($agent);exit;
[/gist]
2. Open EasyBlog page in the frontend(on both tablet devices).
3. Copy and paste the result for each device here.
4. Revert/remove the codes placed from step 1.
Raymond
·
Friday, 24 May 2019 16:29
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Raymond,
I followed your instructions:


Then I got the following from Asus:


and the following from Samsung:


I hope that helps you
George Papadopoulos
·
Saturday, 25 May 2019 02:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex,
I followed your instructions and the render works OK.
As an example I post the layout in tablet:


and the layout in mobile device:


I tested the EasyBlog's frontend under the following environments:

1. Windows Phone with Edge
2. Android Phone with Chrome, Edge, Firefox, Opera, Edge
3. Asus tablet 8'': Chrome, Edge, Firefox, Opera, Edge
4. Samsung Galaxy Tab S2 9.7'': Chrome, Edge, Firefox, Opera, Edge

All works fine.

I have a few questions though:
1. Is this a bug of EasyBlog? If yes, will this fix be integrated into the next version of EasyBlog?
2. If it is not considered as a bug, do I have to replace the file 'responsive.php' in case of a new fresh installation of EasyBlog?

As a final note, I would like to say a big thanks to all the team of EasyBlog. Your support is great!
George Papadopoulos
·
Saturday, 25 May 2019 16:45
·
0 Likes
·
0 Votes
·
0 Comments
·
You're most welcome.

And I am very appreciated that you can help me tested all these on different device and different browser.

Yes, we will include this fix in next release version as well if the iOS device also work fine.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.
Arlex Wong
·
Sunday, 26 May 2019 11:23
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post