Update ForeignKey reference in PublishingRecord model and enhance integration app configuration

- Changed ForeignKey reference from 'content.Content' to 'writer.Content' in PublishingRecord model to ensure correct app_label usage.
- Updated IntegrationConfig to use a unique label 'integration_module' to avoid conflicts.
- Added 'lucide-react' dependency to package.json and package-lock.json for improved icon support in the frontend.
- Enhanced Vite configuration to optimize dependency pre-bundling for core React dependencies.
- Added Phase 5 Migration Final Verification and Verification Report documents for comprehensive migration tracking.
This commit is contained in:
IGNY8 VPS (Salman)
2025-11-18 00:54:01 +00:00
parent a6a80ad005
commit 9facd12082
9 changed files with 4259 additions and 3 deletions

Binary file not shown.

View File

@@ -20,7 +20,7 @@ class PublishingRecord(SiteSectorBaseModel):
# Content or SiteBlueprint reference (one must be set)
content = models.ForeignKey(
'content.Content',
'writer.Content',
on_delete=models.CASCADE,
null=True,
blank=True,

View File

@@ -7,6 +7,6 @@ from django.apps import AppConfig
class IntegrationConfig(AppConfig):
default_auto_field = 'django.db.models.BigAutoField'
name = 'igny8_core.modules.integration'
label = 'integration'
verbose_name = 'Integration'
label = 'integration_module' # Unique label to avoid conflict with business.integration
verbose_name = 'Integration Module'