Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #1122329

    Dear Kriesi Team,

    As mentioned in this thread the problem of elements like slideshows not been shown in Explorer with the enfold version 4.5.7 *) was solved for the live site with version 4.5.7.1-beta-3, however the problem aggravated for the staging site.

    After I installed the beta version on the staging site, the slideshow and an embedded (script) page are not shown on Firefox, Explorer and Chrome (others I did not test). The problem includes the issue of the phone icon at the top not being shown correctly.

    As far as I know the staging site is an exact copy of the live site apart from the password protection.

    So the problem is less urgent now (i am not planning big changes for which I need the staging site), however, it has the potential to become even more urgent if the live site would start to show the same behaviour as the test site.

    Best regards,

    Jan

    *) or as I jumped from 4.5.2 to 4.5.7 any version after 4.5.2.

    #1122756

    Hey Jan_FtFA,

    Thank you for using Enfold.

    We updated the header.php file in the child theme and it seems to have fixed the issue. Please remove the cache prior to checking the page.

    Best regards,
    Ismael

    #1122771

    Dear Ismael,

    Thank you for reply and update to the staging site. The staging site is indeed working again as it should. I checked FF, Explorer and Chrome.

    However it raises an obvious question: why does the live site not have this problem although it had the same header.php? Clearly it is a combination of factors of which (at least for me) one other factor is unknown.

    Some other observations:

    • Today on both the live and the staging site it says that there are 2 updates available and 1 plugin update. When I check: no update is actually showing. (I had a similar problem before but that was resolved with entering the Envato private token). However, as this issue is the same for both sites is is likely to be not related.
    • On the live site the ‘All in One SEO’ option is shown in the menu right under ‘Dashboard’ but it is missing on the staging site, although the plugin is installed on both sites. As this is a difference between both sites, it might be related.

    Also please note that the malfunction was different: only Explorer affected verses all browsers affected.

    So in other words:
    1. What causes the difference in behaviour between both the live and the staging site?
    2. Why is the ‘All in One SEO’ option not shown anymore? (possibly induced by the change to header.php?)

    Best regards,

    Jan

    • This reply was modified 4 years, 8 months ago by Jan_FtFA.
    #1123021

    Hi,

    Thank you for the update.

    Are you sure that they have the same header.php file? Did you update the header.php file of the staging version right after upgrading the theme? We didn’t do anything aside from updating the header.php file.

    Best regards,
    Ismael

    #1123629

    Hi Ismael,

    I have not made any changes to header.php. I also checked the header.php file from the live site versus a back-up from July 24 of the staging site and I see no difference. However, strangely enough if I restore the header.php from this back-up I am not able to reproduce the error.

    I noticed 4 changes in the header.php:

    • the line commented out <!– <meta name=”theme-color” …. was removed
    • onload=”preloader()” was removed from the body tag
    • php script “/** *WP 5.2 add a new function – stay backwa…” was added
    • php closing tag “?>” was removed.

    I assume all these changes were made by you. Am I correct?

    There is a differences though in the functions.php: between staging and live site. On the staging site I used a script (from this site) to check for plugin update errors. I don’t see how this can be related, but I just mention it FYI. (Please note that I included the functions.php file in the check to reproduce the error).

    I also noticed that in the functions.php the line “wp_register_style ….” was commented out, which I assume you did just prior to changing the header.php. Is my assumption correct?

    Furthermore, I noticed that on the home page of the staging site a <br> tag went missing most likely in the process of restoring the staging site from a back-up as part of trouble shooting this whole issue. I noticed a similar issue with an other site lately on the same server, so I start to doubt the integrity of Installatron.

    So because I can not reproduce the situation and because I have to put a question mark on the back-up/restore/clone process of Installatron, I think there it is no use to further pursue this issue.

    Or.. how do you see it?

    So I would like to know if you did indeed make the changes as I describe here (to rule out any other “interference”) but apart from that I think we better stop this thread unless you have a new and fresh idea about this situation

    Best regards,

    Jan

    • This reply was modified 4 years, 8 months ago by Jan_FtFA.
    #1123842

    Hi,

    Thank you for the update.

    I assume all these changes were made by you. Am I correct?

    We didn’t modify the header.php or the functions.php. We just updated the header.php file because based on experience users usually forget to update the template files in the child theme after the upgrade. We didn’t do anything else. And more often than not this helps fix some issues.

    Let us know if we can close the thread.

    Best regards,
    Ismael

    #1132329

    Hi Ismael,

    Sorry for the late reply. The situation is kind of strange, but it is very hard to trace everything back.
    Main thing is that the initial problem (some elements not been shown) is solved.
    So yes, please, close the thread

    Best regards,

    Jan

    #1132352

    Hi,

    If you need additional help, please let us know here in the forums.

    Best regards,
    Jordan Shannon

Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘Parts of website not shown – problem aggravated’ is closed to new replies.