$form['feeds_log'] not showing in Feeds feed form

Created on 29 July 2024, 4 months ago
Updated 2 August 2024, 4 months ago

Problem/Motivation

In Gin Admin theme, $form['feeds_log'] not showing when create a feed entity.
Default value return 0 therefore no Feeds Log record was added to the database.

Steps to reproduce

  1. Create a Feed Type
  2. Enable Logging
  3. Make sure Log field appear in form display setting
  4. Create a feed with feed type has just created. the form is like this:
  5. Expectation: form should have the "log" field. Actual: no field named "log" or id "feeds_log"

Proposed resolution

Remove $form['feeds_log']['#group'] = 'options';

User interface changes

Result:

🐛 Bug report
Status

Closed: works as designed

Version

3.0

Component

Code

Created by

🇻🇳Vietnam mrddthi

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

Merge Requests

Comments & Activities

  • Issue created by @mrddthi
  • Pipeline finished with Success
    4 months ago
    Total: 535s
    #237813
  • Status changed to Postponed: needs info 4 months ago
  • 🇳🇱Netherlands megachriz

    I don't quite understand what is exactly wrong. There's something that you don't see, but it's not quite clear what. Is it the log entries? Is it the config option on the feed form?

    Can you show screenshots from before your code changes and after?

    Can you also share your feed type configuration? On the feed type configuration you can disable logs and then the option for enabling logs on a feed does not appear.

  • 🇻🇳Vietnam mrddthi

    Hi @megachriz, I've updated the issue summary following your recommendation.
    Thanks for checking.

  • 🇳🇱Netherlands megachriz

    Apparently, there's more missing on your feed form, like "Authored by" and "Authored on". Are you logged in as a user with limited privileges? If so, what permissions does this user have?

    This is how it looks like for me, as a user with all permissions:

  • 🇻🇳Vietnam mrddthi

    Hi @megachriz,
    Sorry for taking up so much of your time. It's my bad when checking the issue not clearly.
    It's caused from another module which move the $form[...]['#group'] = 'options' to another place.
    I'll closed the ticket now.

  • Status changed to Closed: won't fix 4 months ago
  • Status changed to Closed: works as designed 4 months ago
  • 🇳🇱Netherlands megachriz

    Thanks for reporting back!

    I hadn't put a lot of time into this issue yet. I was planning to try to reproduce the issue with limited permissions, but I thought I ask first if you were using that.

Production build 0.71.5 2024