enhance: Implement vendor default banner, profile image & controls.

MdAsifHossainNadim commented 1 month ago

All Submissions:

[x] My code follow the WordPress' coding standards
[x] My code satisfies feature requirements
[x] My code is tested
[x] My code passes the PHPCS tests
[x] My code has proper inline documentation
[ ] I've included related pull request(s) (optional)
[ ] I've included developer documentation (optional)
[ ] I've added proper labels to this pull request

Changes proposed in this Pull Request:

Related Pull Request(s)

Implement vendor default banner, profile image & controls.

Closes

Closes #2944

How to test the changes in this Pull Request:

Video Guidance: Link

Changelog entry

Title

Detailed Description of the pull request. What was previous behaviour and what will be changed in this PR.

Before Changes

Describe the issue before changes with screenshots(s).

After Changes

Describe the issue after changes with screenshot(s).

Feature Video (optional)

Link of detailed video if this PR is for a feature.

PR Self Review Checklist:

Code is not following code style guidelines
Bad naming: make sure you would understand your code if you read it a few months from now.
KISS: Keep it simple, Sweetie (not stupid!).
DRY: Don't Repeat Yourself.
Code that is not readable: too many nested 'if's are a bad sign.
Performance issues
Complicated constructions that need refactoring or comments: code should almost always be self-explanatory.
Grammar errors.

FOR PR REVIEWER ONLY:

As a reviewer, your feedback should be focused on the idea, not the person. Seek to understand, be respectful, and focus on constructive dialog.

As a contributor, your responsibility is to learn from suggestions and iterate your pull request should it be needed based on feedback. Seek to collaborate and produce the best possible contribution to the greater whole.

[ ] Correct — Does the change do what it’s supposed to? ie: code 100% fulfilling the requirements?
[ ] Secure — Would a nefarious party find some way to exploit this change? ie: everything is sanitized/escaped appropriately for any SQL or XSS injection possibilities?
[ ] Readable — Will your future self be able to understand this change months down the road?
[ ] Elegant — Does the change fit aesthetically within the overall style and architecture?

Summary by CodeRabbit

New Features
- Introduced settings for default store banner and profile picture with specific dimensions and default images in the admin settings.
- Added conditional rendering for resetting images to default state with a user confirmation dialog.
Bug Fixes
- Improved consistency and clarity in variable naming for user-related data in the Dashboard.
Enhancements
- Enhanced methods for retrieving store banners and avatars in the Vendor module with default image handling and customization options.
- Improved user interface for uploading and cropping images in the admin panel.
Style
- Updated styles for image elements to ensure proper display and alignment.

MdAsifHossainNadim commented 1 month ago

@tuhin480 Vhai, Kindly review this video & let us inform that, the banner image and profile icon should be okay or not... Link

MdAsifHossainNadim commented 1 month ago

@tuhin480 Vhai, I think we need to improve ui in dokan pro's vendor edit page.

ashrafux commented 1 month ago

@tuhin480 Vhai, Kindly review this video & let us inform that, the banner image and profile icon should be okay or not... Link

@MdAsifHossainNadim Vai, We created this design in the cloud, so we should implement it in the plugin as well.

Design link: https://www.figma.com/design/dRiVZXj2FZAY8P5myZcuHG/Storefront-Theme-Design?node-id=1443%3A12282&t=UTR3WCSQ7FSeA1bf-1

Plugin cover image size: https://www.figma.com/design/dRiVZXj2FZAY8P5myZcuHG/Storefront-Theme-Design?node-id=3034%3A15952&t=UTR3WCSQ7FSeA1bf-1

coderabbitai[bot] commented 1 month ago

Walkthrough

The recent update focuses on enhancing store visuals by refining default image management, introducing new methods for retrieving default images, and improving customization options. These changes aim to provide a more user-friendly experience in managing store banners and avatars, ensuring a visually appealing and streamlined interface for users.

Changes

File Path	Change Summary
`assets/src/less/store.less`	Removed specific `background-image` property from a class affecting element styling.
`includes/Admin/Settings.php`	Updated `get_settings_fields` to include store banner dimensions and default image settings.
`includes/Dashboard/Templates/Settings.php`	Renamed variable for clarity in `load_store_content` method, ensuring consistent naming conventions.
`includes/Vendor/Vendor.php`	Enhanced methods for retrieving store banners and avatars, added logic for default images and filter overrides.
`src/admin/components/FieldHeading.vue`	Introduced conditional rendering and added method for resetting to default state with a confirmation dialog.
`src/admin/components/Fields.vue`	Added functionality for handling `croppable_image` fields, including image upload and cropping features.
`src/admin/components/UploadImage.vue`	Added styling to ensure images occupy 100% width for better display.
`templates/settings/store-form.php`	Updated logic for displaying banner and gravatar images in store settings form.
`templates/store-header.php`	Introduced variable for fetching and displaying store banner URL.
`templates/store-lists-loop.php`	Updated handling and display of default store banner based on image presence.

🐰 In the code where banners fly, Defaults set for every eye. Avatars and settings neat, Making stores a visual treat. With each change, we celebrate, A better store, a brighter fate. 🌟

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

getdokan / dokan