182.8 Meters


| submitted by /u/stuntycunty [link] [comments] |
| submitted by /u/RootExploit [link] [comments] |
This is bug-fix release for 1.29.0.
Feature highlights✨:
.txt import of feed URLs in additional to e.g. OPMLBug fixes highlights 🐛:
UI highlights 🖼:
This release has been made by @Alkarex, @Frenzie, @IEEE-754, @Inverle, @McFev, @ciro-mota, @cweiske, @polybjorn and newcomer @mzl2233
Full changelog:
lib_opml library #8652, #8853,
| AIs are eating our websites, and we need to adapt by bringing AI into our website to enhance our content and user experience and provide a five-star dining experience. [link] [comments] |
| Probably the reason for the security update tonight! [link] [comments] |
Firstly thank you for such detailed suggestions and I am learning Drupal at a good pace, enjoying most of the time and process. I am learning mostly frontend right now and absorbing everything, learning some backend too but not heavily, would go on it later
I would really appreciate some help from your side as you all have been in the Drupal market since so long, I have a drupal interview in coming week, the person said its frontend heavy role, you will be working mostly on the frontend with HTML CSS JS.
While I understand how Drupal architecture works and how to make things and how does this css works here,
I am confused what can I be asked in the interviews, mainly what is asked in Drupal? would they ask me from html css? I come from a full stack web dev background so really no idea how it works in low code interviews, its a part time role. Just 1 round of interview to show my understanding and skills
Any help is good, I will really appreciate, thank you so much !!!
May 20, 13:03 UTC
Resolved - Between 06:35 UTC & 12:36 UTC today, our engineering team identified an issue impacting the Cloud Firewall. During this period, users might have encountered issues while updating their firewall rules.
Our team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.
We regret the inconvenience caused and appreciate your patience and understanding. However, if you continue to experience any issues, please create a support ticket for further analysis.
May 20, 12:43 UTC
Monitoring - Our engineering team has implemented a fix that affected the Cloud Firewall rules. Users should now be able to update their firewalls successfully.
We are actively monitoring the situation to ensure overall stability. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
May 20, 12:08 UTC
Identified - Our engineering team identified an issue impacting Cloud Firewall Product. During this time, users may notice HTTP 500 errors when updating firewalls.
We apologize for the inconvenience and will share an update once more information is available.

© iStock
May 20, 07:48 UTC
Resolved - Our Engineering team has verified that the issue causing incorrect Cloud Firewall rules to display on the cloud panel is fully resolved. The user interface continues to function as expected, and all systems have returned to normal operating conditions.
If you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident.
May 20, 07:15 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue causing incorrect Cloud Firewall rules to display on the cloud panel. At this time, the user interface is functioning as expected, and we are actively monitoring the situation to ensure continued stability.
We will provide a final update once we have verified that the issue is fully resolved.
May 20, 05:35 UTC
Investigating - We are currently investigating an issue with incorrect Cloud Firewall rules appearing on the cloud panel. Our engineering team is aware of the situation and actively working to identify the root cause. Since this is a user interface issue, users should not experience any problems with other services or networking.
We apologize for the inconvenience and appreciate your patience. We will continue to provide updates as we learn more.
May 20, 05:13 UTC
Resolved - From 00:00 UTC to 01:40 UTC, users may have experienced degraded write performance and intermittent impacts to workloads dependent on Block Storage Volumes in the NYC3 region.
Our Engineering team has confirmed that the underlying infrastructure issue affecting Block Storage Volumes at the storage layer has been fully resolved, and services are now operating normally.
If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
May 20, 02:19 UTC
Monitoring - Our Engineering team has implemented mitigation measures for the infrastructure issue affecting Block Storage Volumes in the NYC3 region. The team is monitoring the situation, and we will share another update once the issue is fully resolved
May 20, 01:05 UTC
Investigating - Our Engineering team is currently investigating an ongoing infrastructure issue in the NYC3 region affecting Block Storage Volumes at the storage layer. Users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure.
We apologize for the inconvenience and will continue to provide updates as more information becomes available.

© Getty Images/Rest of World
| submitted by /u/zad370 [link] [comments] |

| submitted by /u/naderman [link] [comments] |

© iStock/Rest of World
May 19, 17:30 UTC
Completed - The scheduled maintenance has been completed.
May 19, 14:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 17, 14:35 UTC
Scheduled - Start: 2026-05-19 14:30 UTC
End: 2026-05-19 17:30 UTC
During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the SGP1 region.
Expected impact:
We do not anticipate any downtime for Droplets or Droplet-related services, including Managed Databases, Load Balancers, App Platform, and Managed Kubernetes, as this maintenance has been carefully designed and tested to be seamless. In the unlikely event that an undetected misconfiguration occurs, a subset of customers could experience temporary network disruption. We will endeavor to keep this to a minimum for the duration of the change.
If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket
So, like Icarus, I flew too close to the sun, and fucked up. I was trying to upgrade a small site from Drupal 9.3 because something under the hood was stopping image files from uploading. Unfortunately, I didn't read the instructions on upgrading correctly. While going from 9.3 to 9.5 went fine, at the next step, it went all the way to 11.3, which has rendered the site unreachable, except for the update.php page.
The problems I'm facing are:
So, my question is:
I should add that there's something weird going on with the installation of Drush I'm working with as it seems to only be interacting with one of the multiple sites we have with this hosting provider, and it's not the problem site.
I've been using Drush on Drupal 7 for a long time, but having started on Drupal 11 I've gotten more used to the Composer approach and see on Drupal.org that many Drupal 7 modules can be installed through composer.
Are there any gotchas installing Drupal 7 and installing/upgrading modules with composer?
Is Composer usage on Drupal 7 mature and comparable or even better than Drush?