Under the CSS file organization title, in the file structure section I updated the definitions of base, layout, component, state and theme to match the CSS coding standards written in the google docs attached the following issue: https://www.drupal.org/project/coding_standards/issues/3324368 →
cindy_codediaries → made their first commit to this issue’s fork.
I followed the steps listed on comment #15. It appears the .po file in comment #11 when imported loads successfully. When I switch to the German language it translate some of the button text on the page
I absolutely love DDEV! I use it on my MacBook with Colima and on a Linux (linux mint) machine with docker and I have never had any issues with it. @rfay does a great job of maintating DDEV and he is always around to answer questions!
What triggered these steps was the comment field was empty when I attempted to translate node of article content type. The error message disappeared when I added a comment and published the article.
I attempted to translate node of article content type from English to German with moderation state of draft to publish and I received the following warning: Deprecated function: strip_tags(): Passing null to parameter #1 ($string) of type string is deprecated in Drupal\comment\CommentForm->buildEntity() (line 322 of core/modules/comment/src/CommentForm.php).
cindy_codediaries → created an issue.
The documentation didn't give a clear explanation as to how to implement advanced configuration using the Markdown Easy module. I added additional steps a user should take to implement the hooks provided for advanced configuration.
For the advanced configuration, we should include a .module file for implementing the hooks.
I don't think so either. My vote is yes merge.
I installed and configured the module. I edited a text format with the following markdown filters: markdown easy, limit allowed HTML tags and correct faulty HTML, and convert line breaks into HTML. I tried to rearrange the "Markdown Easy filter" below the "limit allowed HTML tags and correct faulty HTML" and "Convert line breaks into HTML" filters and pressed save and received an error message saying, "The Markdown Easy filter needs to be placed before the Limit allowed HTML tags and correct faulty HTML filter" and the arrangement of the filters was changed so the "Markdown Easy filter" was above the "limit allowed HTML tags and correct faulty HTML" and "convert line breaks into HTML" filters. Even though the arrangement of the filters was now in the correct order I pressed save again and I received the same error message. I had to manually rearrange the filters so the "Markdown Easy" filter is on top again with unsaved changes. Once I saved the changes I received no error messages.
The instructions were straightforward. I tested the module on a new drupal site and on Gitpod. No issues updating the site.
cindy_codediaries → created an issue.
cindy_codediaries → created an issue.
cindy_codediaries → created an issue.
Chris McGrath → credited cindy_codediaries → .
rkoller → credited cindy_codediaries → .
I created Issue fork views_slideshow-3347039 to update the page https://www.drupal.org/project/views_slideshow → . However I am unsure as to which file should be updated. Would you kindly assist me on this?
cindy_codediaries → made their first commit to this issue’s fork.
cindy_codediaries → made their first commit to this issue’s fork.
Chris McGrath → credited cindy_codediaries → .
hotwebmatter → credited cindy_codediaries → .