upgrade url update

[myself-alif]

Summary by CodeRabbit

• New Features
  • Updated the upgrade button link to direct users to a specific pricing page with enhanced tracking parameters for improved marketing analytics.

[coderabbitai]

Walkthrough

The destination URL for the upgrade button in the ProPreviews component was updated to direct users to a specific pricing page with UTM parameters for marketing tracking. No other code, logic, or styling changes were made.

Changes

Cohort / File(s)	Change Summary
Upgrade Button URL Update src/components/ProPreviews/common/UpgradeButton.js	Changed the anchor tag's href from the homepage to a pricing page URL with UTM parameters for tracking purposes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A button once led to the home,
Now pricing is where users will roam.
With UTM tags in the string,
Marketing insights this link will bring.
Hop, hop, hooray for this tiny tweak,
Analytics bunnies will take a peek! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch upgrade-url-update

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7d2fc7e and d653e09.

📒 Files selected for processing (1)

• src/components/ProPreviews/common/UpgradeButton.js (1 hunks)

[coderabbitai]

⚠️ Potential issue

Add https:// scheme and rel="noopener noreferrer" to harden the link

1. A protocol-relative URL (//...) can unexpectedly fall back to http on non-TLS pages, exposing users to MITM risks.
2. Opening a new tab with target="_blank" without rel="noopener noreferrer" leaves the app vulnerable to reverse-tabnabbing.

-          target='_blank'
-          href='//wedocs.co/pricing/?utm_source=wordpress-dashboard+&utm_medium=update_to_pro_pop-up&utm_campaign=free2pro_pop-up'
+          target='_blank'
+          rel='noopener noreferrer'
+          href='https://wedocs.co/pricing/?utm_source=wordpress-dashboard&utm_medium=update_to_pro_pop-up&utm_campaign=free2pro_pop-up'

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	target='_blank'
	href='//wedocs.co/'
	href='//wedocs.co/pricing/?utm_source=wordpress-dashboard+&utm_medium=update_to_pro_pop-up&utm_campaign=free2pro_pop-up'
	onClick={ showPopup }
	target='_blank'
	rel='noopener noreferrer'
	href='https://wedocs.co/pricing/?utm_source=wordpress-dashboard&utm_medium=update_to_pro_pop-up&utm_campaign=free2pro_pop-up'
	onClick={ showPopup }

🧰 Tools

🪛 Biome (2.1.2)

[error] 10-10: Avoid using target="_blank" without rel="noopener" or rel="noreferrer".

Opening external links in new tabs without rel="noopener" is a security risk. See the explanation for more details.
Safe fix: Add the rel="noopener" attribute.

(lint/security/noBlankTarget)

🤖 Prompt for AI Agents

In src/components/ProPreviews/common/UpgradeButton.js around lines 10 to 12, the
href attribute uses a protocol-relative URL which can default to http and cause
security risks; update the href to include the full 'https://' scheme. Also, add
rel="noopener noreferrer" to the anchor tag to prevent reverse-tabnabbing
vulnerabilities when using target="_blank".