Account created on 23 March 2015, about 9 years ago

Merge Requests

Recent comments

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Confirmed this happens on webform_migration for 2.0.x and Drupal 10.2.5

Settings form element from '#unique: false' to '#unique: NULL' resolves this webform unique issue.

Set the branch target to 2.0.x-dev

Provides MR and update patch for 2.0.x-dev that resolves this bug, set back to NR.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei
   * Display last registered user to visitors block.
  protected function showLastRegisteredUser(): string {

    $last_user_uid = $this->database->select('users', 'u')
      ->fields('u', ['uid'])
      ->orderBy('uid', 'DESC')
      ->range(0, 1)

    $user = $this->entityTypeManager->getStorage('user')->load($last_user_uid);
    $username = [
      '#theme' => 'username',
      '#account' => $user,

    $item = $this->t('Last Registered User:') . $this->renderer->render($username);

    return $item;

#12 applies cleanly to 2.x-dev, but the render array of 'Last registered user' still escapes html element, setting back to NW, thanks!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Created MR for 6.2.x

Providing another patch that applies against 6.2.2

Set to NR.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei
+++ b/src/Plugin/Block/VisitorsBlock.php
@@ -265,7 +265,7 @@ final class VisitorsBlock extends BlockBase implements ContainerFactoryPluginInt
+    $item = $this->t('Total Visitors:') .$count;

@@ -295,7 +295,7 @@ final class VisitorsBlock extends BlockBase implements ContainerFactoryPluginInt
+    $item = $this->t('Registered Users:') .$registered_users_count;

Thanks for the patch, works fine on 2.16, just some nit picks I see here, need to add space for concatenation.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

This issue seems to be an duplicate of πŸ› Remove Not rendering HTML Needs work , closing this issue since the other has provided a valid patch that works.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Even though this issue is postponed, I ran into this request earlier today and needed a patch to allow ckeditor5 to work with uploading webp files.

I'm leaving this MR for the future when other dependent issues are resolved, or others who may need a quick fix to make use of this as a patch.

Tested with 10.1.x
Hope this helps, Thanks!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

g-brodiei β†’ made their first commit to this issue’s fork.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Provide gif to prove result after applying patch.

Add 1 count per page reload+cron run.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

I have encountered the same issue and scenario as OP, after looking into this code. I've made change to assure the renderStrategy string may be fetched from the correct source, whether it's from the Plugin Configuration or the settings object.

Settings to needs review.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

You're welcome, glad it worked out for you!

Removing assigned, and hopefully a lovely person may review the code to set it to RTBC (reviewed and tested by the community), then that will be terrific!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Hi @binkdot5,

On what version are you using atm? I've generated this patch for 8.x-1.x, which is tagged as 2.0.1

If the patched was skipped, then the patch will not take effect at all.

How I patched the project was like the following:

composer require drupal/role_login_page:^2.0
composer require cweagans/composer-patches:^1.7

Under composer.json, look for the extra section, add a patches within.

You can either use the online patch file, or download it into a directory locally for composer to use (point it to './patches/xxx.patch')

Once it's updated, use composer install to apply the patch
composer install

Hope it works for you. We're using drupal 9.5.10, role_login_page 2.0.1

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

This issue is caused by the stdClass fetched from DB that was set as default param in the route class.

Attempt to resolve this by converting stdClass data into array, and update the way how data are fetched within the module code base.
(e.g. from using '->' to ['key']).

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Since this is merely a document change, I believe the description is now clear to explain what this method do as OP originally proposed.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Applied patch cleanly to 10.1.1

Changes are seen on web/core/lib/Drupal/Core/Test/FunctionalTestSetupTrait.php

Set to RTBC

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Thank you for spending time to attend to this issue!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Trying to reproduce with the following steps, but the issue described did not show.

  1. Installed Drupal version: 10.0.9 locally
  2. Copy example.settings.local.php to /sites/default/settings.local.php
  3. Uncomment last paragraph to in settings.php to take settings.local.php to override
  4. Check has the following http.response.debug_cacheability_headers: true under parameter section.
  5. Clear cache
  6. Open site homepage and chrome devtools
  7. Navigate to Network tab on devtools and click on the homepage link shown in image
  8. See response headers for X-Drupal-Cache-Contexts, X-Drupal-Cache-Max-Age, X-Drupal-Cache-Tags, X-Drupal-Dynamic-Cache
  9. The Response Headers show as expected, can't reproduce
πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Hi @lanapt,

For module development, you may look into Documentations of module creation. β†’

For examples on the possibilities, check the examples project where it provides detailed comment within the project code to demonstrate ideas of what a module could do and override. β†’

As for the scenario you described, yes it's doable, but you may have some parts to consider and implement before putting your site into public.
Such as:

  1. Spam bots, publicly exposed form may be spammed and attacked by bots, which will consume most of your Openai API usage and exceed the limit, you won't want to wake up and see a huge bill by the end of the month. There are numerous modules that handles this on Drupal.
  2. Safety best practice on usage of AI tools, please look into
  3. Billing limit,
  4. How to write secure code in Drupal, β†’
  5. For more where you need support, please seek help and suggestion on the slack channel #support or #openai

I'm going to close this issue as the original issue is resolved. Best of luck!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Hi @lanapt,

You might need to recheck the credentials you have provided on /admin/config/openai/settings page.

I just bumped into the same issue like yours this morning, it turn out to be me using 'Personal' as the organization id.

It should be 'org-xxx', can be found on page.

Hope this helps, cheers.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Haha, it must be confusing, thanks for spending the effort double checking, cause I still didn't see it on my account page, probably it's a cache problem.

Will wait and see, cheers!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Hi @larowlan, thanks for crediting everyone, just wanted to check if there is a mis-credit between the two Michaels? (@mstrelan) and me (@g-brodiei)?

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Followed the steps from summary with screenshots, and can't reproduce this issue as well.
Closing this bug as cannot reproduce, if OP may be able to reproduce, please reopen this issue and update the reproduce steps, thanks!

  1. Install new site with standard profile [Success, I choose 10.0.8 and 9.5.8]
  2. Enable Interface translation module [automatically installs dependency language module]
  3. Add a new language (French in this case) [same]
  4. Keep english as default language [same]
  5. In language Detection and selection page enable only User and Selected language detection methods [same]
  6. Select French in Selected language configuration page [same]
  7. Edit your admin account and select English in Site language [same]

Final result:
P.S. The screen shot was taken after I finished the config setup with admin logged in. So the interface appears in English.

Logged in as admin, displays English interface:

Logged out viewing as anon, displays French interface:

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Updated steps to reproduce and manually tested on 9.5.x

The issue is no longer valid on 9.5.x. and 10.1.x (see screenshot)

Closing it as cannot reproduce.

If this is issue still valid for OP to reproduce on a fresh Drupal install, please reopen it and adjust the steps to reproduce for future contributors to debug. Thanks!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Checked the page β†’ , wording changed as suggestion, thanks!

Set to RTBC

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Saw this issue from bug smash initiative channel from @quietone to check wordings on policy page.

+1 on the policy change. I’ve read through the threads and notice a slight wording diff on the policy page.

On the issue summary:
If the stale issue meets these criteria, it should be closed:

On policy page β†’ :
if an issue meets these three criteria, it should be closed:

I believe the word `three` would make it clearer for future readers (not native English speaker) to understand the criteria, thanks!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Adding new tags for steps to reproduce and requires summary update for new contributors to step in easier.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Setting status to needs review, still needs tests to be written

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Wow, didn't realize I'd get credit for this, thank you making the effort.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Hi, will you elaborate more on the situation where you'd like the custom streamwrapper to be set on image field type?

As image field may only choose it's upload destination of public/private at its field settings page by nature, I'm setting this issue as 'feature request'

If you'd like to support other upload destinations, you may take a look at project β†’ as ref for how they implements in by code.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Confirms this patch provided works for 2.0.8 and applies cleanly

Review the code implementing the same logic from \Drupal\taxonomy_manager\Controller\MainController Line 48, and works as expected

Thanks for writing this!

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Glad it helped @mattea.turnbull! We were affected while updating one of Acquia's distribution lightning/workflow.

Rewriting title for easier understanding.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Changing to critical as this bug deletes node, paragraph contents.

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

Confirms #5 patch works on drupal core 9.5.2 + amswap 3.1!
Thanks for the effort!!

Production build 0.62.1