@symfonystation i stopped reading at "Upgrades have been painless, for the most part." It is clear this person wasn't doing anything "advanced" like simpleSAMphp for SSO that needed a new release for Symfony 6 or using a CKEditor plugin that had to be rewritten for 5. Version ignorance is still ignorance. Let's say you you own a Jeep and want a 3" lift. If I asked you what year your Jeep was & you said "don't know, doesn't matter", I'd know you were going to pay too much for that lift.
Spoiler… these modules are all part of the Commerce ecosystem. Commerce is great and a very robust, well-designed solution… for large e-commerce use cases. It would have been nice to see other modules like www.drupal.org/project/stripe_pay included.
@kreynen I wish links on Kbin that allowed me to choose which image to use as the thumbnail. One of the downsides of using links over articles is the thumbnail comes from the URL. While I can edit the prepopulated title and body, the image just reappears/reattaches when removed.
@kreynen Worth noting that even the 2.x beta documentation recommends avoiding patches autogenerated by PR/MR URLs.
> "The contents of these patches can change by pushing more commits to a pull request or merge request. A malicious user could abuse this behavior to cause you to deploy code that you didn’t mean to deploy."
The recommendation is to download a patch & apply it locally, but I'm guessing we'll see devs continue to add patches in queues & include those URLs
@kreynen I completely agree, and as the post states, using the GitLab provided patch in a composer.json without downloading it and referencing it from a local directory is also a security risk. Although, I'm curious how this recommendation will change once GitLab allows .patch to be appended to any compare URL.
@kreynen if are a #webdev working in higher ed (especially at a top international school) or an agency that works in this space, please help us generate the most accurate statistics possible about #Drupal usage in higher ed.
Drupal
Hot