ccrim

Thanks, good to hear!

Well, after looking around for a bit for another plugin just for this part of my data migration, I gave up and was thinking about importing the user_id into the unused comment_karma field and programmatically moving it over where it belongs. But happily I was able to modify your plugin code to include the user_id in the comment import mapping. So, thank you!

I still suggest that it would be nice to include the user_id in the comment import but perhaps you were concerned about somebody making a mess of things with user ids. Anyway, thanks again. This really is a great import/export plugin!

Thinking about it more… or you could add support for all three common line breaks: CR, LF, or CRLF

I never heard back from our email exchange but I spent some more time on this and eventually figured out that the problem was the line breaks (CR vs LF) in my files exported from another program. Converting them to LF did the trick and let this plugin proceed with the import.

I would like to suggest an error message on the initial import file screen would be helpful. It scanned the file and gave no error message.

Thanks for a great plugin though!

Thanks for identifying the errors and locations. Was able to quickly fix the offending lines until these guys update their plugin.

Well, alright, I narrowed it down to a conflict with another plugin: “Spam Destroyer”

https://www.ads-software.com/plugins/spam-destroyer/

Activating/deactivating this plugin causes/fixes the JSON.parse error with “Comments – WpDiscuz” when submitting a new comment.

PHP version is 5.5.38. No Hosting Service name as this is my own server (crimdom.net). Deactivate all plugins and install again? Even though it was previously working? Alright, trying that temporarily now…..

I just tried commenting via FireFox and I see the following error: “SyntaxError: JSON.parse: unexpected character at line 2 column 3 of the JSON data”

Notably, there is a very thin pink error bar after trying to submit a comment via Safari but there’s no error message visible.

I’m experiencing the same issue on my own server. (crimdom.net)
I do not have WP Rocket.

Tried deleting and reinstalling wpdiscuz and problem of “endless progress bar” returned immediately. Also encountered errors during attempt to reinstall (“server not responsive”). I’ve now deactivated wpdiscuz.

Thanks for taking the request. Regarding the css, that diagram seems to confirm what I was asking: the text and background color css for the *edit* boxes (like “Join this discussion”) is not configurable in the settings screen. I presume then it is coming from somewhere else then, like my installed theme? If so, I would want to introduce a different css style here for the edit boxes to match the light text and dark background colors I’ve chosen for the rest of the comments elements.