❌

Normal view

Received — 19 July 2026 ⏭

All the extra features added to Drupal core trigger too many update bulletins.

✇Drupal - Open Source Content Platform | #Celebr8D8
By: /u/NappyDougOut
19 July 2026 at 23:40
All the extra features added to Drupal core trigger too many update bulletins.

Patchman has been going crazy fir me over the past year, and it also breaks my sites at times, greatly reducing reliability of Drupal as a solution overall....

Based on this recent bulletin (attached), it shows layout builder was cited this time. I don't use layout builder, and I'm sure others don't as well, so technically, it should possibly be an optional module, rather than included with Drupal core, along with some of the other outlying features included in core perhaps, reducing the tool bloat could also probably reduce a lot of frequent update headaches for users, and reduce overall footprint of Drupal.

If some of these features (like even views) were modules instead of in core, updates could also be performed separately from core updates as well (as was done in D7 prior).

There probably shouldn't be a strict model for developing Drupal in any one way, included in Drupal core, especially because it is an open source framework.

Just a suggestion for evaluation, Plz don't kill the messenger. 🤔⚠️✨

Tanks.

submitted by /u/NappyDougOut
[link] [comments]

What do you do with records that are not clean enough to import, but not obviously wrong enough to delete?

✇CRM - Customer Relationship Managment
By: /u/ahhrsa
19 July 2026 at 22:21

I keep running into the same issue with CRM imports:

Some rows are clearly fine.

Some rows are clearly trash.

But the painful ones are in the middle.

Examples:

same email, different phone

same phone, different name spelling

same company, slightly different title / city / source

records that look mergeable, but not safely

The obvious stuff is easy.

What I’m trying to understand is the middle zone.

How do you actually handle that at scale before import?

Do you:

hold them back in a review bucket

manually label them

merge conservatively

import and fix later

just accept some contamination

I’m not asking for theory. I mean your actual workflow.

submitted by /u/ahhrsa
[link] [comments]

Looking for a CRM for a small business (11 users) that only want to use it for contacts, basic opportunity tracking and notes entered against the contacts.

✇CRM - Customer Relationship Managment
By: /u/badboybubbykitty
19 July 2026 at 20:11

I specifically want to be able to export those notes, weekly, and use them for a sales report, but Hub Spot dont do this unless you pay for the next tier up, and Nimble dont have the functionality. Can anyone recommend one? Its esentially something we could run out of an excel spreadsheet so we're looking for something cheap. Thankyou!

submitted by /u/badboybubbykitty
[link] [comments]

Critical NGINX Vulnerability Can Crash Workers and May Allow Remote Code Execution

✇The Hacker News
By: [email protected] (The Hacker News)
19 July 2026 at 15:42
F5 has shipped fixes for a critical nginx flaw that lets a remote, unauthenticated attacker trigger a heap buffer overflow in the worker process with crafted HTTP requests. CVE-2026-42533 was patched on July 15 in nginx 1.30.4 (stable) and 1.31.3 (mainline), and in NGINX Plus 37.0.3.1; anyone on an earlier build should upgrade. Triggering it can crash or restart the worker, causing a denial of

Would you combine prospecting and CRM in one platform?

✇CRM - Customer Relationship Managment
By: /u/No-Entertainer8410
19 July 2026 at 09:16

For people who actively use a CRM for outbound sales, do you prefer keeping prospecting, enrichment, outreach, and CRM as separate tools, or would you rather manage more of the workflow in one place?

For example, would it be useful to define your ICP and receive a smaller list of already-researched and qualified companies, including the right decision-makers, enrichment data, why they match, and why they may be worth contacting?

Only approved leads or positive replies would then be added to the actual CRM, rather than filling it with every prospect.

Would that make your workflow easier, or do you prefer using tools such as Sales Navigator, Clay, Apollo, outreach software, and your CRM separately?

What would a combined platform need to do before you would consider using it instead of your current setup?

Thanks for any constructive feedback!

submitted by /u/No-Entertainer8410
[link] [comments]

Manual managed CRM or AI-integrated CRM?

✇CRM - Customer Relationship Managment
By: /u/void_craft06
19 July 2026 at 09:10

We (our team) recently made a few websites for a college, integrating a CRM system to make the application process and customer service easier. It was AI-integrated.

We want to know whether a manually managed CRM system is more effective than an AI-integrated CRM, if so, then in what ways? Advantages, limitations and other things.

submitted by /u/void_craft06
[link] [comments]

UAC-0145 Uses ClickFix CAPTCHAs to Infect Ukrainian Devices wih Malware

✇The Hacker News
By: [email protected] (The Hacker News)
19 July 2026 at 08:30
Russian state-sponsored threat actors have been observed leveraging the infamous ClickFix strategy to trick Ukrainian targets into infecting their own machines with data-stealing malware. According to the Computer Emergency Response Team of Ukraine (CERT-UA), the activity has been attributed to UAC-0145, a sub-cluster within Sandworm, an advanced hacking unit affiliated with GRU, Russia's

SonicWall SMA Zero-Days Exploited Before Disclosure to Gain Root Access

✇The Hacker News
By: [email protected] (The Hacker News)
19 July 2026 at 08:18
A previously undocumented threat actor has been attributed to the exploitation of recently disclosed SonicWall Secure Mobile Access (SMA) 1000 series VPN appliances as zero-days prior their public disclosure since June 22, 2026. Cybersecurity company Volexity is tracking the activity under the moniker UTA0533. The discovery was made following an incident response investigation earlier this

Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1

✇DigitalOcean Status - Incident History
19 July 2026 at 10:32

Jul 19, 15:32 UTC
Resolved - Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all 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.

Jul 19, 14:52 UTC
Monitoring - Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues.

We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

Jul 19, 13:36 UTC
Update - We are continuing to investigate this issue.

Jul 19, 13:34 UTC
Update - We are continuing to investigate this issue.

Jul 19, 09:51 UTC
Investigating - Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1, NYC3, SGP1, SYD1 and BLR1 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.

Networking in BLR1

✇DigitalOcean Status - Incident History
19 July 2026 at 04:52

Jul 19, 09:52 UTC
Resolved - Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Jul 19, 09:31 UTC
Monitoring - Our engineering team has implemented the necessary fixes affecting upstream network connectivity for Droplet-based services in the BLR1 region. Users should now be able to connect to the external endpoints from Droplets in BLR1.

We are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

Jul 19, 08:27 UTC
Identified - Our Engineering team has identified an issue affecting upstream network connectivity for Droplet-based services in the BLR1 region and is actively working with the relevant upstream providers to implement a resolution.

Customers may continue to experience intermittent timeouts or connectivity issues when attempting to reach external endpoints from Droplets in BLR1.

We will provide another update once the issue has been fully resolved or when additional information becomes available.

Jul 19, 06:57 UTC
Investigating - We are currently investigating an issue affecting outbound network traffic for Droplets in the BLR1 region. Customers may experience timeout errors or connectivity issues when attempting to reach external services.
Our Engineering team is actively investigating the issue and working to identify the root cause. We will provide additional updates as soon as more information becomes available.

❌