• Resolved robahas

    (@robahas)


    Just a comment about this notice:

    style.css is currently stored in /home/nativesp/public_html/wp-content/themes/intuito/style.css, which isn’t upgrade-safe. Please move the stylesheet to /home/nativesp/public_html/wp-content/ngg_styles to ensure that your customizations persist after updates.

    This seems to me a poorly conceived feature. On the one hand, it assumes that all WP themes will be from the repository and possibly subject to future updates. Many WP developers make their own themes which are not updated in this manner, and the warning does not apply to them.

    The solution to add another CSS file is non-ideal, as the goal is to load the least number possible of css files for optimal performance. Also, this solution is out of reach for many non-code savvy users.

    I can understand and appreciate the notice, but for best usability, allow us to dismiss it. I now have a permanent scary sounding notice on every single page of the website that is not actually relevant, and can scare my own clients.

    The solution to this notice can be very time consuming. If you are going to post it, then ideally you would offer a report showing what css controllers on which lines of the css file have triggered it. After all, you have already detected these in order to show the notice in the first place.

    Please let me know if I have misunderstood and this is actually easier to deal with than I realize.

    Thank you

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hello @robahas

    Thank you for letting us know.
    Are you currently using any extra plugins that might generate this notice?

    We need to take some notes and escalate this to our developers
    We may need to deactivate plugins and switch the theme while troubleshooting temporarily. Would you feel OK with that?. If so, please report this issue as a bug using this form: https://www.imagely.com/report-bug/. Be as specific as possible and let them know Gaby referred you.

    We couldn’t find the related bug report in our ticket system.

    Because it has been a month or more since your last reply, I am going to mark this as resolved as I assume you have found a solution. Please feel free to reply again if you still have questions.

    Thread Starter robahas

    (@robahas)

    It’s not a bug report. Its a complaint about how the functionality is conceived. If you don’t want to implement it, that is up to you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘“Update safe notice”’ is closed to new replies.