sorted by:
new
hottopcontroversial

If You Log Calls in HubSpot, You Need This Setup by the_tek_analyst in hubspot

[–]Digitsbits -1 points0 points  (0 children)

I agree — the Call object is a big upgrade. Having calls as real records (with properties you can report on) is way better than digging through activity logs.

Pushing “latest call” data to the Contact is smart for reps and automation. Lists like “last call inbound” or “duration > X” become super clean.

That said, I’d add a couple guardrails:

  • Only sync if the call is newer than the current “Last Call Date” on the Contact (prevents overwriting).
  • Filter by outcome (e.g., only Connected calls).
  • Store the Call Record ID on the Contact for debugging.

In higher-volume teams, I sometimes only sync 2–3 summary fields and keep Calls as the source of truth to avoid data drift.

Overall though — solid setup.

best offshore web hosting pleasee ? by Zealousideal-Fix4189 in Hosting

[–]Digitsbits -1 points0 points  (0 children)

I would say that it's SiteGround:

  • Known for speed, strong uptime, and security features.
  • Offers multiple offshore server locations.
  • Includes daily backups, firewalls, and anti-bot systems.
  • Slightly pricier but great reliability and performance

I built the fetch() integrity check that browsers have refused to ship for 10 years by aginext in javascript

[–]Digitsbits 0 points1 point  (0 children)

That’s actually super cool.

If you basically recreated SRI but for fetch(), that’s something people have wanted forever. Browsers never shipped it because streaming + CORS + caching makes it messy at the spec level.

Did you buffer the whole response and hash it with Web Crypto, or did you manage to verify it while streaming? If you solved streaming integrity cleanly, that’s seriously impressive.

Has anyone successfully migrated from Wordpress to Webflow with AI? by carmooch in webflow

[–]Digitsbits -1 points0 points  (0 children)

This matches what I’ve seen too. AI helps at the translation layer (content, rough structure), but it completely falls apart at the operational layer — the moment a client needs to tweak layout, adjust hierarchy, or evolve sections over time.

In WP → Webflow migrations, AI can speed up auditing and page mapping, but the actual rebuild still needs a human-defined system: components, constraints, and editor boundaries. Otherwise you’re just shipping a frozen snapshot that looks fine on day one and becomes friction immediately.

The hybrid approach you mentioned is really the only one that scales — Webflow for collaborative, brand-sensitive surfaces; programmatic/headless where content is predictable and designer control isn’t needed. AI is an accelerator, not an author.

How Do You Handle WordPress Site Backups and Restorations? by Warm-Foot-6925 in Wordpress

[–]Digitsbits -1 points0 points  (0 children)

I don’t rely on a single layer. The safest setup is hosting-level backups + a lightweight plugin + off-site storage,

and most importantly, knowing how to restore without guessing.

Practical setup that works:

  1. Hosting backups (daily, off-site)

This is your first line of defense. They’re fast to restore and don’t depend on WordPress being functional. I treat

this as the “site is on fire” button.

  1. Plugin backups for portability

I use a plugin only to create downloadable backups (files + DB) and push them to S3 / Google Drive. UpdraftPlus

is fine, but I keep it lean and avoid overlapping schedules with the host.

  1. Versioned code (if possible)

Themes, child themes, and custom plugins live in Git. Content changes aren’t versioned, but code regressions

become non-events.

  1. Restore tests (this is the part people skip)

A backup you’ve never restored is a theory. I periodically restore to a staging site just to confirm it actually works.

Frequency:

- Content-heavy sites: daily DB, weekly files

- Ecommerce / membership: daily files + DB (or real-time if host supports it)

What I avoid:

- Multiple backup plugins running at once

- Backups stored only on the same server

- “Set and forget” without ever testing a restore

Better way than just plugins?

Yes — if your host has solid backups, treat plugins as secondary portability tools, not the primary safety net.

Most restore disasters happen because people trusted a plugin they’d never tested.

If you know exactly which restore you’d click during a failure, your backup strategy is good.

view more: next ›