🇮🇳India @anjali rathod

I am thinking of doing something like this. Any suggestions or if there is any better way to implement it?

Should we have separate icon set for different entity types? This would mean to have another field added to each entity type and user if has set the logo for the entity then it would appear otherwise fallback to database icon. Or should we have another field for icon in the module configuration form that would replace the default icon and would be same across all the entities.

Sure!
I will be working on this.

Adding screenshots for how the navigation menu for a page set as homepage looks and how the navigation menu for a page not set as homepage looks like..

I have removed the set as homepage link along with the delete page link from navigation menu for the page set as homepage. For other pages there is no changes.

anjali rathod → created an issue.

Since there is no entitylistbuilder implementation for xb page content type, I went ahead with the approach I could think of. @wim leers please let me know if this is okay or should I create a entitylistbuilder and make the changes accordingly?
Thank you!

@jessebaker by autoSavePath do you mean a path similar to /xb/xb_page/1/editor ?
Because the path key value pair returned from /xb/api/content/xb_page gives the path for the autosave entity.

I have updated the warning message and added the suggestion by @wim leers in #11.
If it still doesn't suit then maybe @laurii can provide the message that is to be displayed.
Thank you!

thejimbirch → credited anjali rathod → .

@wim leers Yes. Should I go ahead with the approach I shared in #4 ?

const {
    data: pageItems,
    isLoading: isPageItemsLoading,
    error: pageItemsError,
  } = useGetContentListQuery('xb_page');

on PageInfo.tsx

Here we are getting the pageItems from ApiContentControllers::list() , which returns content values from $this->entityTypeManager->getStorage('xb_page'); entity . But since these are not published yet the value shows the last saved title or Untitled Page incase of new page. Inorder to reflect the immediate changes in the title in navigation drop down, we need to call and generate similar pageItems from AutoSaveManager::getAllAutoSaveList() .
This is my POV . Any feedback or suggestions are appreciated!

anjali rathod → made their first commit to this issue’s fork.

Attaching updated preview of the Block UI page.

I attempted to reproduce the issue mentioned, but I wasn’t able to encounter the same behavior. I’ve attached a screen recording showing my test scenario and the expected outcome.

surabhi-gokte → credited anjali rathod → .

anjali rathod → created an issue. See original summary → .

I am facing issue setting up the responsive preview module. Attaching the screen recording video for reference.

Need review for the API related changes made by me, so that @parthbcharya can then continue working with these changes for React code part.

I will be working on the API part of this issue and then my colleague parthbcharya will take over the FE work. I’m unclear about which API to use for my current task in experience_builder. Should I leverage an existing API route, extend one of the current routes, or consider creating a new API from scratch?

I’d appreciate some guidance to understand the best approach for this scenario.

john cook → credited anjali rathod → .

john cook → credited anjali rathod → .

Hi @azslay I tried to replicate your issue and failed to do so, for me the scenario provided by you works fine.
I embedded the default contact webform which has all the fields as required. Then added a paragraph to the basic page content type and edited the node and entered the value for the same and was able to save the page with empty fields in webforms without any error message.
Is there something that I missed here?

Anjali Rathod → created an issue.

Applied the patch

1. Created a new domain.
2. Exported the configurations.
3. The system.action files were found having correct config name, under dependencies.

Hence, marking it as RTBC.
Thanks @tim-diels