Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author luciole135

    (@luciole135)

    Certainly,
    but it is good to have same functions between different StatPress plugins because they use the same data table.
    Thus, it is impossible to activate multiple StatPress who would write simultaneously on the same data table.

    Thread Starter ciuly

    (@ciuly)

    Your plugin description states that it is compatible with StatPress. The fact that it cannot be activated because of this error proves otherwise.

    So either eliminate the compatibility statement, or fix it as you see fit.
    I don’t claim my suggestion is the best course of action as I don’t have knowledge on either of the plugins, but if the plugins are not compatible, I’d like to know now, as then I’d have to remove StatPressV before it corrupts my StatPress data. And I really don’t have time these days to go through the code to figure it out, I have a milestone due this weekend for some project.

    Thanks.

    Plugin Author luciole135

    (@luciole135)

    I misspoke then.
    Compatible means it works with the same database. It does not add his own.

    Thread Starter ciuly

    (@ciuly)

    I’m sorry, but there is a reason why language is “universal”. So that we can understand each other.
    google “define:compatible”. It says:
    “(of two things) able to exist or occur together without problems or conflict.”

    So, is this plugin compatible (according to universal concept) with the StatPress plugin or not? Will they work nicely together, without problems, or not?
    The current code, as-is, is not compatible, because there is this one obvious error. Having it fixed, will the fixed plugin be compatible with StatPress or not? (code-wise, apparently at least, it will. Data-wise is unknown for me)

    If it is, then you can check with StatPress authors and see if you guys can find a general way of “sharing” code (using include_once/require_once or function_exists or what not)

    Plugin Author luciole135

    (@luciole135)

    Vous avez certainement raison, et comme le langage est universel, je vous laisse traduire ma réponse avec Google translate peut-être qu’elle sera parfaitement traduite, du moins je l’espère.

    Thread Starter ciuly

    (@ciuly)

    I am not a native-english speaker either, but at least if I want to communicate in english I do my best to know and understand the language. Otherwise I will risk my message to be miss-interpreted and miss-understood.
    Even if you use google translate to get your message quickly into english, you should have the minimum knowledge of the language to crrect any flaws. And if not, always mark your messages as “translated from french”. Other people do it and so they eliminate such discussions.
    It is not the fault of the otehr part that they do not understand what you actually are trying to communicate, it is your fault that you don’t invest sufficient resources to learn the language properly or correct the translations or notify your readers that you are translating your messages.

    In conclusion, I will delete your plugin, give a proper review and feedback on it and find something else. Instead of answering my problem which I made clear in my second post, you waste my time with stupid things.

    Way to go frenchie.

    Plugin Author luciole135

    (@luciole135)

    Vous pouvez détruire tout ce que vous voulez, ce plugin est gratuit et que vous en utilisiez un autre ne change absolumment rien pour moi.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘StatPress_Print not compatible with original StatPress’ is closed to new replies.