Before the module creates a watchdog record with: "Changed a permanently moved link" I get 8 PHP warnings, the first is: Undefined property: stdClass::$uid in node_save().

Comments

PROMES created an issue. See original summary.

akkina’s picture

akkina commented

I had the same problem.
I think the value of Impersonate user account in /admin/config/content/linkchecker might be invalid.

promes’s picture

promes
Primary language Dutch
commented

@akkina: you are right. I had to change my username. And since the username is stored in variable 'linkchecker_impersonate_user' the variable has a wrong value.
I presume storing the userid is a better solution. And adding a warning when the variable 'linkchecker_impersonate_user' is out of date.

hass’s picture

hass commented
Title: Undefined property: stdClass::$uid » Disallow deleting the auto corrlinkchecker user
Version: 7.x-1.3 » 7.x-1.x-dev
Category: Bug report » Feature request

Well I never expected this and there is no validation that prevents you from deleting the user. We should add a drupal_set_message() to the used users page and also alter the users form and disable the delete button. Otherwise we could try to find a way to add a validation function to the users page that prevent people from deleting it and tell the user why this user cannot deleted.

hass’s picture

hass commented
Title: Disallow deleting the auto corrlinkchecker user » Disallow deleting impersonate user account
promes’s picture

promes
Primary language Dutch
commented

I didn't delete the user, but only changed the name which resulted in warnings for working with an anonymous user account.
So the primary action should be to use the userid or check for a namechange of the user.
I my opinion mostly a (super-)admin account is used in the settings. And those are not often deleted.

promes’s picture

promes
Primary language Dutch
commented

Abetter idea could be always use userid 1.

hass’s picture

hass commented

In past it was possible to delete user 1, too.

promes’s picture

promes
Primary language Dutch
commented

But deletion of userid 1 is less frequent then renaming the username. Remenber: I did start my issue with a codebreak after renaming my username and not with deleting a user!.
I rename my usernames mostly when I change passwords and when I see in the logging that my chosen name (or more or less equal) has been used by one of the many bots en people trying to open up a site by the daily attempt of guessing of usernames and passwords.
I never expected that a module was using the username to get programmatically access to my account.
But it is your choise how to program the module.

hass’s picture

hass commented

That is strange and need some investigation as I thought the field only contain an integer (user id).

quadrexdev’s picture

quadrexdev
Location Lutsk
commented
Status: Active » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.