Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/ update the get support link to correct contact page #2559

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

TanvirHasan19
Copy link
Member

@TanvirHasan19 TanvirHasan19 commented Feb 6, 2025

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

How to test the changes in this Pull Request:

  • Steps or issue link

Changelog entry

- **fix:** update the get support link to correct contact page

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

  • Documentation
    • Updated support, getting started, and feature request links in the admin panel to direct users to the latest resources on the official website.

Copy link
Contributor

coderabbitai bot commented Feb 6, 2025

Walkthrough

This pull request modifies the admin header template by updating the URLs for various support resources. The "Get Support" link now points to https://dokan.co/contact/, the "Getting Started" link to https://dokan.co/docs/wordpress/getting-started/, and the "Feature Requests" link to https://dokan.co/wordpress/feature-requests/. No public entity declarations were altered.

Changes

File Change Summary
templates/admin-header.php Updated "Get Support", "Getting Started", and "Feature Requests" links to point to the Dokan website URLs.

Assessment against linked issues

Objective Addressed Explanation
Update the 'Get Support' link to direct users to https://dokan.co/contact/ (#2433)

Possibly related PRs

Suggested labels

QA approved, :+1: Dev Review Done, Upcoming Release

Suggested reviewers

  • mrabbani

Poem

Hopping through the code at night,
I change the links to shine so bright.
From support to docs, each URL in sight,
A rabbit’s tweak in the admin light,
Celebrating fresh paths with pure delight! 🐇

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e743934 and f204920.

📒 Files selected for processing (1)
  • templates/admin-header.php (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: e2e tests (3, 3)
  • GitHub Check: e2e tests (2, 3)
  • GitHub Check: e2e tests (1, 3)
  • GitHub Check: api tests (1, 1)
🔇 Additional comments (4)
templates/admin-header.php (4)

91-91: LGTM! Support link updated correctly.

The "Get Support" link has been updated to point to the correct contact page at dokan.co.


112-112: LGTM! Documentation link updated correctly.

The "Documentation" link has been updated to point to the getting started guide at dokan.co.


137-137: LGTM! Feature requests link updated correctly.

The "Feature Requests" link has been updated to point to the feature requests page at dokan.co.


91-137: Verify the new domain is ready to handle traffic.

All links have been updated from wedevs.com to dokan.co. Please ensure:

  1. The new domain is properly set up and ready to handle user traffic
  2. Proper redirects are in place from the old URLs to prevent broken links
  3. The new URLs are accessible and returning the correct content
✅ Verification successful

🌐 Web query:

Is dokan.co the official website for the Dokan plugin?

💡 Result:

Yes, **dokan.co** is the official website for the Dokan Multivendor Marketplace plugin[1][3][4][10]. This domain serves as the primary hub for accessing essential resources related to Dokan:

- **Plugin Downloads**: Users download both free (Dokan Lite) and premium versions directly from dokan.co[10].
- **Documentation**: Detailed technical guides like configuration tutorials are hosted here[4].
- **Support**: Official customer service policies specify that premium users must contact support through this domain[3].
- **Product Information**: Features lists, success stories, pricing details, and mobile app integrations are all published on this platform[1][5][7].

The website is operated by weDevs[8], Dokan's developer, which confirms its authenticity. Third-party platforms like WordPress.org also direct users to dokan.co for demos and premium features[2][7][9].

Citations:

- 1: https://dokan.co/wordpress/dokan-mobile-app/
- 2: https://tr.wordpress.org/plugins/dokan-lite/
- 3: https://dokan.co/support-policy/
- 4: https://dokan.co/docs/wordpress/getting-started/basic-configuration/
- 5: https://dokan.co/wordpress/features/
- 6: https://xtemos.com/forums/topic/dokan-integration-2/
- 7: https://wordpress.org/plugins/dokan-lite/
- 8: https://wedevs.com
- 9: https://wordpress.org/support/topic/dokan-multivendor-plugin-2/
- 10: https://dokan.co/wordpress/download/

Domain Update Verified

The web query confirms that dokan.co is indeed the official website for the Dokan plugin. The links in the file have been updated accordingly.

• The domain is properly recognized as official, indicating it’s set up to serve essential resources.
• Ensure proper redirects from any previous wedevs.com URLs are configured (this may require a separate infrastructure check).
• Verify that the new URLs are accessible and return the correct content in your staging/production environment.


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
🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

@TanvirHasan19 TanvirHasan19 added Needs: Testing This requires further testing Needs: Dev Review It requires a developer review and approval labels Feb 6, 2025
@@ -109,7 +109,7 @@
</div>
<?php esc_html_e( 'Community', 'dokan-lite' ); ?>
</a>
<a href="https://wedevs.com/docs/dokan/getting-started/?utm_source=plugin&utm_medium=wp-admin&utm_campaign=dokan-lite" target="_blank">
<a href="https://dokan.co/docs/wordpress/getting-started/" target="_blank">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@getdokan/product-plugin-team, Should we add utm?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mrabbani vai,
Yes kindly do so as previous link was already associated with utm source so in this change we should do similar as that. Kindly proceed vai

@mrabbani mrabbani added PM Dependency and removed Needs: Dev Review It requires a developer review and approval labels Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Testing This requires further testing PM Dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update the 'Get Support' Link to Correct Contact Page
3 participants