SSWConsulting / SSWConsulting/SSW.Rules
🦙 Bug - TinaCMS Dependency - Unable to Log in to Rules V3 (TinaCMS) for Editing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
Requested by: @GordonBeeming via YakShaver.ai 🦬
cc: @jakebayliss, @adamcogan, @GordonBeeming, @RobJT-wq, @Marxoz, @PothieuG, @Freego1783
Hi Team!
🟥 Watch the video (1 min 16 sec)
Url from screen share: https://app.tina.io/projects
Pain
User is unable to log in to Rules V3 (TinaCMS) to make edits. Despite receiving multiple invites, the user encounters an unexpected error and cannot access the correct organization.
Acceptance Criteria
- User can successfully log in to Rules V3 (TinaCMS) after accepting an invite.
- User can access the correct organization associated with Rules V3 (TinaCMS).
- No unexpected errors occur during the login process.
Reproduce Steps
- Attempt to log in to Rules V3 (TinaCMS) using the invite link sent by Rob Tomlinson or Jake Baylis.
- Observe that the login redirects to the user's personal organization instead of the intended one.
- Attempt to accept the invite link again and note any unexpected errors.
- Verify that the user still does not have access to the correct organization.
Screenshot

Figure: Unable to find other organizations in the interface
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the TinaCMS login and invitation flow at https://app.tina.io/projects using the invite link described in the issue, and compare the resulting organization access with the screenshot. Done means the invite leads to the Rules V3 organization, editing access is available, and no unexpected login error occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100