self-changing implementation

  • Resolved ZicPL

    (@zicpl)


    3 months, 2 weeks ago

    Cze??/Hello,
    I would like to ask why there is a dynamic self-changing implementation.
    Based on my understanding, the code from the “implementation” tab should be inserted into any .php file. The cron job will subsequently execute a hook linking this implementation to its corresponding tasks as per the established schedule. Given that the plugin necessitates a specific function with a unique name, it is unclear why the function name is dynamical altered from its original implementation. This inconsistency is puzzling unless the function name within the implementation is inconsequential. A prompt clarification would be greatly appreciated.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Kuba Mikita

    (@kubitomakita)

    Hi, the function name doesn’t matter at all, we’re generating its name everytime to be unique to prevent from fatal errors. What’s more important is the hook name which is always the same.

    We’ll change that code to a closure in the future releases

    Thread Starter ZicPL

    (@zicpl)

    The changing name doesn’t actually cause my problems now. Maybe I had something with cache set incorrectly. In any case, it’s good to know that this function name won’t change in the future. To prevent future misunderstandings, briefly clarifying that the name change does not impact cron operations might be helpful (on plugin setting tab).

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