I see the issue. We're encountering the same problem with the ParkingSpacesManagement component. Let me fix this component as well:

I've fixed the issue with the ParkingSpacesManagement component by applying a similar approach to what we did with the SiteSettingsManagement component:

1. Updated the ParkingSpacesManagementProps interface to make all dictionary properties optional with the ? operator.

2. Created a comprehensive fallback dictionary object that provides default English text for all the labels and messages:

   const dict = { title: dictionary?.title || "Parking Spaces", description: dictionary?.description || "Manage individual parking spaces in your facility", // ... other default values sections: { title: dictionary?.sections?.title || "Parking Sections", // ... other section default values }, statusOptions: { available: dictionary?.statusOptions?.available || "Available", // ... other status option default values } }
3. Used this dict object throughout the component instead of directly accessing the dictionary prop.

This approach ensures that the component will work even if some or all of the translations are missing. It provides a robust fallback mechanism that will display English text when translations are not available, which is a good practice for internationalization.

Now the component should work correctly regardless of which language is selected, even if the translations for the parking spaces management section are incomplete or missing entirely.

I'll apply the same fix to the PricingManagement component to handle missing translations:

I've applied the same fix to the PricingManagement component:

1. Updated the PricingManagementProps interface to make all dictionary properties optional by adding the ? operator to each property:

   dictionary: { title?: string vehicleTypesPricing?: string // ... other optional properties }

2. Created a comprehensive fallback dictionary object with default English text for all labels and messages:

   const dict = { title: dictionary?.title || "Vehicle & Pricing Management", vehicleTypesPricing: dictionary?.vehicleTypesPricing || "Vehicle Types & Pricing", // ... other default values success: { vehicleAdded: dictionary?.success?.vehicleAdded || "New vehicle type added successfully", // ... other success messages } }
3. Used this dict object throughout the component instead of directly accessing the dictionary prop.

4. Updated the success message references to use the fallback dictionary:

   onSuccess(dict.success.vehicleAdded)

This approach ensures that the component will work correctly even if some or all of the translations are missing from the dictionary. It provides a robust fallback mechanism that will display English text when translations are not available.

Now all three components (SiteSettingsManagement, ParkingSpacesManagement, and PricingManagement) have been updated to handle missing translations gracefully, which should resolve the errors you were encountering when viewing the admin dashboard in different languages.