Skip to content

Require visible register consent with a stored timestamp - #205

Merged
apescic-director merged 2 commits into
mainfrom
cursor/feature/124-register-consent-timestamp
Sep 12, 2026
Merged

apescic-director merged 2 commits into
mainfrom
cursor/feature/124-register-consent-timestamp

Conversation

@apescic-director

@apescic-director apescic-director commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

Fixes #124

Public registration now requires a visible terms and privacy tick before an account is created, and stores that moment on the public local account.

What this changes

  • Register shows a required consent checkbox that links to /terms and /privacy (cookies and Help stay available)
  • Submit is rejected without consent
  • Successful registration writes registration_consented_at on the public local account
  • Existing accounts stay null; the new column is not backfilled

Tests

  • Register page shows the required consent control and legal links
  • Registration without consent does not create an account
  • Successful registration stores the frozen consent timestamp
  • Existing registration, legal-page, schema, and version-pinned tests updated

Release metadata

This PR includes v0.32.11 (VERSION, resources/data/releases.json, resources/data/module-runtime-contract.json). php artisan myapes:changelog-validate --base-ref=origin/main passed on the branch.

Open in Web Open in Cursor 

Public registration now asks for an explicit terms and privacy checkbox, blocks submit without it, and records registration_consented_at on the local account.

Co-authored-by: APES Director <apescic-director@users.noreply.github.com>
Keep the consent timestamp work in the same PR as VERSION, releases.json, and the runtime contract.

Co-authored-by: APES Director <apescic-director@users.noreply.github.com>
@apescic-director
apescic-director marked this pull request as ready for review September 12, 2026 17:47
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 12, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-12T17:52:02.850473Z 40c6ec4 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 40c6ec4c87

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

public function up(): void
{
Schema::table('users', function (Blueprint $table): void {
$table->timestamp('registration_consented_at')->nullable()->after('onboarding_completed_at');

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Verify the consent column in the post-migration gate

In the Cloudron activation path, scripts/deploy/activate-release.sh runs migrate and then myapes:accounts:check, but AccountLifecycleReadinessChecker::check() still verifies only username and onboarding_completed_at. If migration history and schema drift apart so this migration is recorded while the new column is absent, activation succeeds and every consented registration then fails when the controller inserts registration_consented_at. Add this column to the post-migration schema check and cover the missing-column failure.

Useful? React with 👍 / 👎.

@apescic-director
apescic-director merged commit 5110d36 into main Sep 12, 2026
3 checks passed
@apescic-director
apescic-director deleted the cursor/feature/124-register-consent-timestamp branch September 12, 2026 17:52
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.

[v1.1.0] 11 [Story] Register requires visible consent with a stored timestamp

2 participants