WPIntell

Source evidence

self-changing implementation

Advanced Cron Manager – debug & control · support · 2024-08-13T02:06:00+00:00

mixedsentiment
highseverity
0.95relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

7 / 35 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
ZicPL resolved
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. 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 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).

Comments

2 shown
Kuba Mikita 2024-08-13T08:15:00+00:00

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

ZicPL 2024-08-13T11:00:00+00:00

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).