Account created on 22 September 2017, about 8 years ago
#

Merge Requests

More

Recent comments

vnech changed the visibility of the branch 3552070-replace-legacy-profile-fields to active.

vnech changed the visibility of the branch 3552070-replace-legacy-profile-fields to hidden.

Hi @nathaniel_pw

DXPR Builder allows you to create and edit rich content through the UI. In Drupal, the content is not exportable as part of configuration management. This is because Drupal's configuration export system is designed to handle site settings and structure (like content types and views), but not the actual content itself.

If you need to export content, these modules could be a good candidate to use - Single Content Sync , , etc.

Hi @smurferboy,
Could you please update the DPXR Builder to the latest version and tell us if the issue still exists?

Hi @issacliew789, I can't reproduce the error.
Is it still relevant? If yes, it would be nice if you could provide more details on how to reproduce it.

Hi @lagupe, I can't reproduce the error.
Is it still relevant? If yes, it would be nice if you could provide more details on how to reproduce it.

Hello,

Starting from v.2.7.0, DXPR Builder is compatible with Acquia DAM.
To use it, you need to choose the "Media Library (Acquia DAM)" media browser on /admin/dxpr_studio/dxpr_builder/settings.

Hello,

Starting from v2.6.0 "Image carousel" component is using the SortableJS library, which allows you to change the order of carousel slides using the drag-and-drop image thumbnails on the component settings.

Hello, the issue does not reproduce with the following stack:

• Drupal 11.1.7

• DXPR Builder 3.0.0-alpha58

We're closing the issue as outdated (and not reproducible with the latest versions of the stack used).

In general, after the module uninstalling, it's required to clear the cache to update node type definitions.

Hello, the issue is fixed in 2.5.x.
The \Drupal\dxpr_builder\Service\DxprBuilderService::replaceBaseTokens() method checks if the str_replace() receive non-empty string (see).

Hello, the issue does not reproduce with the following stack:
- Drupal 11.1.7
- DXPR Builder 3.0.0-alpha58
- DXPR Theme 6.0.0

We're closing the issue as outdated (and not reproducible with the latest versions of the stack used).

Hello, the issue does not reproduce with the following stack:
- Drupal 10.0.9
- DXPR Builder 3.0.0-alpha58
- DXPR Theme 6.0.0

We're closing the issue as outdated (and not reproducible with the latest versions of the stack used).

We can't reproduce the issue. Could you please provide more details about the issue?

Hi @fabianderijk
Could you please change the target branch to 6.x in MR #34? I can't do this (seems like I don't have permissions)...

I tested the changes from MR #34 and everything works as expected.

HTT:

  1. Apply MR #34 patch
  2. Run drush updb -y; drush cr
  3. In you settings.php add following settings:
    // Specific settings for "o365" authentication connectors.
    $settings['o365']['default']['client_id'] = '{PLACEHOLDER}';
    $settings['o365']['default']['client_secret'] = '{PLACEHOLDER}';
    $settings['o365']['default']['tenant_id'] = '{PLACEHOLDER}';
      

This issue isn't relevant anymore as group member AU can see public groups only.
See https://www.drupal.org/project/social/issues/3504318 As AU I should have access to public groups only Needs review

vnech made their first commit to this issue’s fork.

vnech changed the visibility of the branch 3490185-improve-small-teaser to active.

vnech changed the visibility of the branch 3490185-improve-small-teaser to hidden.

vnech changed the visibility of the branch 3490185-improve-small-teaser to active.

vnech changed the visibility of the branch 3490185-improve-small-teaser to hidden.

Production build 0.71.5 2024