• Resolved wpsskim

    (@wpsskim)


    Hello.

    While updating from oceanwp 4.0.0 to 4.0.3, there is a bug that does not depend on the inner page background color value of the previous version.

    I am using a child theme.

    The default color is gray, and if you do not publish, it does not change and is only displayed in gray on the custom screen.

    https://drive.google.com/file/d/1GRhn55UgK47ik_qoPaWqNkaE2FRVsNc8/view?usp=drive_link

    It is not a bug that causes a big problem, but I would like to inform you that some WordPress sites have a problem where the inner page background color value depends and does not.

    Have a nice day.

    • This topic was modified 3 months, 1 week ago by wpsskim.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Hello @wpsskim,

    Thank you for reaching out,

    Please share a live URL from the issue.

    I thoroughly examined the issue you mentioned in this topic but couldn’t replicate it on my end: https://postimg.cc/gallery/DkN19BVw.

    Please remember that updating OceanWP alone isn’t enough to get all the new changes—you also need to update the Ocean Extra plugin. Can you confirm that the plugin is updated to the latest version as well?

    Also, please let us know how we can replicate this issue somewhere other than your site. Once we’re able to reproduce it, I’ll work on a solution.

    Best Regards

    Thread Starter wpsskim

    (@wpsskim)

    Hello. @shahin,

    Regarding the above issue, you can see that it occurred in Ocean Extra 2.4.3 and OceanWP 4.0.3 versions, and in OceanWP Child Theme environment, as shown in the image sharing link below.

    https://drive.google.com/file/d/1NbhFygW3vlx3GgYr7Mygukx7KAp_oCJg/view?usp=drive_link

    It affects both the page and the post, so I hope you come up with a good improvement plan.

    Thank you.

    Shahin

    (@skalanter)

    Hello @wpsskim,

    Thank you for reaching out,

    Your screenshots are only from the Customizer, and perhaps because of cache, you can’t see the live preview for that section. Is the issue also present on the front-end?

    Since this issue is not happening on my side, I would like to ask if the new settings are applied on the front-end after you made the changes. After making your adjustments in the Customizer, please save the changes and refresh the Customizer page, then let us know the result.

    I reviewed your previous screenshots, and I didn’t find any issues on my end, but I did recheck the matter.
    Could you also check this on a different WordPress setup, without any caching or CDN? This might help us rule out any potential issues related to caching or delivery networks.

    And one more question, are you using a Child theme? If so, please temporarily deactivate it and test with the Parent theme to see if any customizations are affecting it.

    _______

    It seems it’s a cache issue, if you have any cache plugin or server cache(CDN / Browser Cache and Cookies and …), you need to clear its cache contents or disable them to see your changes.

    To refresh the page, please follow the steps explained in this link:
    https://www.documate.org/automation/what-is-a-hard-refresh-how-to-do-a-hard-refresh-in-any-browser/
    https://www.usmobile.com/blog/how-to-do-a-hard-refresh-on-your-browser/
    To clear cookies, use this icon: https://postimg.cc/0rtp7SS9.
    Summary:
    Win: Ctrl+Shift+R
    Mac: Shift+Command+R

    Clearing all caches depends on the cache at the ISP, which might take time. Alternatively, you can check it on a device that you haven’t used to access your website recently or check your website on a guest browser.

    I hope it helps.
    Best Regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.