Change dokan file location

[Aunshon]

All Submissions:

• My code follow the WordPress' coding standards
• My code satisfies feature requirements
• My code is tested
• My code passes the PHPCS tests
• 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)

• Full PR Link

Closes

• Closes #

How to test the changes in this Pull Request:

• Steps or issue 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

  • Updated to version 3.12.6, enhancing overall performance and stability.

• Bug Fixes

  • Improved file reference consistency across various methods for better functionality.

[coderabbitai]

Walkthrough

The pull request introduces several updates to the WeDevs_Dokan class in dokan-class.php. Key changes include updating the version property from '3.11.3' to '3.12.6' and modifying various methods to utilize DOKAN_FILE instead of __FILE__ for file path references. This adjustment affects methods such as plugin_path(), localization_setup(), define_constants(), declare_woocommerce_feature_compatibility(), and init_hooks(), ensuring consistent file reference usage throughout the class.

Changes

File	Change Summary
dokan-class.php	Updated version from '3.11.3' to '3.12.6'. Modified plugin_path(), localization_setup(), define_constants(), declare_woocommerce_feature_compatibility(), and init_hooks() methods to use DOKAN_FILE instead of __FILE__.

Possibly related PRs

• [fix] Dokan localize_data not found #2409: Modifies localization logic in the Assets class, related to the changes in the localization_setup() method.
• enhance: Hide revenue coupon info from woocommerce analytics report. #2418: Involves changes in the Assets class regarding script management, relevant to the same file as the main PR.
• Fix/revenue reports #2423: Updates in the QueryFilter class for analytics reports, potentially connecting to the overall functionality of the Dokan plugin.

Suggested labels

QA approved, :+1: Dev Review Done

Suggested reviewers

• mrabbani
• shohag121

🐇 In the code where paths align,
A version change, oh how divine!
With DOKAN_FILE, we find our way,
Clarity shines, come what may.
So hop along, let’s celebrate,
Updates here, oh isn’t it great! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c6dcc61 and a2d41f1.

📒 Files selected for processing (1)

• dokan-class.php (6 hunks)

🔇 Additional comments (6)

dokan-class.php (6)

205-205: LGTM! Consistent with file path standardization.

The change from __FILE__ to DOKAN_FILE in the localization setup is consistent with the standardization effort.

---

218-218: LGTM! Consistent with file path standardization.

The change from __FILE__ to DOKAN_FILE in the constant definition is consistent with the standardization effort.

---

234-235: LGTM! Proper class existence check and consistent file path usage.

The changes to use DOKAN_FILE in WooCommerce feature compatibility declarations are consistent and include proper class existence checks.

---

136-136: Verify DOKAN_FILE constant definition.

The change from __FILE__ to DOKAN_FILE looks good, but we should ensure that DOKAN_FILE is properly defined before usage.

#!/bin/bash
# Check for DOKAN_FILE constant definition
echo "Checking for DOKAN_FILE constant definition..."
rg "define.*DOKAN_FILE" -B 2 -A 2

---

266-266: LGTM! Verify all file references are updated.

The change from __FILE__ to DOKAN_FILE in the plugin action links filter is consistent. Let's verify that all file references have been updated throughout the codebase.

#!/bin/bash
# Check for any remaining __FILE__ references that might need updating
echo "Checking for remaining __FILE__ references..."
rg "__FILE__" --type php

---

26-26: Verify version bump and changelog entries.

The version has been updated from '3.11.3' to '3.12.6', which spans multiple minor releases. Please ensure that:

1. All changes between versions are properly documented in the changelog
2. The version bump follows the release process

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.