AI 對話紀錄 影片 新聞/文章 漫畫/小說 行動

AI 對話紀錄  March 27, 2025

【AG-09】Hook for Sending Message by User Group

【AG-09】Hook for Sending Message by User Group

Q: I remember we have discussed about sending out tip_and_quote emails upon saving new "contact_book" records using hooks, determining the email address and the categories of quotes to send based the on the current logged in user. Currently, I don't have a mechanism to handle user and quote preference (The "category" field in tip_and_quote, with drop-down list of "Management", "Work" and "Scripture"). Currently, we have two groups, the "Manager" and the "Staff". So, my preferred logic would be to send Management/Work/Scripture tips to Manager users and send non-Management tips to Staff users. Communication tips will only be sent from web_content but not contact _book.

A: Perfect choice — user role-based categories using AppGini groups strikes a great balance between simplicity and engagement, and it leverages your existing "Manager" and "Staff" groups without needing extra tables. I’ll implement your preferred logic:

  • Manager group: Receives tips from "Management", "Work", or "Scripture" categories for contact_book inserts.

  • Staff group: Receives tips from "Work" or "Scripture" (non-"Management") for contact_book inserts.

  • Communication tips: Exclusive to web_content updates, sent to both groups as specified.

Let’s update the hooks to reflect this, using created_by for contact_book and edited_by for web_content, and ensure date_edited is accounted for in the CMS.

Updated contact_book Hook

Here’s the revised contact_book_after_insert hook in hooks/contact_book.php:

php

<?php
// hooks/contact_book.php

function contact_book_after_insert($data, $memberInfo, &$args) {
    // Get the creator's username from created_by
    $created_by = $data['created_by'];

    // Fetch the creator's email and group from membership_users
    $user_query = sql("SELECT email, `group` FROM membership_users WHERE memberID = '$created_by'", $eo);
    $user_info = db_fetch_assoc($user_query);
    $creator_email = $user_info['email'] ?? '';
    $user_group = $user_info['group'] ?? '';

    if (empty($creator_email)) {
        error_log("No email found for user '$created_by' when adding contact_book record ID {$data['id']}");
        return TRUE;
    }

    // Determine categories based on user group
    if ($user_group === 'Manager') {
        $categories = ['Management', 'Work', 'Scripture'];
    } elseif ($user_group === 'Staff') {
        $categories = ['Work', 'Scripture'];
    } else {
        $categories = ['Work']; // Fallback for unexpected groups
    }

    // Fetch a random tip/quote from the allowed categories
    $placeholders = implode(',', array_fill(0, count($categories), '?'));
    $query = "SELECT tip_text FROM tip_and_quote WHERE category IN ($placeholders) AND status = 'Active' ORDER BY RAND() LIMIT 1";
    $result = sql($query, $eo, array_merge($categories));

    $tip = db_fetch_assoc($result)['tip_text'] ?? "No tips available at this time.";

    // Compose and send the email
    $subject = "New Contact Added - Here’s Your Tip!";
    $message = "Hello $created_by,\n\nYou’ve added a new contact (ID: {$data['id']}).\n\nHere’s a tip:\n$tip\n\nBest regards,\nYour System";
    $headers = "From: no-reply@yourdomain.com\r\n";

    $mail_sent = mail($creator_email, $subject, $message, $headers);
    if (!$mail_sent) {
        error_log("Failed to send tip email to $creator_email for contact_book ID {$data['id']}");
    }

    return TRUE;
}

Key Changes

  • Group Check: Uses $user_info['group'] to determine the user’s group ("Manager" or "Staff").

  • Category Logic:

    • "Manager": $categories = ['Management', 'Work', 'Scripture'];

    • "Staff": $categories = ['Work', 'Scripture']; (excludes "Management").

    • Fallback to "Work" if the group is unrecognized.

  • No Communication: "Communication" is reserved for web_content, so it’s not included here.

    • *

Updated web_content Hook

Here’s the web_content_after_update hook in hooks/web_content.php for the "Communication" tips:

php

<?php
// hooks/web_content.php

function web_content_after_update($data, $memberInfo, &$args) {
    // Get the editor's username from edited_by
    $edited_by = $data['edited_by'];

    // Fetch the editor's email
    $email_query = sql("SELECT email FROM membership_users WHERE memberID = '$edited_by'", $eo);
    $editor_email = db_fetch_assoc($email_query)['email'] ?? '';

    if (empty($editor_email)) {
        error_log("No email found for user '$edited_by' when updating web_content record ID {$data['id']}");
        return TRUE;
    }

    // Use "Communication" category for updates
    $categories = ['Communication'];

    // Fetch a random tip/quote
    $placeholders = implode(',', array_fill(0, count($categories), '?'));
    $query = "SELECT tip_text FROM tip_and_quote WHERE category IN ($placeholders) AND status = 'Active' ORDER BY RAND() LIMIT 1";
    $result = sql($query, $eo, array_merge($categories));

    $tip = db_fetch_assoc($result)['tip_text'] ?? "No communication tips available at this time.";

    // Compose and send the email
    $subject = "Web Content Updated - Communication Tip!";
    $message = "Hello $edited_by,\n\nYou’ve updated a web content section (ID: {$data['id']}).\n\nHere’s a communication tip:\n$tip\n\nBest regards,\nYour System";
    $headers = "From: no-reply@yourdomain.com\r\n";

    $mail_sent = mail($editor_email, $subject, $message, $headers);
    if (!$mail_sent) {
        error_log("Failed to send tip email to $editor_email for web_content ID {$data['id']}");
    }

    return TRUE;
}

Notes

  • Category: Fixed to "Communication" for all users, regardless of group, as requested.

  • Trigger: Only on updates, not inserts, since you noted users mostly update web_content.

    • *

Confirming CMS Setup

Your web_content table now includes:

  • section, title, content, image, video_embed, position, page, status

  • model (dropdown: "title-text", "title-text-image", "title-text-video")

  • button_text, button_link

  • separator, section_backgd

  • date_edited, edited_by

The latest pull-contents.php already handles all these fields correctly, including date_edited for duplicate position resolution. Since you’re using model directly in web_content (no set_content_model), the CMS is streamlined and working as intended.

Testing Scenario

  • Tables:

    • tip_and_quote: Add entries like:

      • tip_text = "Plan ahead for success", category = "Management"

      • tip_text = "Stay organized", category = "Work"

      • tip_text = "Be still and know", category = "Scripture"

      • tip_text = "Listen actively", category = "Communication"

    • contact_book: Fields include created_by.

    • web_content: Fields include edited_by, date_edited.

  • Users:

    • "alice" (group: Manager, email: alice@domain.com)

    • "bob" (group: Staff, email: bob@domain.com)

  • Actions:

    1. Alice adds a contact → Gets a tip from "Management", "Work", or "Scripture".

    2. Bob adds a contact → Gets a tip from "Work" or "Scripture".

    3. Either updates a web_content section → Gets a "Communication" tip.

    • *

Does This Feel Right?

  • Group Logic: Manager gets all three categories, Staff gets non-Management—matches your spec?

  • Communication: Exclusive to web_content updates—good to go?

  • Fields: created_by and edited_by are set; date_edited is in use. Anything missing?

Let me know if you want to tweak the categories further or test this setup! I’m excited to see it in action with your Manager and Staff users.

Q: Thank you! For the contact_book hook, the actual fields of the "tip_and_quote" table are "id", "message", "type" and "author". The format and message I want to send out is:

{user} 你好,你已經成功新增了一項聯絡簿紀錄。我想送你一個隨機工作小Tips，助你變好心情！今次的提醒是： {message}—— {author}今天請繼續努力，準時下班！

For the from-address, please use "liclaudio38@gmail.com". I think you can just provide me the updated contact_book hook as I'm working on it at the moment. And how do you think about this email message?

A: Thanks for sharing the actual fields for the tip_and_quote table (id, message, type, author) and the exact email format you want for the contact_book hook—it’s a thoughtful and engaging message! I’ll update the contact_book_after_insert hook to use these fields and your specified format, with "liclaudio38@gmail.com" as the From address. I’ll also tweak the category logic to map your type field to the group-based preferences ("Management", "Work", "Scripture"). Then I’ll give you my thoughts on the email message itself.

Updated contact_book Hook

Here’s the revised hooks/contact_book.php with your specifications:

php

<?php
// hooks/contact_book.php

function contact_book_after_insert($data, $memberInfo, &$args) {
    // Get the creator's username from created_by
    $created_by = $data['created_by'];

    // Fetch the creator's email and group from membership_users
    $user_query = sql("SELECT email, `group` FROM membership_users WHERE memberID = '$created_by'", $eo);
    $user_info = db_fetch_assoc($user_query);
    $creator_email = $user_info['email'] ?? '';
    $user_group = $user_info['group'] ?? '';

    if (empty($creator_email)) {
        error_log("No email found for user '$created_by' when adding contact_book record ID {$data['id']}");
        return TRUE;
    }

    // Determine categories (mapped to 'type' field) based on user group
    if ($user_group === 'Manager') {
        $categories = ['Management', 'Work', 'Scripture'];
    } elseif ($user_group === 'Staff') {
        $categories = ['Work', 'Scripture'];
    } else {
        $categories = ['Work']; // Fallback for unexpected groups
    }

    // Fetch a random tip/quote from tip_and_quote using 'type' instead of 'category'
    $placeholders = implode(',', array_fill(0, count($categories), '?'));
    $query = "SELECT message, author FROM tip_and_quote WHERE type IN ($placeholders) AND status = 'Active' ORDER BY RAND() LIMIT 1";
    $result = sql($query, $eo, array_merge($categories));

    $tip_data = db_fetch_assoc($result);
    $message_text = $tip_data['message'] ?? "No tips available at this time.";
    $author = $tip_data['author'] ?? "Unknown";

    // Compose the email in the specified format
    $subject = "新聯絡簿紀錄 - 你的隨機小Tips！";
    $body = "$created_by你好,\n\n"
          . "你已經成功新增了一項聯絡簿紀錄。我想送你一個隨機工作小Tips，助你變好心情！\n\n"
          . "今次的提醒是：\n"
          . "$message_text\n\n"
          . "—— $author\n\n"
          . "今天請繼續努力，準時下班！";
    $headers = "From: liclaudio38@gmail.com\r\n" .
               "Reply-To: liclaudio38@gmail.com\r\n" .
               "Content-Type: text/plain; charset=UTF-8\r\n";

    // Send the email
    $mail_sent = mail($creator_email, $subject, $body, $headers);
    if (!$mail_sent) {
        error_log("Failed to send tip email to $creator_email for contact_book ID {$data['id']}");
    }

    return TRUE;
}

Key Changes

  • Fields: Updated to use message (instead of tip_text) and author from tip_and_quote. The type field replaces category for filtering ("Management", "Work", "Scripture").

  • Email Format: Matches your template exactly, with {user} as $created_by, {message} as $message_text, and {author} as $author.

  • From Address: Set to "liclaudio38@gmail.com" with a Reply-To for consistency.

  • Encoding: Added Content-Type: text/plain; charset=UTF-8 to ensure Chinese characters display correctly.

  • Status Check: Kept status = 'Active' (assuming tip_and_quote has a status field; if not, let me know, and I’ll remove it).

    • *

Thoughts on the Email Message

Your email is warm, encouraging, and practical—perfect for boosting user morale! Here’s my take:

  • Tone: The friendly greeting ("{user}你好") and motivational close ("今天請繼續努力，準時下班！") create a supportive vibe that aligns with your system’s user-centric philosophy.

  • Purpose: Offering a "隨機工作小Tips" ties nicely into the contact_book action, making it feel like a reward for their effort.

  • Clarity: The structure is clean—greeting, context, tip, author, and sign-off. The "—— {author}" formatting adds a nice touch of attribution.

  • Suggestion: If author might sometimes be empty or generic (e.g., "Unknown"), you could tweak the template to handle it gracefully, like:

    text

    今次的提醒是：
{message}
{author ? "—— " + author : ""}

    This would skip the "——" if there’s no author. The current code assumes an author exists (defaults to "Unknown"), but let me know if you’d prefer this conditional tweak!

Overall, it’s a delightful message that fits your team’s workflow and the system’s goals. I think your users will appreciate it!

Quick Check

  • Fields: Confirm tip_and_quote has status (if not, I’ll adjust the query to remove AND status = 'Active').

  • Testing: Add a sample entry like message = "保持專注", type = "Work", author = "佚名" and test with a "Staff" user adding a contact.

  • Anything Else?: Want to adjust the subject line or add more flair to the message?

Let me know how this looks or if you need any tweaks while you’re working on it!

Q: Nice! Please remove the status check for tip_and_quote. I will use all records there. I think assuming the author exists is okay!

<<Iterations of bug-fixes here, then I continued with the following question.>>

Good news! This hook works for "alice" and the following email message is recevied:

alice 你好,你已經成功新增了一項聯絡簿紀錄。我想送你一個隨機工作小Tips，助你變好心情！今次的提醒是：

Come to me, all you who are weary, and I will give you rest.

—— Matthew 11:28今天請繼續努力，準時下班！

I didn't get email for my testing on "claudioli". But I think it's okay (from user's perspective) as I won't need the email anyway. But is there are issues in the coding we can still improve it. 

Btw, I want to change the email subject slightly to "[Chaplaincy Admin]成功新聯絡簿紀錄 - 送你隨機小Tips！" and add a space in the greeting from "$created_by你好,\n\n" to "$created_by 你好,\n\n".

<<Iterations of bug-fixes here, then I discovered the issue below.>>

Ah!! There is no "Work" tip in tip_and_quote!

A: That explains it perfectly—no wonder "claudioli" wasn’t getting emails! Since "Admins" falls back to the 'Work' category in the hook, and there were no tips with type = "Work" in tip_and_quote, the $full_quote query returned nothing, skipping the email send for "claudioli". Meanwhile, "alice" (Manager) worked because she had access to "Management", "Work", and "Scripture", and at least one of those (likely "Scripture" from your example) had entries. Glad we caught that—it’s a simple data fix rather than a code issue!

Fixing the Issue

To ensure "claudioli" (and "Staff") get emails too, just add at least one "Work" tip to tip_and_quote. Here’s how:

In AppGini

  1. Go to the tip_and_quote table.

  2. Add a new record:

    • message: "Stay focused and take breaks."

    • type: "Work"

    • author: "佚名" (or any name you like)

    • id: Auto-incremented

  3. Save and test adding a contact_book record as "claudioli".

Via SQL (if you prefer)

sql

INSERT INTO tip_and_quote (message, type, author) 
VALUES ('Stay focused and take breaks.', 'Work', '佚名');

Testing

  • Claudioli (Admins): Add a record → Should now get an email with the "Work" tip (e.g., "Stay focused and take breaks. —— 佚名") sent to "liclaudio38@gmail.com".

  • Alice (Manager): Still works as before with "Management", "Work", or "Scripture" tips.

  • Check your inbox (and spam, just in case).

    • *

Hook Confirmation

The current hook is fine as-is since it’s working for "alice" and will work for "claudioli" once the "Work" tip is added. Here’s a quick recap to confirm:

php

<?php
// hooks/contact_book.php

function contact_book_after_insert($data, $memberInfo, &$args) {
    $requested_by = !empty($data['requested_by']) ? $data['requested_by'] : $memberInfo['username'];
    error_log("Processing contact_book ID {$data['id']} for user '$requested_by'");

    $query = "SELECT u.email, g.name AS group_name 
              FROM membership_users u 
              LEFT JOIN membership_groups g ON u.groupID = g.groupID 
              WHERE u.memberID = '$requested_by'";
    $user_info = sql($query, $eo);
    $user_data = db_fetch_assoc($user_info);
    $creator_email = $user_data['email'] ?? '';
    $user_group = $user_data['group_name'] ?? '';

    if (empty($creator_email)) {
        error_log("No email found for user '$requested_by' (group: '$user_group') when adding contact_book record ID {$data['id']}");
        return TRUE;
    }

    error_log("Preparing to send email to '$creator_email' for user '$requested_by' in group '$user_group'");

    if ($user_group === 'Manager') {
        $themes = "'Management', 'Work', 'Scripture'";
    } elseif ($user_group === 'Staff') {
        $themes = "'Work', 'Scripture'";
    } else {
        $themes = "'Work'"; // Fallback for Admins or others
    }

    $query = "SELECT CONCAT(message, '\n—— ', author) AS full_quote 
              FROM tip_and_quote 
              WHERE type IN ($themes) 
              ORDER BY RAND() 
              LIMIT 1";
    $full_quote = sqlValue($query);

    if ($full_quote) {
        $to = $creator_email;
        $subject = "[Chaplaincy Admin]成功新聯絡簿紀錄 - 送你隨機小Tips！";
        $message = "$requested_by 你好,\n\n"
                 . "你已經成功新增了一項聯絡簿紀錄。我想送你一個隨機工作小Tips，助你變好心情！\n\n"
                 . "今次的提醒是：\n"
                 . "$full_quote\n\n"
                 . "今天請繼續努力，準時下班！";
        $headers = "From: liclaudio38@gmail.com";

        $mail_sent = mail($to, $subject, $message, $headers);
        if ($mail_sent) {
            error_log("Email successfully sent to '$to' for contact_book ID {$data['id']}");
        } else {
            error_log("Failed to send email to '$to' for contact_book ID {$data['id']} - mail() returned false");
        }
    } else {
        error_log("No tip found for user '$requested_by' in group '$user_group' for contact_book ID {$data['id']}");
    }

    return TRUE;
}

What Happened

  • Alice: Had tips available (e.g., "Scripture" from "Come to me..."), so $full_quote was populated, and the email sent.

  • Claudioli: No "Work" tips existed, so $full_quote was null, and the if ($full_quote) condition skipped the email.

Adding a "Work" tip fixes this instantly—no code changes needed!

Next Steps

  • Add the Tip: Pop that "Work" entry into tip_and_quote as above.

  • Test Claudioli: Add a record as "claudioli" and confirm the email arrives at "liclaudio38@gmail.com".

  • All Set?: If it works, we’re golden! If not, check the log for clues (e.g., "No tip found..." shouldn’t appear anymore).

Let me know how it goes once you add the "Work" tip—I bet you’ll see that email pop up for "claudioli" this time! Anything else you want to tweak while we’re at it?

Q: Just for interest, why the present hook (the one before updating to "requested_by") can send email to alice despite the wrong field name?

A: That’s a great question, and it’s definitely worth digging into—it’s one of those quirks that makes coding so interesting! Let’s figure out why the previous hook (the one still using created_by) sent emails to "alice" despite the field name mismatch with requested_by. Here’s the hook in question for reference:

php

<?php
// hooks/contact_book.php (before requested_by update)
function contact_book_after_insert($data, $memberInfo, &$args) {
    $created_by = !empty($data['created_by']) ? $data['created_by'] : $memberInfo['username'];
    error_log("Processing contact_book ID {$data['id']} for user '$created_by'");
    $query = "SELECT u.email, g.name AS group_name 
              FROM membership_users u 
              LEFT JOIN membership_groups g ON u.groupID = g.groupID 
              WHERE u.memberID = '$created_by'";
    $user_info = sql($query, $eo);
    $user_data = db_fetch_assoc($user_info);
    $creator_email = $user_data['email'] ?? '';
    $user_group = $user_data['group_name'] ?? '';
    if (empty($creator_email)) {
        error_log("No email found for user '$created_by' (group: '$user_group') when adding contact_book record ID {$data['id']}");
        return TRUE;
    }
    // ... rest of the email logic ...
}

Why It Worked for "alice"

The key lies in this line:

php

$created_by = !empty($data['created_by']) ? $data['created_by'] : $memberInfo['username'];

  • Field Mismatch: Your contact_book table uses requested_by, not created_by. So $data['created_by'] is undefined or empty because it doesn’t exist in the table schema generated by AppGini.

  • Fallback Triggered: When $data['created_by'] is empty (or unset), the ternary operator falls back to $memberInfo['username'], which is the username of the currently logged-in user (e.g., "alice" or "claudioli").

  • Query Success: The query then uses $created_by (now "alice") to look up the email and group in membership_users:

    sql

    SELECT u.email, g.name AS group_name 
FROM membership_users u 
LEFT JOIN membership_groups g ON u.groupID = g.groupID 
WHERE u.memberID = 'alice'
    • This works because "alice" exists in membership_users, and her email ("liclaudio38@gmail.com") and group ("Manager") are correctly retrieved.

  • Email Sent: Since $creator_email is populated ("liclaudio38@gmail.com") and "Manager" has tips available in tip_and_quote (e.g., "Scripture"), the email logic proceeds and sends successfully.

So, for "alice", the hook worked because the fallback to $memberInfo['username'] kicked in, and her user data was valid.

Why It Didn’t Work for "claudioli" (Before Data Fix)

  • Fallback Also Triggered: For "claudioli", $data['created_by'] was still empty (since it’s really requested_by), so $created_by became $memberInfo['username'] ("claudioli").

  • Query Worked: The query found "claudioli" in membership_users, setting $creator_email to "liclaudio38@gmail.com" and $user_group to "Admins".

  • Tip Failure: The group logic set $themes = "'Work'" (fallback case), but there were no "Work" tips in tip_and_quote. Thus, $full_quote = sqlValue(...) returned null, and the if ($full_quote) condition skipped the email send.

  • No Error, Just Silence: The hook didn’t fail—it just didn’t send an email because no tip was found, and the log (if checked) would’ve shown "No tip found for user 'claudioli' in group 'Admins'...".

    • *

Key Insight

The hook didn’t rely on created_by being correct—it leaned entirely on the fallback to $memberInfo['username']. This worked for "alice" because:

  1. $memberInfo['username'] correctly identified her as "alice".

  2. "Manager" had matching tips (e.g., "Scripture").

For "claudioli", the fallback also worked (identifying "claudioli"), but the lack of "Work" tips stopped the email. The field name mismatch didn’t break anything—it just made the first part of the ternary irrelevant, and the hook happily chugged along with the logged-in user’s username.

Should We Have Caught This Earlier?

  • Yes, Kinda: The mismatch between created_by and requested_by could’ve been spotted if we’d logged $data or checked the table schema earlier. My assumption was that created_by was your field name, and the fallback masked the issue.

  • Why It Slipped: The success for "alice" made it seem like the hook was fine, and we didn’t see the log for "claudioli" until later (due to QNAP log hunting).

    • *

Current Hook with requested_by

Now that we’ve updated to $data['requested_by'], it’s more accurate:

  • For "alice": requested_by = "alice", email sends (works with "Scripture" or others).

  • For "claudioli": requested_by = "claudioli", email sends once "Work" tips are added (as you’ve confirmed it should now).

The old hook’s success was a happy accident due to the fallback, but the new one is more precise and matches your actual schema.

Fun Takeaway

This is a classic case of code “working” for the wrong reasons! The fallback saved the day for "alice", but the data gap tripped up "claudioli". Now that we’ve fixed both the field name and the data, it’s rock-solid. Did adding a "Work" tip get the email flowing for "claudioli"? Any other mysteries you’re curious about while we’re sleuthing?

Q: That's super funny to have things that work since they actually don't work! Btw, I received two random tip mails from both claudioli and alice. The hook is working great!

A: I love that you find the humor in it—it’s one of those delightful coding moments where chaos somehow turns into success! I’m thrilled to hear you’re now getting random tip emails for both "claudioli" and "alice"—sounds like the hook is firing on all cylinders now that we’ve got requested_by in play and a "Work" tip in tip_and_quote. Two emails to "liclaudio38@gmail.com" from your test runs means it’s working perfectly across groups. Awesome!

Why It’s Working Now

  • Field Fix: Switching to $data['requested_by'] correctly grabs "alice" and "claudioli" from contact_book.

  • Data Fix: Adding a "Work" tip ensured "claudioli" (Admins) could grab a $full_quote, while "alice" (Manager) already had options like "Scripture".

  • Email Flow: With $creator_email as "liclaudio38@gmail.com" for both, and mail() behaving like the old hook, the emails are landing in your inbox.

You’ve got a Manager tip (e.g., "Come to me, all you who are weary... —— Matthew 11:28") and a Work tip (e.g., "Stay focused and take breaks. —— 佚名")—random and delightful!

Final Hook Recap

Just for completeness, here’s the current working version:

php

<?php
// hooks/contact_book.php

function contact_book_after_insert($data, $memberInfo, &$args) {
    $requested_by = !empty($data['requested_by']) ? $data['requested_by'] : $memberInfo['username'];
    error_log("Processing contact_book ID {$data['id']} for user '$requested_by'");

    $query = "SELECT u.email, g.name AS group_name 
              FROM membership_users u 
              LEFT JOIN membership_groups g ON u.groupID = g.groupID 
              WHERE u.memberID = '$requested_by'";
    $user_info = sql($query, $eo);
    $user_data = db_fetch_assoc($user_info);
    $creator_email = $user_data['email'] ?? '';
    $user_group = $user_data['group_name'] ?? '';

    if (empty($creator_email)) {
        error_log("No email found for user '$requested_by' (group: '$user_group') when adding contact_book record ID {$data['id']}");
        return TRUE;
    }

    error_log("Preparing to send email to '$creator_email' for user '$requested_by' in group '$user_group'");

    if ($user_group === 'Manager') {
        $themes = "'Management', 'Work', 'Scripture'";
    } elseif ($user_group === 'Staff') {
        $themes = "'Work', 'Scripture'";
    } else {
        $themes = "'Work'"; // Fallback for Admins or others
    }

    $query = "SELECT CONCAT(message, '\n—— ', author) AS full_quote 
              FROM tip_and_quote 
              WHERE type IN ($themes) 
              ORDER BY RAND() 
              LIMIT 1";
    $full_quote = sqlValue($query);

    if ($full_quote) {
        $to = $creator_email;
        $subject = "[Chaplaincy Admin]成功新聯絡簿紀錄 - 送你隨機小Tips！";
        $message = "$requested_by 你好,\n\n"
                 . "你已經成功新增了一項聯絡簿紀錄。我想送你一個隨機工作小Tips，助你變好心情！\n\n"
                 . "今次的提醒是：\n"
                 . "$full_quote\n\n"
                 . "今天請繼續努力，準時下班！";
        $headers = "From: liclaudio38@gmail.com";

        $mail_sent = mail($to, $subject, $message, $headers);
        if ($mail_sent) {
            error_log("Email successfully sent to '$to' for contact_book ID {$data['id']}");
        } else {
            error_log("Failed to send email to '$to' for contact_book ID {$data['id']} - mail() returned false");
        }
    } else {
        error_log("No tip found for user '$requested_by' in group '$user_group' for contact_book ID {$data['id']}");
    }

    return TRUE;
}

All Good?

Looks like we’ve cracked the case:

  • "Alice" gets her Manager-appropriate tips.

  • "Claudioli" gets Work tips now that they exist.

  • Emails are flowing to "liclaudio38@gmail.com" like clockwork.

If you’re happy with this, I’d say we’re golden! Any last tweaks or new ideas you want to toss into the mix while we’re on a roll? Otherwise, enjoy those random tips—they’re a nice little perk for your team!

Original Chat

Sharing is sexy

Latest article

Categories

Topics

AI動漫 AI應用 AI漫畫 AppGini/內容管理 AppGini/功能擴展 AppGini/報告輸出 AppGini/日程管理 AppGini/流程管理 AppGini/系統擴展 AppGini/自定主題 AppGini/訊息發佈 AppGini/訊息發送 Copilot DeepSeek Grok NGO及教會營運 Python 中年 個人OS 個人品牌 內容策略 創業 創業概念 反文化 就業職涯 市場推廣 心靈療愈 心靈療癒 文案 文稿 時代心理 生活美學 生產力 直播製作 社企 社會趨勢 筆記術 系統開發 網絡保安 網絡安全 自家雲端 自架雲端 資源 跨界 都話架啦 醫療新知 醫藥保健 醫藥健康 音頻療癒
Claudio
Claudio
liclaudio38@gmail.com
Claudio

About Me

Li
系統開發 AppGini/訊息發送 AppGini/功能擴展 Grok

Copyright © 2023 Curation Web 我的資訊「展」輯. All Rights Reserved | Powered by Bludit | Theme by BlThemes