@bluehawk thank you so much for suggesting some wording but why pretending a technical issue when you are sure that there was not any ?
If some of you are really interested about the initial topic of a D10 release: better using your time to work on a fork instead of writing in this thread.
If you are interested in creating conflicts as it seems: it will be without me, sorry.
Last message from me here.
@bluehawk work on the fork in a professional way
@keiserjb work on the fork instead of becoming a customer
@danlinn
I never received any of these emails.
And sorry for you, but I never enable out of office on my emails. So it fully demonstrates that you’re a liar.
Work on your fork now, I’m very impatient to seen what a guy like you can do, I have the feeling that I will be laughing a lot.
From now on I won’t any more answer to your messages, no time to waste.
Dan@danlinn.com
Please stop lying, I never received any message from you.
Make also sure to use a proper and respectful language, your language is not acceptable.
Very impatient to see your masterpiece fork ! I hope it’s not a lie like the fact that you contacted me.
@b1ueh4wk
Thanks for your understanding and for tour suggestion and proposal of wording. I agree with you that our communication was probably not sufficient. Next week will add some similar message to the one you suggested.
As for the people who wrote they filled in our contact form but did not receive any answer, what I can say is that all people contacting us are receiving an answer. Except in case of some technical issue that would have prevented us from receiving their message, it’s not possible that they would not have received any answer. If these people could provide their email address I could investigate in our CRM to know if and when they contacted us, and what was the answer given to them.
@keiserjb I guess you just pretend not understanding. It’s not A paid service. There is the open source project AND the optional paid service. Nothing extraordinary.
As a summary:
For the ones who will wait the Opigno D10 release will happen.
For the ones who want a fork, let’s code it.
And this way everyone will be happy.
Enjoy your weekend !
@keiserjb last time we asked for help to manage some issue to someone who opened a ticket on Drupal.org, the guy answered that he had no customer paying for these hours to help for issue resolution. That’s open source vision of a lot (most) people: let’s open tickets, let’s request what we want, and wait for it to arrive for free and fast.
I’m not sure that you really measure the amount of work to maintain Opigno. It cannot happen with just a few hours when available. Be honest and say how many hours you could dedicate to it per week (in a guaranteed way).
Opigno was created 11 years ago. We had time to analyze this question and unfortunately community could not bring the necessary support. Sadly.
Once again, we will continue providing releases. If you think that you can do better, feel free to fork !
@pixiekat indeed we communicated a deadline that we could not meet and that was a mistake. This is why we won’t repeat the same mistake.
As for open source everyone is free to have their own vision. Let’s say that our company is obviously supporting open source in a very different way since for every OS technology that we are using we purchased editor support. Our vision for supporting them.
Hi everyone,
I think we were transparent but as it seems that there is still confusion, here are some clarifications and answers to some questions.
Will a D10 release be done on Drupal.org ? Definitely. We said we will do it and we will.
When? We don’t want to generate additional frustrations by announcing a date and then not be able to meet this deadline. We cannot commit to more than best effort.
Why is it still not available? All developers involved in Opigno project are employees of our company. If we want to move faster we need to hire more developers but the company needs to pay their salaries. So far we cannot afford for more developers and our team is fully busy with customers’ project, maintenance of Opigno (nearly weekly updates and security fixes have to be done), and starting to prepare for D11. FYI thousands of hours are spent every year by our developers on Opigno, then the result if made available on Drupal.org. That’s a huge investment of time and money. And it’s increasing more and more as the frequency of Drupal releases is increasing.
Is there already a D10 release available for our clients? Yes, and we have always been transparent with this. We give the priority to our clients because they are paying the salaries of our developers, and our remaining available time is spent for the community management. It’s impossible to address customers’ expectations and open source management at same pace. If Opigno exists it’s because our company maintains it, and if our company exists it’s because we have customers.
What about the ones with « business critical » needs for a D10 release ? In such case you should not use open source software without editor support. This is valid not only for Opigno but for all entreprise software. We introduced a specific offer allowing our customers to get faster updates and benefit from SLA. This also brings benefits for open source community since it will allow us to hire more developers and better and faster develop Opigno. Purchasing editor support is the best way to support some open source project.
Will there be a D11 release? Yes, on the same principle as D10.
I think it’s difficult to be more transparent and I hope it will bring the necessary clarity.
@mnikolov Yes it's correct, last release with composer is 3.1.3
I will close this ticket since you said that it works now, thanks for your feedback !
Hi,
The package was not updated yet, we manually triggered the update.
Now it should work, can you try one more time please ?
Hi
We removed this tag, it should be working now.
Can you please try again ?
Hi @jackradford
We don't want to announce some precise timeline since many different factors are involved, and not being able to meet the announced timeline would then generate some frustration, which I can understand.
What I can say for sure is that we are actively working on it and getting closer, and we are trying our best to make it happen as soon as possible.
Hi @sascher
It should be 10.2.x (10.2.2 or more recent)
Hi @sascher
It will be Group 1.6.
Update to 2.2 is theoretically possible, but the name of content types were changed.
This would consequently require some additional work (to some already complex port from Drupal 9 to Drupal 10) and extensive testing, so Opigno 3.2 (Drupal 10) will start with Group 1.6 (that is still supported with Drupal 10).
Then we will work on upgrade to Group 2.2.
Hi @kavo3, @jamesmacintyre
The initial announcement was indeed optimistic, and we are sorry for this. For now we don't want to commit on a precise date, in order to not create disappointment or frustration.
What we can say is that we are definitely committed to doing it as soon as it will be reasonably possible.
In short, this upgrade amounted for much larger changes than we anticipated, but additionally the release on drupal.org doesn't depend just on us, and represents some additional work, and for obvious reasons in very busy periods we have to focus as first priority on our customers.
In case this upgrade is business-critical for some of you, please contact us at https://www.opigno.org/contact
Thanks for your understanding!
Hi @Tim Corkerton and @jive01
It will be Bootstrap 4.6.2
Hi @nikolaimanek
Unfortunately we are not able to provide a precise date at the moment.
We commit to precise dates with your customers, and we will do the deployment on Drupal.org when we will have time.
One of our representatives will contact you early next year.
Best wishes,
Hi everyone,
Unfortunately we still couldn’t find time to push a stable d10 release on Drupal.org.
It will be done in January.
Happy holidays !
Hi kanchamk,
Did you follow these instructions for the upgrade ?
https://opigno.atlassian.net/wiki/spaces/OUM3/pages/2918580225/Upgrade
Thanks for reporting this. We will include a fix in the next release of Opigno.
Hi @drupalfan79
Opigno currently not officially supports Drupal 10, that will be next version supporting it (some modules still need some upgrades / patches).
It will be easy to switch to CKeditor 5 with Drupal 10.
Hi,
Thanks for raising this point.
We cannot apply the patch suggested for several reasons:
- It doesn’t fit code standards (static calls of services instead of dependency injection);
\Drupal::service('file_system')->copy($source_folder, $dest_folder);- this piece of code will not work because it’s possible to copy only files using Drupal file system, not directories.
Submitted merge request could not be approved for the same reasons + it’s created to branch 8.x-1.x that is not the latest version.
We will implement it in a different way and include this in the next Opigno release.
Hi Claudiu
Thanks for raising this issue and suggested this fix.
It will be included to the next Opigno release
Hi,
This trait is in opigno_module module that is probably not installed on your sites.
Can you please check this ?
Hi
Thanks for reporting this issue.
It will be fixed in the next release of Opigno
Hi Karen
It's not a hook_update_N() if the value in the database is not changed.
There was a wrong detection of the field value and this was fixed.
We checked again on our platforms and in UI we have the same value that is in DB.
Maybe you had a custom fix to detect this field value and now it negates the result ?
In this update we set the reference between module attempts and the latest training attempt for every user. Entities are not re-saved, the data is updated directly in the database and guided navigation checkbox state is not changed
So this update cannot explain why your settings for navigation have been changed.
Unfortunately that might be complicated to investigate why it occurred remotely.
Thanks for your answer.
It's very strange and something did not went as it should.
Could you please tell me the hook_update_N() that failed twice for you ?
That would be an interesting starting point to understand why the navigation mode was changed to "free".
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0
Released in Opigno 3.1.0