SimplePortal

Development => Feature Requests => Topic started by: gurupreet on May 04, 2015, 10:00:38 AM

Title: ezportal handy feature missing in simple portal?
Post by: gurupreet on May 04, 2015, 10:00:38 AM

Hello,

Ever since that google changed the standards to determine websites are friendly with its search engine or not there major issues with simple portal installed over SMF as the look of the website with simple portal enabled looks all junky.

I tried ezportal and in it there is a handy feature which allows one to disable blocks (portal system) for mobile users resulting in the site being displayed properly over mobile phones and also passing the google friendly test.

I was wondering wether the same can be implemented through simple portal as because of this single reason i had to un-install simple portal from my web site.

Looking forward to answers and suggestions.

Regards
Gurupreet

Title: Re: ezportal handy feature missing in simple portal?
Post by: Rupurudu! on May 04, 2015, 01:50:15 PM

http://simpleportal.net/index.php?topic=13934.msg69009#msg69009

/Themes/default/css/portal.css

Find:

Code: [Select]

body
{
min-width: 750px;
}
Replace with:

Code: [Select]

@media only screen and (max-width: 750px), only screen and (min-resolution: 300dpi) {

#sp_main #sp_left, #sp_main #sp_center, #sp_main #sp_right {
display: block;
width: auto !important;
padding: 0;
}
}


Title: Re: ezportal handy feature missing in simple portal?
Post by: gurupreet on May 10, 2015, 05:05:42 AM

this is a temp solution...what i want is the blocks not to display at all for mobile users

Title: Re: ezportal handy feature missing in simple portal?
Post by: [SiNaN] on August 01, 2015, 08:47:33 AM

By default we just disable the portal functions for those accessing the WAP, WAP2 and IMODE modes. Since there is no consistent built-in function in SMF to detect whether the user is a mobile user or not and we didn't want to include code dedicated for this, we have not included this. Better accommodating the mobile users is certainly something we are considering for the future. I'll be moving this to Feature Requests board.