- Issue created by @arunkumark
- 🇮🇳India arunkumark Coimbatore
Temporary Solution:
If you are keeping Use 2-step wizard when creating a new Content entity within a group the page won't break but it will not be allowed to the Group.
This issue is perhaps for the Group module rather than for Drupal Core.
- 🇮🇳India arunkumark Coimbatore
@cilefen
Yes, the form Workspace support need to done from Group. But, page break should not happen. We have to handle the exception and solving the page break. - 🇷🇴Romania amateescu
Throwing this exception is very much intentional, we need to warn developers that there's something to fix.
- 🇮🇳India arunkumark Coimbatore
Throwing this exception is very much intentional, we need to warn developers that there's something to fix.
It was better to show an error in validation or show message rather than showing the page break.
- heddn Nicaragua
I'm going to remove the group.module's submit handler and use another that uses a cron queue instead.
- heddn Nicaragua
OK, that won't work. Instead I dove into seeing if we could actually support it. It would natively support it if relationships were revisionable. Since they aren't, see ✨ Support for Revisions of Group Relationship Entities Needs review , I think we should just mark the relationship entity as ignored. Working on MR.
- heddn Nicaragua
Here's a fairly minimal solution. Which should work in most cases.
- Status changed to Needs review
3 months ago 8:31pm 5 September 2024 - 🇮🇳India vinmayiswamy
Hi, I have tested the fix provided in MR !177. I followed the steps outlined in the issue summary to reproduce the issue before applying the fix and to verify the solution afterward.
Before the fix, I encountered the White Screen of Death (WSOD) with the following error message:
Drupal\Core\Entity\EntityStorageException: This entity can only be saved in the default workspace. in Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (line 817 of core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).
Although the node was created, it wasn’t added to the group, and the WSOD appeared with the above error logged.
After applying the fix, the issue was resolved. The WSOD no longer occurred, and the node was successfully created and added to the group within the non-default workspace.
Attaching before and after screenshots for reference.
I believe this is now good to go for RTBC!
Thanks!
- Status changed to RTBC
about 17 hours ago 4:30pm 20 November 2024