🇭🇷Croatia @MilosR

@Anybody

Because of that, I disabled that option by default. If someone needs to delete logs for deleted entities, then they have options to do that.

I've created logic where 100 logs are loaded on cron. It checks if entities exist, and if they don't, it deletes the log. Deletion is disabled by default, but can be enabled in settings.

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

Hi, I added a new field called 'bundle,' which contains the entity type. Now, it can be filtered in the view by this 'bundle' field. This way, all fields under one entity type will be obtained together.

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

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

Hi @levmyshkin

The Entity log is used for tracking field changes on entities.

It's not used for deleting, so it seems like your custom integration for logging entity deletions caused an issue.

I tried the case you described, but I did not encounter any issues because the module does not log any deletions.

Hi @mdolnik,

This doesn't seem like a bug to me, it looks more like a custom solution you want to implement on your project.

I'm not clear on why you're calling the setEntityLoggedId() method. As you mentioned, if you want to modify logged values, you can extend the EntityLogService class and customize the logFields() method to suit your needs.

I can confirm that I was able to reproduce the issue on Drupal 9 as reported. Upon the first page refresh, there are no flags, but when navigating to another page, AJAX is used and everything works.

After updating to Drupal Core 10, it no longer works, not even with AJAX - nothing appears at all.

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

Hi @roman_pro

This is something that needs to be custom-made for a specific case, it's not something that should be done at the module level.

MilosR → changed the visibility of the branch 3137304-error-when-faceting to active.

MilosR → changed the visibility of the branch 3137304-error-when-faceting to hidden.

I am currently experiencing this issue on Drupal core 10.2.5 and Stage File Proxy Version 2.1.4.

@Asterovim

Hi, you can, for example, add a "changed" field in the view.

@thechanceg

Yes, it is possible, you just need to add field under General. Add the flag you need, and then in the view, add an indexed field like "User flag (indexed field)" as necessary. Additionally, you may need to add a User relationship in the view, depending on what is required.

@jukka792

Can you provide steps to reproduce this issue?

@Youcanlearnit

You're not right. Flags related to users can be indexed.

@jukka792

Can you check when hovering over the flag link if there's something like this in the link: "/typeerror-null-given"?

Thanks @BenStallings

In my case, I had a problem with facets in my custom code, which was called like this:

$request->query->get('f')

So, I changed it to this, and it works:

$request->query->all('f')

MilosR → created an issue.

@larowlan which part of the code?

MilosR → created an issue.

The flags created and used with the flag_search_api module do not have labels. In this case, the 'List item label' should not exist in the form. The fix is to uncheck the 'List item label,' and here is the patch that removes the 'List item label' checkbox for all flags that do not have that functionality. Therefore, in future cases, there will not be any options to check 'List item label'.

Hi, @jukka792, I just tested this case in a fresh new installation of Drupal Core (version 9.5.11), and indexing works as expected in both cases, whether an action is flagged or unflagged. I do not see that the issue you mentioned is caused by this module. Could you please investigate further on a fresh Drupal installation and provide more data?

The patch are not applying on the latest version of the module, we need to work on this.

#91 Patch file does not apply to the latest version.