[1.x] Personalized Content Dashboard

Created on 5 April 2024, 9 months ago
Updated 6 September 2024, 3 months ago

Offers a dashboard to facilitate access and management of different content according to roles. This dashboard is accessible through an item "My Dashboard" in the main administration menu.

Project link

https://www.drupal.org/project/content_dashboard

📌 Task
Status

Needs work

Component

module

Created by

🇨🇦Canada libeo

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @libeo
  • Status changed to Needs review 9 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    Thank you for applying!

    Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smother review.

    The important notes are the following.

    • If you have not done it yet, you should run phpcs --standard=Drupal,DrupalPractice on the project, which alone fixes most of what reviewers would report.
    • For the time this application is open, only your commits are allowed.
    • The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status won't be changed by this application and no other user will be able to opt projects into security advisory policy.
    • We only accept an application per user. If you change your mind about the project to use for this application, please update the issue summary to give the link to the correct project link and the issue title to contain that project name.

    To the reviewers

    Please read How to review security advisory coverage applications , What to cover in an application review , and Drupal.org security advisory coverage application workflow .
    Reviewers only describe what needs to be changed; they don't provide patches to fix what reported in a review.

    Remember to change status, since Active means the project is not yet ready for review. Needs review is the status used when the project is ready for review.

  • Status changed to Needs work 9 months ago
  • 🇮🇳India vishal.kadam Mumbai

    1. FILE: content_dashboard.libraries.yml

    version: VERSION

    That line is used only by Drupal core modules. Contributed modules should use a literal string that does not change with the Drupal core version a site is using.

    2. FILE: content_dashboard.info.yml

    version: '1.0'
    project: 'content_dashboard'
    datestamp: 1710274695

    Remove "version", "project" and "datestamp" from the info file, it will be added by drupal.org packaging automatically.

  • 🇮🇳India vishal.kadam Mumbai

    I am changing priority as per Issue priorities .

  • 🇮🇳India rushiraval

    This thread has been idle, in the needs work state with no activity for several months. Therefore, I am assuming that you are no longer pursuing this application. If you are no longer pursuing this application then I mark it as Closed (won't fix).

    If this is incorrect, and you are still pursuing this application, then please feel free to set the issue status to Needs work or Needs review, depending on the current status of your code.

Production build 0.71.5 2024