🇬🇧United Kingdom @yanniboi

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

Once a mysql user has been created with a password you just have to reference the user, not include the password again. The existing command will error without my change.

I've created a PR to fix this. :)

I can confirm this issue and I would suggest using the "administer feedback message entities" permission for the collection page.

We've started looking at contributor proposals :)

If you want to contribute to this please link your proposals from gsoc (https://summerofcode.withgoogle.com/) here.

I cant actually see what change you made in that fork, but I assume you mean change:

Drupal::moduleHandler()->loadInclude('install', 'decoupled_auth', 'decoupled_auth');

This has actually already been fixed in the 2.x and 3.x branches. Which branch are you trying to install?

Patch attached to provide the logged in user context to all blocks in the dashboard.

Tests are failing/passing as expected:

• https://github.com/penyaskito/dashboard-initiative/pull/26
• https://github.com/penyaskito/dashboard-initiative/pull/27

@plopesc patch 13 is an empty file :P

Tests failed on coding standards

I'm attaching a js test to cover the changing and saving of a dashboard with a form block present.

I am assigning this to myself and will try to work on this during DrupalCon Lille. If I dont make any progress I will unassign myself again.

What @hansfn is saying is true, it is very simple to create a content type and a views block. However, I very frequently have clients that just want to insert a specific bit of helper text into a UI. Maybe its a clarification about what should and should not be done or its just a temporary holding message. If there are several columns and rows on a dashboard there might be several blocks with adhoc text to be added in different areas.

An additional (huge) benefit of having a specific block time with config fields means that the text can be exported to site config and deployed with the block instances which avoids having to have to add the copy as content on production after a new feature is deployed.

yanniboi → created an issue.

penyaskito → credited yanniboi → .

added to menu

Updated description

I am not sure if @dabley's issue is related, however it looks like since mailchimp-api-php has release release candidate 6 with the API fix included we can now update the version dependency of mailchimp module.

yanniboi → created an issue.

Patch attached

yanniboi → created an issue.

yanniboi → created an issue.

Thanks a lot

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

Looks great!