Hello @gretchen,
Do you know if your current Database User has Insert Privileges ?, Also if you purchase the plugin you can open a ticket on comment mail:
https://www.websharks-inc.com/support/?product=comment-mail
Regards.!!
@gretchenlouise Can you tell us which version Comment Mail you’re using and which version Subscribe to Comments Reloaded you have installed? I’d like to run a few tests against both of those versions to see if there might be a bug in the importer.
@raam, I’m using Comment Mail Version 160213 and Subscribe to Comments Reloaded Version 150611. The latest version of STCR breaks the site, so I had to download a previous version, per another support thread I saw.
@reedyseth, I don’t know that, unfortunately. But I would assume so, as it’s an Admin WP user. I’ll do some digging.
@gretchenlouise Do you have anything inside wp-content/plugins/comment-mail/stcr-import-failures.log?
@raam, yes, actually, I do. It’s a lot of lines with entries like these (I removed email addresses). Is it possible that it has all already beeen imported? How can I tell?
Skipping this subscription
note: A Replies Only (R) subscription already exists for this Post ID; see http://bit.ly/1RqXCyD
email:
status: R
post_id: 5
Failed to import Replies Only (R) subscription
note: Associated comment has been deleted, trashed, or marked as spam
post_id: 10
email:
Failed to import Replies Only (R) subscription
note: Associated comment has been deleted, trashed, or marked as spam
post_id: 11
@gretchenlouise Well, it’s possible subscriptions have been imported (if so, they should show up in Dashboard → Comment Mail → Subscriptions). However, the “Insert/replace failure.” error is a bit worrying and would indicate to me that even if subscriptions were imported, they might not have all been imported.
My first thought when I saw those errors and heard this was related to an StCR import from an older version of StCR, which you downgraded to because of having issues with a newer version of StCR, was that the Comment Mail import failure could be related to a corruption of your StCR database in some way. If that’s the case, fixing this isn’t going to be easy.
Do you have a large number of StCR subscriptions or would you be able to cross-reference the StCR subscriptions list with the subscriptions imported by Comment Mail (if any)?
There are 696 subscriptions in STCR. But none of them show in Comment Mail. And they all originally came from Comment Reply Notification. I was using STCR to get them from Comment Reply to Comment Mail… So right now, there are zero in Comment Mail. We can stick with STCR but it just is scary that we can’t update the plugin without the whole site going down due to a STCR error.
We can stick with STCR but it just is scary that we can’t update the plugin without the whole site going down due to a STCR error.
@gretchenlouise
That error that you describe is because of your PHP version is lower thatn 5.4.x
@raamdev
Her error could be issues with PHP version as well ?
You know what, I realized that I hadn’t tried updating Subscribe to Comments Reloaded since we had taken care of our PHP version. So, I updated STCR and it’s all working fine. However, the Comment Mail import still gives me the same failure notices.
I can just leave STCR for now unless I can help troubleshoot the Insert/replace failure.
Thank you!
@gretchenlouise I’m glad to hear you got StCR working again. 🙂
The only thing I can suggest trying for Comment Mail is to deactivate the plugin deletion safeguards in Comment Mail → Config. Options → Data Safeguards, and then deactivate and delete the plugin (that will wipe away any Comment Mail configuration, including from the database). Then you could try reinstalling Comment Mail and running the import again.
If you still receive errors, then the only other thing that would help us would be a copy of your StCR database, so that we can run an import in our development environment and attempt to debug the issue from there. If you’d like to help us with that, please email me privately at raam at websharks-inc dot com. If not, no worries at all. 🙂
Deleting the plugin and all its options and reinstalling worked perfectly. Thank you!
@gretchenlouise Awesome! That’s great to hear. 🙂
