I'll raise a MR as soon as I can.
amangrover90 → created an issue.
Module is successfully uninstalled and can be properly installed after pulling in the code from this branch.
@wimleers I checked both the issues, while these issues do address media/image fields and autocomplete fields, I'm not sure if it'll be enough to provide a fix for the fields that don't involve AJAX and just involve client side JS. e.g. generating a tag based on title; generating the path field based on title or any text field whose input is being set by the client side JS.
A good example to check this out could be; adding a field to an entity type e.g. summary field and updating summary based on what user types into body field by picking up first 50 words using client side JS. OR simply updating path field based on title like we were doing in https://www.drupal.org/project/experience_builder/issues/3499960 ✨ Creating a page generates the URL path dynamically when editing. Active . The JS attached to the form does update the field value but it didn't get saved in the redux state. So if one types anything in any other field or just clicks on Publish, those changes are lost.
All in all, XB UI needs to respect the JS behaviors attached to the Form by Drupal. So I think this issue is still needed to fix this for any kind of field that comes up with its own JS behaviors.
I know I'm talking somewhat generically but hope it makes sense.
Blocked on https://www.drupal.org/project/experience_builder/issues/3504063 🐛 XB UI doesn't save the media/image or fields that involve Drupal javascript. Active
amangrover90 → created an issue.
amangrover90 → created an issue.
amangrover90 → created an issue.
Sure @wim-leers.
amangrover90 → changed the visibility of the branch 3500052-provide-an-api to active.
amangrover90 → changed the visibility of the branch 3500052-provide-an-api to hidden.
amangrover90 → made their first commit to this issue’s fork.
amangrover90 → created an issue.
amangrover90 → created an issue.
amangrover90 → created an issue.
amangrover90 → made their first commit to this issue’s fork.
Rebased branch on top of 3.0.x and changed base branch to 3.0.x.
amangrover90 → created an issue.
amangrover90 → created an issue.
amangrover90 → created an issue.
e0ipso → credited amangrover90 → .
amangrover90 → made their first commit to this issue’s fork.
amangrover90 → created an issue.
This got fixed in https://www.drupal.org/project/drupal/issues/3368790 🐛 guzzlehttp/promises 2.0 blocking update to 10.1 due to AWS SDK Fixed . Drupal 10.1.x-dev core-recommended has removed direct dependency on guzzlehttp/promises. Reference: https://github.com/drupal/core-recommended/blob/10.1.x/composer.json
@rakshit.thotada CH module doesn't support partial field syndication for translations/entities, we maintain hashes based on whole entity and not based on fields.
@guaneagler you can write a form alter in a custom module and turn access to TRUE.
If you see the comment in acquia_contenthub_unsubscribe.module
/**
* @file
* Drupal Module: Acquia Content Hub unsubscribe.
*
* The experimental module provides form elements for disconnecting local
* entities from remote updates. The form elements are not accessible by
* default. Custom code is required to determine when to expose these form
* elements.
*/
it says by default form elements are not accessible by default.
It does work with drupal/core but since most of the users install drupal using drupal/recommended-project template, it makes the process trickier to uninstall drupal/core-recommended and install drupal/core.
amangrover90 → created an issue.
Closing this issue with the recommendation. Feel free to reopen.
@ashetkar can you try uninstalling acquia_contenthub_translations module and then try to import the content?
Like I mentioned in my last comment, installation of acquia_contenthub_translations module wasn't successful so it needs to be uninstalled. If you don't need this module then I would recommend not installing it unless you are trying to filter out entity translations based on subscriber site's languages.
@ashetkar, could you please provide more details about the issue?
I tried the above steps but didn't face any error accessing content page.
I believe you tried to install acquia_contenthub and acquia_contenthub_translations module.
Only reason this could have happened is that the installation wasn't successful and the acquia_contenthub_entity_translations_tracking table did not get created.
Could you plz try installing the module again and see if it's throwing the same error?
amangrover90 → created an issue.
amangrover90 → made their first commit to this issue’s fork.
amangrover90 → made their first commit to this issue’s fork.
amangrover90 → made their first commit to this issue’s fork.
amangrover90 → made their first commit to this issue’s fork.
MR resolved the issue for a use case when tag container is saved with no conditions.
mglaman → credited amangrover90 → .
amangrover90 → created an issue.
amangrover90 → created an issue.
mglaman → credited amangrover90 → .
mglaman → credited amangrover90 → .
amangrover90 → created an issue.
mglaman → credited amangrover90 → .
amangrover90 → created an issue.
Patch seems to resolve the issue.
amangrover90 → created an issue.