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
Finalize StCR → Comment Mail Migration Process #80
Comments
@websharks/comment-mail-team Completing work on this GitHub Issue will depend on the completion of GitHub Issues #44 and #1 (stripping the Lite version from the Pro version, so that the Lite version can be used for testing here). What's important is that we don't start thoroughly testing the StCR → Comment Mail migration process until we're getting closed to a release-version of Comment Mail Lite, otherwise we'll end up doing lots of testing now, and then have to re-do all that testing again later when Comment Mail is closer to release. We need to make sure that the migration process is fully tested using the version of Comment Mail that new users are going to see. There are also few things that I'm sure about, as I haven't been following @jaswsinc's Comment Mail work that closely. If the following work hasn't been done, we'll need to open separate GitHub issues for each of these so that we can complete this work:
|
@raamdev I would also like to add an additional point. I guess Comment Mail has the migration process for an old version of StCR.
|
@Reedyseth That's a great point. I forgot to mention that. StCR has changed a bit since the StCR import routines in Comment Mail were written, so we'll need to do a full review of this again once we have a Lite version of Comment Mail we can start testing with. I'm going to update the checklist above to mention this. |
Referencing a dump of StCR options:
|
@jaswsinc Great, if you have any question with an option I would be happy to clarify it ! |
@raamdev Thanks ! |
Just to bring a point that I mention before. The first time that I run the importation routing the number of subscriptions did not match, so after we have the lite version ready to test I will take this task to confirm it. |
Referencing StCR transitioning helper. Needs review: |
@jaswsinc Cool, I am on it, no need to wait for the Striping ! |
Great! Just let me know if you have any trouble or find a bug. Thank you :-) |
Awesome! Thanks @Reedyseth |
@Reedyseth Feel free to submit a pull request for any changes/improvements you'd like to make there. |
Adding the following todo item to the checklist above ↑:
|
@jaswsinc RIght now I have a clone of the repo, what would be better, create a branch and from that branch submit the pull request or fork the repo ? |
You can use the clone and create a new branch called |
👍 |
Cool, Thank you ! |
No warning, but if you attempt it again it simply returns
Yes, you can always visit the Import tab, and, in addition to that notice, there is also a blinking navigation item when you visit the options page, reminding you to complete the StCR data import in case you somehow miss it. |
I read over the changelog for StCR. Has anything changed in the storage of subscribers and/or their status flags? |
I don't believe so, no, but I would want Israel to confirm that, as he's worked on the past few StCR releases. |
Nope, the flags remain the same, no changes on that part. Something that was added is a new table to store the subscribers email addresses and a unique key for that email. This is due to the security issue by google, they call it PII, but it will not affect the subscribers information on the |
Copy that. I remember you mentioning this before. So the unique key is what's being stored in the database then, not the actual subscriptions. Is that right? Sorry, just making sure I understand :-) |
Correct, what it store is the email and the unique key. This does not affect the subscriptions statuses only interact with the subscriptions forms to allow them to manage the subscription. |
Added two new GitHub issues to the todo list above related to finalizing the StCR Migration process. ↑ |
Completed the checklist at the top of this issue. Closing (finally!). 😀 |
👍 Yay! |
- **Bug Fix**: Fixed a bug where the "My Comment Subscriptions" link would appear on the Add New Subscription page (when Subscribing without Commenting) and would lead to a page that displayed an error message stating that there were no subscriptions to list. That link is now hidden when there are no subscriptions to list. Props @Reedyseth @kristineds. See [Issue #229](#229). - **Bug Fix** (Pro): Removed an erroneous anchor tag in the Advanced Template for Comment Notification Message Body. Props @kristineds. See [Issue #287](#287). - **UI Enhancement:** Improved the nav bar at the top of the options pages to reduce unnecessary whitespace. Also moved the Restore button to the nav bar so that it's not so prominent. Props @renzms. See [Issue #284](#284). - **UI Enhancement:** Added links to the Comment Mail [Twitter](http://twitter.com/CommentMail) and [Facebook](https://www.facebook.com/Comment-Mail-565683256946855/) pages to the nav bar on the options page. Props @renzms. See [Issue #286](#286). - **UX Enhancement:** Removed IP address information from email notification templates to better comply with data protection laws in certain countries. Props @kristineds. See [Issue #288](#288). - **SEO Improvement:** Added `rel="nofollow"` to the "Subscribe without Commenting" link and "Manage Subscriptions" link on the comment subscription form to avoid indexing or transferring PageRank. Props @IvanRF. See [Issue #80](wpsharks/comment-mail-pro#80). - Removed several development-only files from the distributable that were inadvertently included during the build process. See [Issue #285](#285). - Added Renz Sevilla (`renzms`) to the contributors list.
This GitHub Issue will be used to track any final work necessary to finalize the StCR → Comment Mail migration process. The following tasks need to be completed (this checklist will be updated if more work is discovered to be necessary):
Issues to Close
The text was updated successfully, but these errors were encountered: