Fix user settings update failure via buttons

[botmaker00]

The user reported that setting values like thumbnail, caption, prefix, etc., via buttons was not working. This was likely due to silent failures in the event handler filter or input processing.

The fix involves:

1. Modifying event_filter in bot/modules/users_settings.py to robustly check for the existence of the user object before accessing its ID. This prevents potential AttributeError crashes if the update lacks user information.
2. Updating set_custom to explicitly check if message.text exists and strip it. This handles cases where message.text might be None (e.g., media messages) or contain unintentional whitespace.

These changes ensure that the handler correctly captures the user's input and updates the settings as expected.

---

PR created automatically by Jules for task 17556196815641779005 started by @botmaker00

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[Copilot]

Pull request overview

This PR fixes user settings update failures when setting values (thumbnail, caption, prefix, etc.) via button interactions. The changes add defensive checks to prevent AttributeErrors when processing user input.

Changes:

• Added None check and whitespace stripping in set_custom function to handle edge cases where message.text might be None or contain unintentional whitespace
• Added user existence check in event_filter to prevent AttributeError when accessing user.id

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The None check is incomplete. If message.text is None:

1. The condition if value: evaluates to False, so value remains None
2. Subsequent operations will fail: line 341 (is_goapi(value)), line 349 (value.split()), line 368 (value.split()), and line 385 (value.encode()) will all raise AttributeError when value is None

While the event_filter at line 458 should prevent None text from reaching this function (since mtype = event.text and the filter requires mtype to be truthy), defensive programming would make this more robust.

Consider: value = (message.text or "").strip() to ensure value is always a string.

Suggested change

	value = message.text
	if value:
	value = value.strip()
	value = (message.text or "").strip()