WordPress.org

Ready to get started?Download WordPress

Forums

NextGEN Gallery
How to disable warning message? (10 posts)

  1. Logico7
    Member
    Posted 9 months ago #

    Hi! How can I disable following warning message:

    WARNING: NextGEN Gallery Stylesheet NOT Upgrade-safe

    I already really hate it! I don't want to move my css file. I want it to be with my other theme files!

    http://wordpress.org/plugins/nextgen-gallery/

  2. tizz
    Member
    Posted 9 months ago #

    Put the nggallery.css in /wp-content/ngg_styles/, it will be safe and the message will disappear.

  3. photocrati
    Member
    Plugin Author

    Posted 9 months ago #

    @tizz - Thanks!

    @Logico7 - The placement of the custom CSS file where @tizz suggested protects it from being removed with a theme (in your case) or plugin update.

    - Cais.

  4. Logico7
    Member
    Posted 9 months ago #

    As I already wrote I don't want to move it. I need it only in one theme and I want it to be stored there. I just want to disable this annoying message.

  5. Dave333
    Member
    Posted 8 months ago #

    My NGG style sheet is in my Child theme folder and as such it is impossible for it to be overridden with any updates. This is whole point of Child themes and is standard practice as advised in the Codex. Yet I am still being told that it is not upgrade safe. The message is also telling me to move it to a folder that doesn't even exist.

    It seems that NextGen are trying to reinvent the wheel for those who are sloppy or ignorant of how to follow the standard rules of creating a WordPress website (i.e. using Child Themes). This seems like dangerous behaviour. Why cater for people who are not using WordPress properly? This will only encourage more sloppy installations of WordPress. Does anyone really want that?

  6. tizz
    Member
    Posted 8 months ago #

    @Dave333, if you want to put the Nextgen style in your child theme's style sheet you're free to do so, as you are free to do it for any style.
    The message warns to not to move the file, it don't say that you can't do the Nextgen style directly in your child theme's style sheet.
    Simply copy the content of your custom Nextgen style (not the file, and not the header, only CSS) and paste it where you think it's the best place in your child theme's style sheet.
    In the Nextgen CSS custom area then you can delete the style that you may have put inside, save and, puff!, message disappear, and STOP.
    If it's not clear:
    Leave custom CSS area as you find it, with only the header, don't move any file and there will be no message, you write your style directly into your child theme's .css.

    Then you say that the folder does not exist. The folder is created when you fill the area and save, if there are permissions on wp-content the folder and the file will be created in wp-content directory.
    Once you have created you can't delete it, but you can leave the file empty if you don't use it, and it will not bother you.

    Lastly, the error message is generic, it recognizes a theme (a child-theme is a theme), and it says it's not safe for your safety.
    We all know that the child theme is safe and that is a standard practice.
    Custom CSS area in back-end can be useful for those who don't use a child theme, or for anyone who prefer make changes from the back end.
    If you don't want to use it, don't use it.
    I understand that the 2.x versions have had so many problems, but yours is a non-problem, and speaking of "dangerous behavior" for such a thing it seems to me not only exaggerated, but completely out of place.

  7. Dave333
    Member
    Posted 8 months ago #

    Actually tizz, the warning does very clearly state that the entire css file needs to moved out of my child directory, which it wrongly claims "isn't upgrade safe". Files in my Child directory are safe, contrary to what warning messages alerts.

    The folder certainly does not exist, again, contrary to the alerting statement's claims. You gave instructions on how to generate that folder, but the wanring says nothing about having to create the folder. Instead it refers to the folder as if it already exists. The folder does not exist unless you follow the steps you gave or create it manually. How are users supposed to just automatically know that?

    You wrote:

    Lastly, the error message is generic, it recognizes a theme (a child-theme is a theme), and it says it's not safe for your safety.
    We all know that the child theme is safe and that is a standard practice.

    Exactly. You are correct in stating that the warning message falsely claims that the contents of my Child theme folder is not upgrade safe. This is exactly the point I was making - the plugin should not incorrectly tell people that their Child themes are not upgrade safe when they in fact are upgrade safe. This goes against standard practise as described in the Codex as you just acknowledged. WordPress users are encouraged to use Child Themes because they ARE upgrade safe. That's the whole point of using Child Themes.

    For this plugin to tell people that Child Themes are NOT upgrade safe not only adds confusion to the user, it goes against standard WordPress practice. You say it's a generic message, but if the standard practise stated by the WordPress Codex to use Child Themes then Child themes are the norm, not the exception, and so this generic message is going to be wrong more often than not by assuming that users are NOT using Child Themes.

    This plugin has caused many people a huge amount of problems and my concern is for new WordPress users, not myself. I have removed it from all but one of my client's websites but will remove it from that final one next time I am asked to work on it.

  8. tizz
    Member
    Posted 8 months ago #

    The folder does not exist unless you follow the steps you gave or create it manually. How are users supposed to just automatically know that?

    With two messages above the area:

    - "You could edit this file if it were writable"
    That's the same WP message under the files editor when you don't have permission on wp-content or if WP can't access the files directly by the PHP running as the apache user rather than the user that owns your WP files.
    Or,
    - "Changes you make to the contents will be saved to .../wp-content/ngg_styles/nggallery.css"
    So, it's clear that if you write something in that area then you also click the save button, and when you save the file is created.

    the plugin should not incorrectly tell people that their Child themes are not upgrade safe when they in fact are upgrade safe

    OK, this can be quite right, but the question is: why move that file, are there some reasons to do it?
    Normally, the "normal" user doesn't move style elsewhere if it can be written in back-end. There are few plugins that have a style customization area, so if you need some style changes in a plugin, what do you usually do, do you move the plugin .css file in your child theme? Or you clients do this?
    You are the only one of thousands if not millions to point out this thing.
    Again, nobody forces you to use that area if you don't want, child themes are for customization so use them, so I can't really understand your false problem.
    You can remove all the plugins that you want from your customers websites, but if you do it for these reasons and not for real problems... I don't think you should complain with the plugins' authors if you can't handle this kind of things.
    You could tell and ask about that inconsistency in the warning, and you'd be right even if you came to see it moving things that are not supposed to be moved, but everything else you've said falls into "The roof is on fire!" category.

  9. Dave333
    Member
    Posted 8 months ago #

    The two messages that you refer to do not appear in the location above the message as you claim on any of the affected websites.

    I am certainly not the only one of millions to point this out as you claim, the forums are full of users who are confused by this.

    I've moved the style sheet to the folder, exactly as instructed by this message:

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

    It is still giving the same incorrect message, stating that the Child theme folder is not upgrade safe (but it is) and that I have to move the style sheet to the "ngg_styles" folder (it's already in that folder).

    My problem is not "false", it is standard and real. I can't get rid of the error by following the instructions given in the alert message.

    i removed this plugin from all other sites I run because it is an endless source of frustration. Like many others, I have wasted way too much time troubleshooting this plugin when I can simply delete it and use one that is not plagued with ongoing problems. Again, these are real problems that many are experiencing. If you think this plugin has had no trouble in the past few months you've not been reading the forums.

  10. tizz
    Member
    Posted 8 months ago #

    I know that this forum is full of requests, that's the reason why I'm often here to try to help out, at least with the PEBKAC, I can't solve big problems or bugs.
    I had some problems too since the beginning with Nextgen (from versions 1.9x) and with some 2.x versions, I have lost time too and I'm not here to argue about your choice of removing the plugin.
    I'm trying to focus on this topic and when I said you are the only one I was referring to your idea of placing NGG style sheet in your child theme folder, and then complain if it doesn't work and there's a message that warns you.

    Now, you say that you have moved ngg_styles file in /wp-content/ and the message is still there, but have you deleted the one in your child-theme folder?
    And, can you please provide a readable shot of your /wp-admin/admin.php?page=ngg_other_options full opened in Styles > Show Customization Options?
    Then, if this issue can't be solved in the forum, you can open a bug report here giving your FTP and WP login credentials.

Reply

You must log in to post.

About this Plugin

About this Topic