• This appears to have potential but (a) the pink wording on blue buttons in the admin pages is hideous — there’s no way I can use a plugin that’s going to scream at me like that every time I try to use it — (b) it uses a deprecated function, and (c) it generates no fewer than 40 PHP notices!

    I suggest you turn on debug or, better still, use the Query Monitor plugin when developing.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author CodeBard

    (@codebard)

    This appears to have potential but (a) the pink wording on blue buttons in the admin pages is hideous

    Please note that you can override the style of buttons (and actually anything) by hooking into templating functions. Individually, or you can duplicate the templates/ folder into another plugin and override entire template by overriding template loading.

    Plugin Author CodeBard

    (@codebard)

    I missed that you were talking about admin interface.

    Normally, you shouldn’t need to see admin interface for a long time after setting up your plugin as you want. Because everything is meant to be done from front end – a support admin, agent or user never need to see the WordPress admin interface.

    However if you are bothered by the style of admin interface, elements there can be modified in setting_sections/ templates under the plugin, and the style can be overridden from admin css as well.

    • This reply was modified 8 years, 2 months ago by CodeBard.
    Thread Starter KTS915

    (@kts915)

    I know that it is possible to modify admin CSS, but you only get once chance to make a first impression. I suggest you re-think the admin design before you deter other users too.

    Plugin Author CodeBard

    (@codebard)

    It is certain that many people will have many different opinions on the color palette of a button in admin section of any given plugin. Leaving aside the fact that people at large have different preferences when it comes to art and style.

    That is why it is a custom in WordPress development to give people the tools to change and modify their software to maximum extent possible when developing. Which principle, this plugin has been developed on.

    And in that tangent, if a user would instantly drop this plugin over the color choice of a particular type of text on a particular type of button in Plugin’s WordPress settings page (which s/he will rarely ever see) in lieu of the functionality loaded in the Front end of the plugin (which really, really matters), then there isn’t much we can do to satisfy such a user in the long run.

    It seems you are taken back by the color choice of a font on buttons on admin side, instead of anything related to actual functionality of the plugin, as your criticism focuses in that direction.

    Which means that the actual functionality of the plugin was satisfactory, and that’s quite good to hear.

    Thread Starter KTS915

    (@kts915)

    It seems you are taken back by the color choice of a font on buttons on admin side, instead of anything related to actual functionality of the plugin, as your criticism focuses in that direction.

    Then I suggest you read my initial post again.

    I have responded to your comments on the aesthetics of the admin page because that’s the only aspect of my original post on which you have commented!

    I am actually much more concerned about all the errors that your plugin generates. Yet you have failed to respond at all about them!

    If you think that generating 40 PHP notices means that all’s good with the functionality of this plugin, then that tells me all I need to know.

    Plugin Author CodeBard

    (@codebard)

    PHP notices

    PHP notices, are not errors. Things like variables being not initialized before, are not critical concerns in PHP due to nature of the language as many people in our line of work agree.

    https://softwareengineering.stackexchange.com/questions/104818/how-important-are-php-notices-really

    The functionality of the plugin is well tested, debugged. Anything that has been implemented, has been manually tested over time. And everything, naturally works.

    You have changed your wordage from notices to errors, which now makes it look as if the plugin creates any actual errors that hampers a production server or breaks functionality. If your production server is set to display PHP notices, that would be your particular situation. I didn’t hear anyone using their production server with php notices on.

    If you think that generating 40 PHP notices means that all’s good with the functionality of this plugin, then that tells me all I need to know

    If there is any issue or error you encountered with the functionality of the plugin, i would have been pleased to learn of them. Instead, you first talked about the notices you encountered, and then moved on to talk about them as errors.

    Which particular error have you encountered with the functionality of the plugin?

    Are you unable to open support tickets as a user? Or reassign them as an admin. Or, is there any issue in between the capabilities of Support Admins or Support Agents?

    If there is anything that impacts actual functionality of the plugin, as opposed to any personal principle about strict typing of PHP code that underlies it, i will happily accommodate you.

    Thread Starter KTS915

    (@kts915)

    Experience tells me that a long list of PHP notices that are not addressed now simply means saving up trouble for later. I much prefer prevention to cure.

    I also don’t look forward, when trying to debug something on my site, to seeing the logs being polluted with all that guff everywhere. A plugin downloaded from www.remarpro.com might be free in terms of money, but one that adds unnecessarily to the time and trouble involved is still far too expensive.

    Plugin Author CodeBard

    (@codebard)

    An uninitialized variable will not cause any trouble now or later as long as PHP group does not decide to turn the language into a strictly typed one in which people would have to initialize their variables before using them. Not to mention break a lot of other things inside PHP itself.

    Its your preference to have your PHP strictly typed.

    ……….

    Long story short, you havent encountered any issue with the functionality of the plugin, as you havent named any.

    To make sure – have you encountered any issue or problem with the functionality of the plugin? What havent you been able to do?

    Plugin Author CodeBard

    (@codebard)

    Considering this thread resolved since you havent seem to have encountered any issue with plugin functionality.

    Your other assessment and criticism was also noted. Thanks.

    If you encounter any issues with plugin functionality or would like to ask for features, feel free to open another thread.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Has potential but needs cleaning up’ is closed to new replies.