User Contributed Forum still listed in Core Section

Created on 22 June 2024, 6 months ago
Updated 24 June 2024, 6 months ago

Problem/Motivation

Just updated from Drupal 10.2.7 to Drupal 10.3.0 via composer, and then updated the Forum module to the user Contributed module version 1.0.1. The user contributed Forum module version 1.0.1, was successfully installed, and is listed under the contributed modules section in the Drupal file structure (/modules/contrib). However the module continues to be listed under the core section in the admin/modules "list" tab. Under the core section, Forum, listing specifics, it is now listed as version 1.0.1, not the core version.

To ensure that the user contributed version was the "active" version, under the core modules files directory (core/modules/forum), I renamed the core directory to forum-bak (core/modules/forum-bak). I purged caches, restarted my server, and logged in/out/in drupal. The Forum version 1.0.1 version is the active version, not the 10.3.0 core version.

Steps to reproduce

Proposed resolution

Propose that this module be listed in its own user contributed area, as all other user contributed modules are.

Remaining tasks

I have also installed Drupal 11.0.0beta from the Drupal 10.3.0 version noted above (on separate server), and the user contributed forum module remains listed in the core section of Drupal 11.0.0beta, even though there is no longer a core module in Drupal 11.0.0beta. Screenshots of the Status of Drupal 10.3.0/11.0.0beta show the system in working order, and a screen shot of the user contributed forums section is also included.

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Closed: duplicate

Version

1.0

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States lee56

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

Comments & Activities

  • Issue created by @lee56
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Yep we probably just need to update the package in the info file
    Do you want to open a merge request? Thanks!

  • πŸ‡ΊπŸ‡ΈUnited States lee56

    Thanks for replying to issue. As a fairly new admin for drupal, I am not familiar with the drupal merge request process, or how to proceed. I pretty much know the basics of the drupal module file structure and how to report bugs, but have no drupal/PHP coding experience. I also am not familiar with git/github, which I believe is the repository for drupal development, including merging code. If there is some way to assist, I am willing to learn/help, but will likely be more of obstacle at this time.

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    This is a great first issue then!
    Above there should be a button 'create issue fork', first step is to click on that.
    I'm happy to guide you from there.

  • πŸ‡ΊπŸ‡ΈUnited States lee56

    Thanks for your patience. I did click on 'create the issue fork', which then informed me that I have push access.

    Issue fork forum-3456433 βœ“ You have push access

    In the show commands area, I see 2 options, one SSL, one non SSL:
    Since I know I have not set up SSL for this, I believe the second option would apply to me:

    Or, if you do not have SSH keys set up on git.drupalcode.org:
    git remote add forum-3456433 https://git.drupalcode.org/issue/forum-3456433.git
    git fetch forum-3456433

    I did just install git on my Linux server. The git version listed is 2.45.2

    Have stopped at this point.

  • Status changed to Closed: duplicate 6 months ago
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Gah, sorry for the noise here - it looks like we already fixed this in πŸ“Œ Change package from Core to Forum Fixed

    For what it's worth, I was going to guide you through the process, here's those steps below - this would have been a great first issue because it doesn't need any local setup!

    So by clicking that button, you now have a copy of the forum code base just for this issue.

    The next steps would have been:

    Click on the branch name "3456433-user-contributed-forum" in this box

    Then you would end up at the version of the codebase for this issue - https://git.drupalcode.org/issue/forum-3456433/-/tree/3456433-user-contr...

    If you weren't logged in, you would click the Sign in link in the top right corner

    Once you're logged in, you might get sent to the homepage of gitlab, if so, you would navigate back to https://git.drupalcode.org/issue/forum-3456433/-/tree/3456433-user-contr...

    You would have needed to edit the info file, so you would have scrolled down till you found it

    Then when you click on it and you would see its contents

    Then you could have clicked edit, and edited it in the browser - we'd use 'edit single file'

    You could have changed the package to 'Forum' (as it already is now from the linked issue above), saved the changes and opened a merge request.

    Once again, sorry for not picking up we'd already done this.

  • πŸ‡ΊπŸ‡ΈUnited States lee56

    That is quite ok. I learned much about this process by your instructions. I am just glad that the issue is being resolved. It appears that the forum.info.yml file is where the info needed to be revised. I look forward to the revision, and seeing the forum listed out of the core area.

    It has been a steep learning curve for me, learning the basics of Drupal a few years ago with no admin or php experience. In 2022 I volunteered to rescue an old Drupal 6 site built in 2008 that was no longer operative. I am retired, and figured I had the time to learn the admin portion. The Drupal 6 site was brought back online and then converted to Drupal 9, and then updated to Drupal 10.

    I hope to take a breath and learn more about the coding at some point in the near future. I was going to purchase a book on Drupal development back in 2022, but the books on the market were covering Drupal 6-7 and the short lived Drupal 8. Drupal finally seems to have stabilized since Drupal 10, so perhaps now is the time to find a good book to learn some of the finer points. Thanks again for your help.

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    No worries!

    You may already be aware, but if not, I'd recommend joining slack, and saying hi to the community - drupal.org/slack has instructions.

    I have been doing Drupal for 16 years but the first couple of years I struggled on my own without realising there was an amazing community.

    There's lots of regional and subject specific channels and plenty of friendly folks.

  • πŸ‡ΊπŸ‡ΈUnited States lee56

    Thanks, I will definitely give it a look. Thanks for recommendation.

Production build 0.71.5 2024