News

There must be 1000s of Ruby on Rails apps still running on version 5, 6, 6.1, 7, 7.1, etc. Upgrading your Rails 5 app to version 8 is a herculean task. My latest article on how to upgrade your non-8-version Ruby on Rails application to version 8 provides a detailed guide you can follow to make this process less herculean. Read it here – Rails 8 Upgrade Guide 2025: Step-by-Step Instructions for a Smooth Transition.

The moment a lot of us has been fearing may be soon upon us. Among the various remedies proposed by the United States Department of Justice to address Google’s monopoly abuse, there’s also banning Google from spending money to become the default search engine on other devices, platforms, or applications. “We strongly urge the Court to consider remedies that improve search competition without harming independent browsers and browser engines,” a Mozilla spokesperson tells PCMag. Mozilla points to a key but less eye-catching proposal from the DOJ to regulate Google’s search business, which a judge ruled as a monopoly in August. In their recommendations, federal prosecutors urged the court to ban Google from offering “something of value” to third-party companies to make Google the default search engine over their software or devices. ↫ Michael Kan at PC Mag Obviously Mozilla is urging the courts to reconsider this remedy, because it would instantly cut more than 80% of Mozilla’s revenue. As I’ve been saying for years now, the reason Firefox seems to be getting worse is because of Mozilla is desperately trying to find other sources of revenue, and they seem to think advertising is their best bet – even going so far as working together with Facebook. Imagine how much more invasive and user-hostile these attempts are going to get if Mozilla suddenly loses 80% of its revenue? For so, so many years now I’ve been warning everyone about just how fragile the future of Firefox was, and every one of my worries and predictions have become reality. If Mozilla now loses 80% of its funding, which platform Firefox officially supports do you think will feel the sting of inevitable budget cuts, scope reductions, and even more layoffs first? The future of especially Firefox on Linux is hanging by a thread, and with everyone lulled into a false sense of complacency by Chrome and its many shady skins, nobody in the Linux community seems to have done anything to prepare for this near inevitability. With no proper, fully-featured replacements in the works, Linux distributions, especially ones with strict open source requirements, will most likely be forced to ship with de-Googled Chromium variants by default once Firefox becomes incompatible with such requirements. And no matter how much you take Google out of Chromium, it’s still effectively a Google product, leaving most Linux users entirely at the whim of big tech for the most important application they have. We’re about to enter a very, very messy time for browsing on Linux.

Shrouding the Heavens, 遮天,85,Zhe Tian,
At the edge of the dark and frozen universe, nine giant dragon corpses were bound in ancient bronze coffins. It seemed they had been there since the birth of the universe. This amazing view was captured by a spacecraft hovering in outer space.
The nine dragons and the mysterious bronze coffin made people wonder whether they went back to ancient times or had just reached another shore in the universe. A giant mythical world opens up, where immortality gradually emerges and paranormal events continue to occur.
Many people began to find their own traces (Dao) in these mythical realms. Their passion was like the turbulent and unrelenting waves of the sea. The heat in their blood was like an erupting volcano. Their desire for power and immortality drags them into the abyss without realizing it.
#ShroudingtheHeaven
#遮天
#85
#ShroundingtheHeavens
#Zhetian

Ready to make your WordPress website shine?
With strategic SEO crafted specifically for WordPress, you’ll watch your online presence skyrocket, reaching audiences that are looking for exactly what you offer.
Netrocket can be your guide to turning clicks into loyal clients. Let’s make your website a beacon of growth, visibility, and unmatched ROI.
Watch as Caleb shares the steps that can bring your website to life online, or schedule a free consultation to take the next big leap.
🌐 https://netrocket.pro/seo-for-a-wordpress/

Let’s grow online. Together!

by Marie Achour.  

Hello Moodlers,

 

Welcome to this edition of ‘Showcase Shorts’!

 

It’s been a very busy time at Moodle Products over the last few weeks, with many of our team members attending MoodleMoot Global in Merida, Mexico. We had a blast spending time with over 350 members of our community, celebrating all things Moodle with them. The event’s agenda was full of fantastic talks, which can be viewed on the Moodle YouTube channel, our ever popular Jam events, and the famous Moodle Party.

 

On November 5th, we were very proud to announce the release of Moodle Workplace 4.5. From advanced course discovery and curated offerings in the Learning Catalogue, to AI-driven tools designed to elevate content creation, the new release focuses on making learning more engaging, accessible, and tailored. We invite you to find out all about its benefits by checking out our release announcement. 

 

Upon returning from Mexico, the team dived right into planning mode to finalise our plans for the next  Moodle LMS and Moodle Workplace releases. 

 

Some of the highlights you can expect to see come to life include:

• A range of new AI-driven functionality, including integration options with more AI providers (AWS Bedrock and Ollama are next on our list) and new capabilities to help students get more out of their learning experiences in Moodle, such as actions to support translations and other personalisation of learning content options (check out the roadmap for all the details)!

• Much-needed improvements to the Assignment Grader experience, making grading easier for teachers (check out the prototypes here & here to see where we are heading)

• Optimisations to our Administration Settings, including smarter search functionality and more user-friendly descriptions of key settings (MFA settings will be first off the rank).

• The retiring of functionality that make Moodle harder to use and run than it should be, including the removal of the Chat & Survey tools, the Atto text editor and support for Oracle Databases (don’t worry, Chat, Survey and Atto will remain available as plugins for the few of you who still need them).

• More goodness for LTI lovers, with the migration of mod_lti into core. This will enable the use of LTI placements in the text editor, course navigation and assignments (find out more here).

• The launch of support for SMS notifications, critical for everyone in the world who doesn’t always have access to the internet but still wants to stay connected to their learning (which is still more than 34% of the world’s population – about 2.6 billion people!).

• For our Workplace customers, you can expect to see data visualisations come to report builder (charts are coming!), improvements to multi-tenant settings, programs available in the course catalogue and, the much much requested ‘user in multiple tenants’ functionality.

 

We will also complete our next MUA project, the upgrade to Bootstrap 5.0, and all our products (including our beloved Mobile Applications) will go through their annual accessibility audits and be certified to WCAG 2.2 (vs 2.1) for the first time.

 

With all the travel and the planning work, we don’t have a lot to share in terms of demo videos this time around, but we did think you’d like to see what a team gets up to during a release sprint, so here is the Showcase Short from the Moodle Workplace team in full. You’ll notice they don’t stop for a release, and the improvements keep coming!

Go to the forum to see the video! 

That’s it for this edition of our ‘Showcase Shorts’; we hope you’ve enjoyed the updates.

 

Until Next Sprint!

The Moodle Product Team

Today we are talking about being the CTO of the Drupal Association, How the job has changed, and How its impacted Drupal with guests Josh Mitchell & Tim Lehnen. We’ll also cover Automatic Anchors as our module of the week.

For show notes visit: https://www.talkingDrupal.com/477

Topics

• How long ago were you CTO Josh
• Tim when did you take over
• DA infrastructure
• Drupal Credit System
• Josh’s proudest moment
• Tim’s proudest moment
• Growth
• Josh if you could do one thing differently
• Tim if you could make one change
• Future of the CTO job

Resources

• OOP Hook conversion
• Oregon State University Open Source Lab
• Whuffie: Cory doctorow Down and Out in the Magic Kingdom
• Rethink weighing of contrib projects and credits

Guests

Tim Lehnen – aspenthornpress.com hestenet

Hosts

Nic Laflin – nLighteneddevelopment.com nicxvan John Picozzi – epam.com johnpicozzi Joshua “Josh” Mitchell – joshuami.com joshuami

MOTW Correspondent

Martin Anderson-Clutz – mandclu.com mandclu

• Brief description:
  • Have you ever wanted headings on your Drupal site to have unique id values, so links can be created to take users to specific parts of any page? There’s a module for that.
• Module name/project name:
  • Automatic Anchors
• Brief history
  • How old: created in Jun 2020 by Chris Komlenic (komlenic) of Penn State
  • Versions available: 2.1.1-beta1, which supports Drupal 8.8, 9, and 10
• Maintainership
  • Test coverage
  • Number of open issues: x open issues, y of which are bugs against the current branch
• Usage stats:
  • 137 sites
• Module features and usage
  • By default, the module automatically generates ids on , , , , and elements within the page content
  • Even if two headings have the same content, the module will make sure their ids are unique, as well as making sure they are i18n-friendly, use hyphens instead of spaces, and are short enough to be useful
  • The module won’t interfere with or change manually-added or already-existing HTML ids
  • There’s a permission to view helpful links on each heading that the ids obvious and easy to copy
  • Configuration options include the root element it should look within (defaults to the body tag), which elements should get ids, what content to use for the displayed links, and whether or not generate ids on admin pages