docs: rename plugin to comply with WordPress.org#57
Merged
Conversation
Rename the plugin from "IpQuery" to "Stracini Visitor Analytics with IpQuery" following trademark compliance requirements from the WordPress.org Plugin Review Team. The plugin needed a clear distinction as a third-party integration with IpQuery. - Updated plugin name in README.md and documentation files. - Adjusted dashboard and settings navigation labels for clearer identification. - Added a notice in the README.md explaining the renaming and mentioning the unchanged internal components like class names and database tables.
Reviewer's GuideRenames the WordPress plugin to "Stracini Visitor Analytics with IpQuery" for WordPress.org trademark compliance and updates user-facing labels and documentation while leaving internal identifiers unchanged. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
gstraccini
Bot
added
the
☑️ auto-merge
|
Warning Review limit reached
Your plan currently allows 1 review/hour. Refill in 6 minutes and 59 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (18)
WalkthroughThis PR updates all public-facing documentation and branding to reflect the plugin's WordPress.org-compliant directory name "Stracini Visitor Analytics with IpQuery" while preserving all internal code identifiers. Navigation paths are consistently redirected from "IpQuery" menu entries to "Visitor Analytics" throughout user-facing documentation. ChangesDocumentation Branding and Navigation Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![gstraccini[bot]](https://avatars.githubusercontent.com/in/480132?s=60&v=4){kind=small}
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- The docs now refer to the plugin by both the full name (“Stracini Visitor Analytics with IpQuery”) and the shorter admin menu label (“Visitor Analytics”); it may be worth explicitly clarifying this distinction once (e.g., in README or docs/index.md) so users understand why the plugin name and sidebar label don’t exactly match.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The docs now refer to the plugin by both the full name (“Stracini Visitor Analytics with IpQuery”) and the shorter admin menu label (“Visitor Analytics”); it may be worth explicitly clarifying this distinction once (e.g., in README or docs/index.md) so users understand why the plugin name and sidebar label don’t exactly match.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Contributor
🔍 WordPress Plugin Check Report
📊 Report
|
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
0 |
readme_parser_warnings_trimmed_short_description | The "Short Description" section is too long and was truncated. A maximum of 150 characters is supported. |
📁 includes/class-sva-db.php (1 warning)
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
399 |
PluginCheck.Security.DirectDB.UnescapedDBParameter | Unescaped parameter $sql used in $wpdb->get_results()\n$sql assigned unsafely at line 394. |
🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check
Update the 'Tested up to' WordPress version to 7.0 to reflect compatibility with the latest release. Bump the stable tag from 1.2.0 to 1.3.0 to denote that the plugin has been updated and tested with the new WordPress version. These changes ensure users are informed about the plugin's current compatibility and stability status.
docs: update plugin name and data storage details Update the plugin name from "IpQuery" to "Stracini Visitor Analytics with IpQuery" for consistency with branding. Modify the description to include the full plugin name instead of just "IpQuery". Change the database storage table reference from `wp_ipquery_visitors` to `wp_stracini_visitor_analytics_visitors` to reflect the updated plugin name. These changes improve the clarity and coherence of the documentation.
Rename all class, file, and variable references from IpQuery to SVA to better reflect the Stracini Visitor Analytics branding. This includes renaming database tables, AJAX actions, and other identifiers. These changes ensure consistent naming following the rebranding, and maintain compatibility across references in code and configurations.
Refactor code to transition from 'IpQuery' branding to 'SVA' (Stracini Visitor Analytics). Update file names, variables, CSS selectors, HTML classes, and function names throughout the codebase. This change aligns the code with the plugin's new name and branding, providing a consistent experience for users and improving maintainability.
Revert stable version tag in `readme.txt` from 1.3.0 to 1.2.0 to match the current plugin version. Correct the spelling of "analyze" in both `readme.txt` and `stracini-visitor-analytics.php` for consistency with American English. These changes ensure clarity and consistency across documentation and versioning.
Update phpcs.xml to reflect the renaming of the plugin from IpQuery to Stracini Visitor Analytics with IpQuery. Change the ruleset name, description, main file reference, and text domain to align with the new plugin identity. These changes ensure consistency across the configuration following the plugin's rebranding.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📑 Description
Rename the plugin from "IpQuery" to "Stracini Visitor Analytics with IpQuery" following trademark compliance requirements from the WordPress.org Plugin Review Team. The plugin needed a clear distinction as a third-party integration with IpQuery.
✅ Checks
☢️ Does this introduce a breaking change?
Summary by Sourcery
Rename the WordPress plugin and documentation to use the new "Stracini Visitor Analytics with IpQuery" branding for WordPress.org compliance.
Documentation:
Summary by CodeRabbit