• jsjs

    (@jsjs)


    Unfortunately not compatible with PHP 8.2.

    Deprecated: Creation of dynamic property sv_core\settings::$setting_checkbox is deprecated in /var/www/html/wp-content/plugins/plugins/sv-tracking-manager/lib/core_plugin/core/settings/settings.php on line 168

    • This topic was modified 3 months ago by jsjs.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Matthias Bathke

    (@matthiasbathke)

    Thank you for taking your time trying our plugin and sending your feedback. While we always love to improve, your conclusion in this case may be wrong. Please let me explain my perspective:

    Logical

    1. this is not a bug, but a deprecation notice for future PHP versions
    2. dynamic properties will throw a fatal error not before PHP 9.0
    3. PHP 9. isn’t even announced yet
    4. there is no need to bind valuable DEV ressources yesterday into changing critical architecture components

    Emotional

    This is a free open source software without funding except from our DEV Team. I understand that situations can become challenging in life. Maybe that could have been the reason why you have not used better methods, e.g. there is a Support forum for questions like these, with a chance that community support may respond better/faster than we ever could.

    You’ve made a devastating evaluation of our performance and results without giving us a chance to respond before you’ve framed the relationship you have started with us. Please reconsider, that our work was free so far and your part of this relationship created costs without benefits on our side. This is not how open source communities or even any relationship should work.

    My Conclusion

    What is a 1 star review for a non-critical deprecation warning without any effect on the outcome of the feature telling us about failure culture in these times.

    Thank you for considering.

    Matthias Bathke

    Thread Starter jsjs

    (@jsjs)

    Hi Matthias,

    i`m sorry. I searched for the suport forum and did not find it. Link was more prominent in the past and I did not see another possibility of creating a bug report. Please do not overjudge this as a general failure culture thing. I was just in a rush and wanted to report the problem.

    I created a topic with my issues
    https://wordpress.org/support/topic/deprecation-warning-in-php-8-2-and-incompatibility-with-roots-sage/

    Sorry again,

    Johannes

    Thread Starter jsjs

    (@jsjs)

    One more thing: Your plugin is recommmended by Usercentric as “Plugin from out partner straightvision”: https://usercentrics.com/de/knowledge-hub/wordpress-und-usercentrics/

    I`m a usercentric customer, and installed the plugin. And my local wordpress was completely broke because of the deprecation notice and the wordpress admin asset thing. So even if this is open source plugin: That didn’t look to me like a plugin that a single developer put his free time into. It looked like a plugin from a commercially active company where im a paying customer. Perhaps one more reason why I quickly switched to bad rating.

    Just that you can understand my perpective a bit more 🙂

    • This reply was modified 3 months ago by jsjs.
    Plugin Contributor Matthias Bathke

    (@matthiasbathke)

    I feel a great sense of relief, thank you for taking my answer so constructively.

    Thank you for elaborating on what your experience was like in problem solving, the path helps me tremendously to surmise the origins. What I see is that a trivial problem became a stressful situation because two anti-patterns ran counter to an intuitive treatment of the problem:

    • The support forum could be linked in a more visually striking way. The contact person is the WordPress design team.
    • Your WordPress environment is configured to display PHP warnings. You can change the setting via WordPress Config. My recommendation is to deactivate the display of errors at web host level and only work with error logs.

    Thank you also for pointing out how you came to the conclusion that we are financially equipped for a different level of quality and support. I can now better understand the expectations. Unfortunately, we have the same dynamic on other plugins, too. The reality is, that open source software is likely not to get funded by Software as a Service providers.

    So thank you once again for giving me the opportunity to reflect on the overall situation with your feedback.

    Kind regards,

    Matthias

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