WordPress.org

Forums

Tiny Forge
[resolved] Responsive not displaying properly in iPad 4 (15 posts)

  1. abu117
    Member
    Posted 1 year ago #

  2. Tomas Mackevicius
    Member
    Theme Author

    Posted 1 year ago #

    I don't have iPad myself, so I only could check with: http://ipadpeek.com

    and it looks normal there :-/

    Could you post a screen shot?

    Is it possible that it's on the left, because of the sidebar? Perhaps sidebar?

    Interesting that for example mobile FireFox renders page in full mobile view, but mobile chrome on the same screen renders same site with sidebar in elastic view.

    P.S. I would consider moving those little images from the left corners somewhere else, because it is not good to interrupt text flow on the left side from the usability point of view ;)

  3. abu117
    Member
    Posted 1 year ago #

    That's interesting. It looks totally ok in iPadgeek.com yet crowded to the left on my iPad (vers 4). This happens in both orientations and the same in Chrome and Safari. I believe I have disabled the sidebar from the site.

    Portrait screenshot
    Landscape screenshot

  4. Tomas Mackevicius
    Member
    Theme Author

    Posted 1 year ago #

    Could you try to disable all plugins (including front slideshow) and check it on clean theme?

  5. abu117
    Member
    Posted 1 year ago #

    The slideshow is the only plugin installed. I have disabled it for now, but no difference.

  6. Tomas Mackevicius
    Member
    Theme Author

    Posted 1 year ago #

    I see that slideshow is embedded inside the pages title (h1). Is the plugin requiring it this way?

    If I have chance I'll check the theme with my friends iPad. If you have access to other devices, please try too, perhaps it is related to an older iOS version?

  7. Tomas Mackevicius
    Member
    Theme Author

    Posted 1 year ago #

    Also could you try the fresh tiny forge theme?

  8. abu117
    Member
    Posted 1 year ago #

    sorry, how do I refresh the theme?

  9. abu117
    Member
    Posted 1 year ago #

    And no, I don't believe it is required to be within the h1 tags

  10. abu117
    Member
    Posted 1 year ago #

    The plugin was within the h1 tags only on the homepage. I changed this, but no difference.

  11. abu117
    Member
    Posted 1 year ago #

    BTW - the version I am using is 1.5.3

  12. abu117
    Member
    Posted 1 year ago #

    And my iPad has the latest iOS - 7.0.4

  13. Tomas Mackevicius
    Member
    Theme Author

    Posted 1 year ago #

    I got that strange behaviour on my Nexus7 tablet with Chrome. But after double-tapping on site it extends. Mobile FF shows good.

    Interesting if you would go to mtomas.com, would you have same behaviour?

    Fresh install: download Tiny Forge theme (you can try new version: http://wordpress.org/themes/download/tiny-forge.1.5.4.zip ), open style.css and change name to Tiny Forge Custom or something like that. Upload theme and activate it.

    Check the behaviour.

    It feels like there are some custom CSS styles that cause this behaviour.

  14. abu117
    Member
    Posted 1 year ago #

    ok. The mtomas.com looks as I would expect - filling the whole screen.

    I will need to research how to install this as I did it before from my cpanel using softaculous.

    I may have made edits to the original style sheet. Is there a way I can get the style sheet only (the original) and over-write it? That may fix what I have done.

    I guess I am afraid of losing all the work I have done if I overwrite the theme?

    As you may have picked up - a bit of a newbie at WordPress :)

  15. Tomas Mackevicius
    Member
    Theme Author

    Posted 1 year ago #

    You can find original css:

    http://themes.svn.wordpress.org/tiny-forge/1.5.4.1/style.css

    In the future, I would suggest using a plugin for cutom css modifications. Plugins are listed here:

    http://mtomas.com/389/tiny-forge-framework-child-themes-comprehensive-guide#Use%20child%20theme%20or%20not

    Just copy your css to some text file, to have it for reference.

    So I mark this as "resolved", because it looks it was caused by internal css rules.

    In any case feel free to post any updates here ;)

Topic Closed

This topic has been closed to new replies.

About this Theme

About this Topic