Download the PHP package elshaden/popup-card without Composer

Laravel Nova Popup Card

A customizable popup modal card for Laravel Nova that automatically displays to users when they access your dashboard or resource pages. Perfect for welcome messages, announcements, notifications, and more.

🌟 Features

• Automatic Display: Shows popup cards to users when they access specified pages
• User Tracking: Remembers which users have seen which popups
• Do Not Show Again: Users can opt out of seeing specific popups again
• Customizable Content: Full HTML support for rich content in popups
• Configurable Width: Choose from multiple width options (1/4, 1/3, 1/2, 2/3, 3/4, full)
• Targeted Display: Show different popups on different pages or to specific users
• Admin Interface: Manage all your popup cards through a Nova resource
• Database Storage: All popup cards and user interactions are stored in the database
• Configurable Tables: Customize database table names to fit your application

Example

Here's an example of how a welcome popup from ACME Company might look:

Note: Create this image based on the specifications in docs/images/sample-popup-instructions.md

Compatibility

• Laravel Nova 4.x and 5.x
• PHP > = 8.0 up To 8.4
• Laravel >=9.x up to 12.x

Installation

You can install the package in Laravel Nova app that uses Nova via composer:

Package Registration

The package will be automatically registered using Laravel's package auto-discovery. However, if you have disabled auto-discovery, you need to manually register the package's service provider in your config/app.php file:

Configuration

You can publish the config file with:

Database Table Configuration

The package allows you to customize the database table names and foreign keys used by the popup card system. This is useful if you need to avoid table name conflicts or follow specific naming conventions in your application.

Available configuration options:

Example: Customizing Table Names

If you want to use custom table names, you can modify these values in your published configuration file:

After changing these values, make sure to run the migrations to create the tables with your custom names.

Configuration Content

Migrations

You can publish the migration with:

After publishing the migration, you can create the necessary database tables by running the migrations:

This will create two tables:

• popup_cards: Stores all your popup cards with their content and settings
• cards_users: Pivot table that tracks which users have seen which popup cards

Usage

Basic Setup

1. Add the Trait to Your User Model

You MUST add the HasPopupCards trait to your user model. This enables tracking which users have seen which popups:

2. Register the Resource in Nova's Menu

Add the PopupCard resource to your Nova menu to manage popup cards:

Adding Popup Cards to Pages

You can add popup cards to your dashboard or any resource page. The popup will automatically display when users visit that page.

Important: The name you use in the ->name() method must match the name of an existing popup card in your database. You need to create the popup card first using the Nova admin panel before you can display it in your code.

Dashboard Example

In this example, a popup card with the name "welcome-message" must already exist in your database.

Resource Example

Similarly, a popup card with the name "user-instructions" must already exist in your database.

Customizing Display Conditions

You can control who sees the popup using Nova's canSee() method:

In this example, a popup card with the name "2fa-reminder" must already exist in your database. This popup would only be shown to users who don't have two-factor authentication enabled.

Width Options

You can customize the width of your popup card using one of these options:

• '1/4' - 25% of screen width
• '1/3' - 33% of screen width
• '1/2' - 50% of screen width
• '2/3' - 66% of screen width
• '3/4' - 75% of screen width
• 'full' - 100% of screen width

How It Works: Complete Workflow

Here's a step-by-step explanation of how the popup card system works:

1. Create a Popup Card in Nova Admin Panel

   • Navigate to the PopupCard resource in your Nova admin panel
   • Click "Create Popup Card"
   • Fill in the required fields:
     • Name: A unique identifier (e.g., "2fa-reminder") - this is crucial!
     • Title: The title displayed at the top of the popup
     • Body: The content of the popup (supports HTML)
   • Set "Published" and "Active" to true

   • Save the popup card

     2. Reference the Popup Card in Your Code
        • In your dashboard or resource file, add the PopupCard to the cards method
        • Use the exact same name you specified in the admin panel:
        • Optionally add conditions using canSee() to control who sees the popup
2. User Experience
   • When a user visits the page, the system checks if there's an active popup card with the specified name
   • If found and the user hasn't seen it before, the popup is displayed
   • The user can close the popup or choose not to see it again

This name-based reference system allows you to create different popup cards for different parts of your application and control them centrally through the Nova admin panel.

Managing Popup Cards

Using the PopupCard resource in Nova, you can:

• Create new popup cards with custom titles and content
• Edit existing popup cards
• Publish or unpublish popup cards
• View which users have seen each popup

Creating Popup Cards

When creating a popup card in the Nova admin panel

1. The name field must be unique for each popup card
2. This name is used to reference the popup card in your code via the ->name() method
3. The popup card must be created in the admin panel before it can be displayed in your code

User Interaction

The system will automatically show the latest active and published popup card to users when they access the page where the popup is configured. Users can:

• Close the popup card
• Choose to not see the popup again by checking the "Do Not Show Again" option

Testing

This package includes a comprehensive test suite. To run the tests:

1. Install development dependencies:

2. Run the tests:

Available Test Suites

• Unit Tests: Test individual components in isolation

• Feature Tests: Test API endpoints and integration

Test Coverage

Generate a test coverage report:

For more detailed information about testing, including how to run tests from a project that has installed this package (using either PHPUnit or Pest PHP), refer to the README-testing.md file.

If you encounter any issues while using this package, please check the README-troubleshooting.md file for common solutions.

License

The MIT License (MIT). Please see License File for more information.

Credits

• Elshaden - Package Creator and Maintainer

Contributing

Please feel free to fork this package and contribute by submitting a pull request to enhance the functionalities. See CONTRIBUTING.md for detailed guidelines on how to contribute.

Security

If you discover any security related issues, please email [email protected] instead of using the issue tracker. All security vulnerabilities will be promptly addressed.

Support

Thank you for using this package! If you encounter any issues or have questions:

1. Check the README-troubleshooting.md file for common solutions
2. Search the issue tracker to see if your issue has already been reported
3. Open a new issue with a clear description and reproduction steps if needed