Text and images too narrow from mobile

@themeansar can you please help me to solve this problem? thank you!

Hi,

Thanks for contacting us,

For this remove the below css code in additional css filed, then check your website

.mg-blog-post-box .small.single {
    width: 55% !important;
    margin-left: auto !important;
    margin-right: auto !important;
}

Thanks

Hi @themeansar , many thanks for your reply!

I removed that additional css filed (I used it to vertically align text and images), but nothing happened in the mobile version of the website. Do you have any other CSS code to solve this problem?

Furthermore, do you know how can delete word “Category” from category page? https://ibb.co/3CvLkry I’d like just to remove “Category” and leave it in place “Comprare Casa”.

Thanks in advance and happy Easter!

Hi,

We have removed the code and its working perfectly at our end, please clear cache then check your website,

you can check below screenshot link: https://prntscr.com/11375ty

Remove the category name add the below css code in additional css field

.mg-breadcrumb-title h1
{
display: none!important;
}

And if you remove whole breadcrumb add the below css code in additional css filed

.mg-breadcrumb-section
{
display: none!important;
}

Any confusion lets know

Thanks

Hi @themeansar many thanks for your help. I think there is a misunderstanding: the problem is that text and images are too narrow from mobile view (only from mobile, not desktop) please find here a screenshot of how a post appear in mobile version (please see screenshot here https://prnt.sc/1137wtp).

I tried to delete cache and try again with other browsers and other devices, but the problem persist.

many thanks!

Hi,

Fixed your issue, please check your website,

Any confusion lets know

Thanks

@themeansar If you ask for login access again to a user’s site, you may be banned from these forums. I have archived your reply and flagged your account for moderation.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

Hi @jdembowski,

Thanks for your suggestion,

For this we apologize, no further login access will be sought from any user.

And the user will be reprinted on the suggestion given by you from now on.

Again sorry for this

Thanks