Build And Push Image / docker (push) Successful in 3m52sDetails
- Add guest settings to event creation with configurable max guests per person
- Implement guest selection in RSVP form when guests are permitted
- Update API endpoints to handle guest count in RSVP requests
- Extend event and RSVP types to support guest-related fields
Build And Push Image / docker (push) Successful in 3m25sDetails
- Add proper TypeScript type annotations and assertions
- Handle string/number conversion for attendee counts consistently
- Improve null/undefined checks for events array
- Make event handlers async for better error handling
- Fix data type inconsistencies between components and API
Build And Push Image / docker (push) Successful in 3m13sDetails
- Fixed conflicts in server/api/events/index.get.ts with improved logging and session management
- Fixed conflicts in server/api/events/index.post.ts with better validation and error handling
- Fixed conflicts in server/utils/nocodb-events.ts incorporating admin config integration and token validation
- Events system now uses proper session management and NocoDB v2 API patterns
- Maintains compatibility with existing admin configuration system
Build And Push Image / docker (push) Successful in 3m22sDetails
- Removed ALL filtering (dates, status, search, role-based)
- Removed ALL sorting
- Added comprehensive debug logging
- This will test if even basic field filtering causes 422 errors
- Goal: Isolate exactly what NocoDB query syntax works vs fails
Build And Push Image / docker (push) Successful in 3m34sDetails
Root cause identified and fixed:
- Events table uses 'Id' (capital I) not 'id' (lowercase)
- Fixed all field references to use correct NocoDB field names
- Added proper filtering with gte/lte operators (btw didn't work)
- Fixed RSVP lookup to prevent undefined event ID errors
- Updated calendar transformation to use correct field names
Debug findings showed:
- Basic table access works (mp3wigub1fzdo1b confirmed correct)
- Sample record revealed actual field structure
- Issue was field name mismatch causing undefined IDs in queries
This should resolve all 422 errors and make events calendar functional
Build And Push Image / docker (push) Successful in 3m20sDetails
- Added comprehensive logging to identify exact table access issues
- Will show actual field names from events table if query succeeds
- Will show detailed error information if query fails
- This will help identify if issue is field names, permissions, or other factors
- Uses emojis for easy log scanning in production
Build And Push Image / docker (push) Has been cancelledDetails
- Completely stripped down query to test if basic API call works
- No where clauses, no sorting, just limit/offset
- Added debug logging to identify the root cause
- This will help determine if issue is with query syntax or basic connectivity
Build And Push Image / docker (push) Waiting to runDetails
- Use btw (between) operator for date ranges instead of gte/lte
- Use proper ~or and ~and logical operators for complex conditions
- Use like operator with %wildcards% for search functionality
- Role-based filtering with correct OR conditions for board visibility
- All query syntax now matches official NocoDB v2 API documentation
This should resolve the 422 Unprocessable Entity errors by using the
correct query parameter format that NocoDB expects.
Build And Push Image / docker (push) Has been cancelledDetails
- Removed complex query conditions to isolate the issue
- Using simple (status,eq,active) query to test field names
- Will build up complexity once basic queries work
Build And Push Image / docker (push) Successful in 3m20sDetails
- Updated all where clauses to use NocoDB v2 syntax: (field,operator,value)
- Changed SQL-like syntax (field >= 'value' AND field = 'value') to v2 format
- Fixed date range queries: (start_datetime,gte,date) and (start_datetime,lte,date)
- Fixed equality queries: (status,eq,active) instead of (status = 'active')
- Fixed AND/OR logic: ~and() and ~or() syntax for complex conditions
- Updated findEventRSVPs, findUserRSVP, and findUserEvents methods
- Fixed RSVP queries to use proper v2 format for member and event matching
This should resolve the 422 Unprocessable Entity errors that were caused by
using deprecated SQL-like syntax with the v2 API endpoints.
Build And Push Image / docker (push) Successful in 3m15sDetails
- Updated all NocoDB API calls from v1/db/data/v1/ to v2/tables/ endpoints
- Fixed 422 Unprocessable Entity errors on events calendar page
- Ensures consistency with members system which already uses v2 API
- Updated methods: findAll, findOne, create, update, delete, createRSVP, findEventRSVPs, findUserRSVP, updateRSVP, updateAttendeeCount, findUserEvents
- Maintains same functionality while using correct API version
Resolves continuous 422 errors when loading events calendar.
Build And Push Image / docker (push) Successful in 3m24sDetails
- Add events and rsvps table ID fields to NocoDB settings dialog
- Replace mock getUserSession with proper SessionManager integration
- Improve type safety with explicit type casting and error handling
- Add comprehensive events system bug analysis documentation
Matt