Matthias Bathke

Hi Ryan,

big thanks for your support!

Kind regards,

Matthias

Hi Ryan,

I’ve sent you the mail with the infos for the staging. Big thanks for looking into it.

Kind regards,

Matthias

Hi Ryan,

thank you for your response, concerning your questions:

1. This occurs in Site Editor and on a piece of content (e.g. new post in post editor)
2. This occurs on some titles. Some posts work, some not.
3. I’ve tried to create a helpful screencast showing the issue, but I don’t think it would help here. You would see only some posts will be selectible only and some not, but screencast is not showing any difference between the posts. Maybe access to staging to reproduce the issue live is a faster way to reproduce the issue. May I ask to send the credentials somewhere for a quick look?

Kind regards,

Matthias

Hi Johannes,

thank you for addressing these issues. Your feedback is very appreciated. We’ve implemented the patch for the first issue. You may test it in v2.0.02. I’ve prioritized the release in appreciation of your effort in this case.

Unfortunately, I have no clue why assets in WP-Admin are not loaded and you are in need of an redirect to fix this on the Roots Bedrock environment. We never had any problems with asset loading on regular WordPress environments. Due to it’s edge case classification and involvement of third party software, we can not take care of this due to capacity issues through our free support.

I would recommend to address this issue to Roots Bedrock and ask if there may a possibility to investigate on their side which change in their environment triggered this issue.

Kind regards,

Matthias Bathke

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

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

Dank dir für die Nachricht. Welches Caching Plugin setzt du ein?

Hi,

thank you for the report, this has been fixed in v2.0.02.

Kind regards,

Matthias

Ja, gerne eine Staging-Kopie der Website einrichten und WP-Admin & FTP Zugang an [email protected] senden.

Hi Karsten,

dann handelt es sich vermutlich um eine Inkompatibilit?t. Kannst du mir die Fehlermeldung aus der Error Log posten?

Hi Karsten,

probier gerne einmal der neue Version v2.0.00 aus. Das Plugin bietet jetzt einen eigenen Block, so dass dein Problem ggf. hierdurch gel?st werden konnte. Gib gern Bescheid, ob das Update geholfen hat.

Beste Grü?e,

Matthias

Hi Karsten,

leider konnte ich wegen Krankheit nicht schneller reagieren. Bitte aktiviere das debug.log in WordPress – kannst du dort nach Auftreten des Fehlers ggf. eine Fehlermeldung sehen, die mit dem Problem zusammenh?ngen k?nnte?

Debugging in WordPress

Beste Grü?e,

Matthias

Hi Karsten,

ein Update-Release ist in Vorbereitung. Ob es dein Problem behebt, kann ich leider nicht einsch?tzen, hierzu br?uchte ich mehr Informationen, welche Art von Konflikt bei dir auftritt. Das Plugin funktioniert in der ver?ffentlichten Version 1.9.00 auf vielen Websites, es k?nnte also bei deiner Installation auch ein anderes Problem vorliegen.

Unter https://github.com/straightvisions/plugin_sv_provenexpert kannst du beispielsweise die derzeit aktuelle Entwicklungsversion (v2.000) als Branch ausw?hlen und herunterladen. Gib gern Bescheid, ob sich dein Konflikt hierdurch l?sen konnte. Ansonsten gib gerne weitere Informationen, damit das Problem weiter eingegrenzt werden kann.

Beste Grü?e,

Matthias

Hi spencer,

I haven’t heard anything more from you so far, so I hope your problem has been fixed by the update and mark this topic as resolved.

Kind regards,

Matthias

Hi spencer,

thank you for your good feedback.

With regard to “Close on Anchor”, there are currently two reasons why this plugin should not be used:

1. It would soften the single purpose approach of the plugin, which might be worth considering.
2. According to my tests, the menu is already closed when clicking on an anchor, possibly this is already part of the original script of the navigation block (I have not checked this).

The suggestion to simulate a close click is very interesting, I’m just not sure if this would be best practice. I implemented the aria-hidden switch first (v1.0.01 release), but I’m keeping your approach in mind as a possibility for the future. Thank you very much!

I look forward to your feedback.

Kind regards,

Matthias