Skip to content

chore(release): v1.0.1 - #8

Merged
dpk404 merged 4 commits into
mainfrom
develop
Jun 30, 2026
Merged

dpk404 merged 4 commits into
mainfrom
develop

Conversation

@dpk404

@dpk404 dpk404 commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

Release v1.0.1 — promotes develop to main.

Included

  • feat: file_ids attachment handling on CRM Lead creation (feat: relink uploaded files via file_ids on lead create #6)
    • upload_lead_file returns file_id; create accepts file_ids to re-link already-uploaded files to the new lead (no duplicate File), with a single permission-scoped get_list.
    • A file_id already attached elsewhere is not moved — a new File is created from its file_url, which DFP points at the same stored object (shared copy, no re-upload).
    • Fixes the DFP External Storage rejection (http(s)://file(s) not ready to be saved…) and the duplicate-File / "Local file not found" failures from the old external-URL path.
    • Verified end-to-end against a real S3-compatible bucket (Backblaze B2).
  • docs: README updated for the file_ids upload-first flow; plugin repo link renamed gravityforms-erpnextcrm → gravityforms-frappecrm.
  • chore: __version__ bumped 1.0.0 → 1.0.1 (chore(release): bump __version__ to 1.0.1 #7).

Version

1.0.0 → 1.0.1

dpk404 added 4 commits June 9, 2026 12:36
* feat: relink uploaded files via file_ids on lead create

upload_lead_file now returns file_id alongside file_name/file_url.

create() accepts a file_ids key (comma-separated File names already
uploaded via upload_lead_file) and relinks those files to the new lead
via a single get_list + bulk db.set_value, instead of inserting
duplicate File records. The attachments key is retained for external
URLs only.

This avoids the duplicate File rows and the DFP External Storage
rejection ("http(s)://file(s) not ready to be saved...") that occurred
when an already-uploaded or external URL was passed through the old
insert path.

* feat: handle already-attached file_ids on lead create

Only relink files that are not yet attached, so re-sending a file id
already linked elsewhere is no longer silently moved.

Such ids now have their file_url queued as a new File, which DFP points
at the same stored object (a shared copy), instead of being skipped.

* refactor: scope file_ids lookup via a single permission-checked get_list

Addresses PR review feedback:
- guard empty/whitespace file_ids before querying
- fetch name, attached_to_name and file_url in one get_list instead of
  an N+1 get_value loop
- scope both the relink and reuse paths through get_list permissions so a
  caller can only act on files it can read
@dpk404
dpk404 merged commit 79effb6 into main Jun 30, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant