Contrib.social

Error on Views updates might be related to Profile module

Open on Drupal.org →
Created on 24 December 2023, 12 months ago
Updated 7 January 2024, 12 months ago

First, I have actually uninstalled the Profile module only because I ended up not needing it. I have posted this same question in the Drupal Core Issues as well. I'm using D10, and after running my usual updates using Composer, I started getting this error that I can't fix:

 --------- -------------------- ------------- ---------------------------------
  Module    Update ID            Type          Description
 --------- -------------------- ------------- ---------------------------------
  views     remove_default_arg   post-update   Remove
            ument_skip_url                     default_argument_skip_url
                                               setting.
  views     remove_skip_cache_   post-update   Remove the skip_cache settings.
            setting
  views     taxonomy_filter_us   post-update   Removes User context from views
            er_context                         with taxonomy filters.
  webform   authenticated_user   post-update   Issue #3404493: webform_default
            _permission                        permission.
 --------- -------------------- ------------- ---------------------------------


 Do you wish to run the specified pending updates? (yes/no) [yes]:
 > y

>  [notice] Update started: views_post_update_remove_default_argument_skip_url
>  [error]  The "profile_owner" plugin does not exist. Valid plugin IDs for Drupal\views\Plugin\ViewsPluginManager are: entity_browser_widget_context, node, taxonomy_tid, user, current_user, raw, query_parameter, fixed
>  [error]  Update failed: views_post_update_remove_default_argument_skip_url
 [error]  Update aborted by: views_post_update_remove_default_argument_skip_url
 [error]  Finished performing updates.

I have tried rerunning Update several times, and clearing all the caches, but I can't get past that error.
I don't know if it's connected or not, but I also can't run the cron from the status page anymore without it crashing.
Is this related to something the Profile module left behind? Why would it show up now after all this time? And sorry for posting the same question here if it really isn't related to the Profile module.

💬 Support request
Status

Fixed

Version

1.0

Component

Code

Created by

🇺🇸United States wxman

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

Comments & Activities

  • Issue created by @wxman
  • Comment 12 months ago →
    🇺🇸United States wxman

    I found DB entries:

    1 match in cache_config 	Browse 	Delete 		
2 matches in cache_data 	Browse 	Delete		
1 match in config 	Browse 	Delete
1 match in config_export 	Browse 	Delete
1 match in config_import 	Browse 	Delete
1 match in config_snapshot 	Browse 	Delete

    A search of the site found:

    views.view.user_pages.yml:          default_argument_type: profile_owner
views.view.user_pages.yml:          default_argument_type: profile_owner
views.view.user_pages.yml:          default_argument_type: profile_owner

    I think I fixed it. I manually deleted the DB entries that were showing, and removed the file in the /web/sites/default/files/config directory. I reran the updates, and the database updated normally. My manual cron still seems to be not working, but I'll put up with that for now. I still don't know how those entries could have been left over after all this time.

  • Status changed to Fixed 12 months ago
  • Comment 12 months ago →
    🇺🇸United States wxman
  • Comment 12 months ago →
    System Message

    Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024