So I have confirmed that this field group has had a bad config since it was created years ago. I'm in a hurry, so I just modified the config and re-imported it. I have an issue now where I can't move things out of a fieldset now but I can live with that for now. I'm using 3.2.0 on D9.5.
I can confirm that this is happening on an upgrade from Drupal 9.3.1 to 9.5, too. We have a Sidebar Details element that gets corrupted somehow. It now has no settings on the manage form display page and I'm unable to change it. Looking into it!
@axelm You have multiple people on this thread who have tried to contact you to give you money, yet you say you haven't received them. Maybe you need to check your email deliverability.
You're calling me a liar and I'm being disrespectful? Ok, buddy.
Is your email address still Axel Minck ? I got that when we bought support hours and met with your team. Here are the emails I've sent that have gone unanswered:
Sent April 15, 2022 - got an out of office, but never a reply:
Hello Opigno crew!
We’ve got an issue we’d like to discuss around config imports as we gear up to go live with our implementation. Can we get some time on a calendar to discuss it under our support contract?
Also, any representatives coming to Drupalcon? We’d love to meet you in person!
Thanks,
Dan
Sent April 15th, 2024 - no reply:
Hello Axel,
I hope you’re doing well. We’ve been anticipating the release of the Drupal 10-supported version of Opigno, as initially indicated for Q1 completion. We understand that timelines can shift, but we find ourselves at a critical point where we need to plan our next steps.
We are currently limited to Drupal 9.3 and unable to upgrade to PHP 8, which is not ideal. Given the situation, we’d like to leverage our support hours to discuss how we can move forward. It's become apparent that the focus may have shifted towards cloud products, and we're left uncertain about the roadmap for Opigno.
Could we schedule a call soon to explore solutions using our support hours? Whether it’s a development release, forking, simply updating some dependencies, or even having our team assist in development, we’re open to suggestions. Our goal is to ensure a smooth transition to Drupal 10 with minimal disruption to our operations.
We appreciate your attention to this matter and look forward to finding a viable path forward.
Thanks,
Dan
Sent May 29th - no reply:
Hello Axel,
I didn't hear back about this, and in the meantime, I've seen your posts in the issue queues. What do we have to pay to get the upgraded code for D10? We still have support hours, and I thought that meant we were a "paying customer", but if not, we need to find out what it takes to become one.
Thanks,
Dan
So am I a liar or are you just super shady and pulling an open source rug pull? Our fork won't be a masterpiece, but it will be open source.
I’ve sent multiple emails to @axelm and we have paid support hours and they still aren’t responding. We even offered to pay whatever the extortion rate is to get the D10 version. It’s pretty clear they are abandoning open source as we understand it. I’m working with folks on the Drupal slack on a fork. @reswild Your code may be a good start for that!
@abedih I haven't forked a project before but if you do fork it, we will contribute.
Follow
We're actively patching stuff. We could REALLY use this... I'm starting to wonder if it's abandoned?
Here's a new patch against the newest version:
Here's a patch that we are using to allow for HTML emails.