Following up my previous thread, our users are still experiencing some issues with the new system:
- Can't post/like/moderate anything at all on iphone 5
- Conflict with "scroll to id" plugin breaks page
- Front end moderation "Move comment" not working on ipad
- Random white space/hard returns on end of some comments
- Can't create <p> inside blockquotes - hard returns/new paragraphs in blockquotes opens/closes blockquote
- Some users can't like comments/are told they already liked it/that they are the author.
- embedded youtube videos in comments are not contained by comment box, go off the side in replies.
We recommended your "private window" advice for iPhone 5, it made no difference. We fixed the javascript error you pointed out, it made no difference.
Hi @kitk,
Please provide us some example URL to allow us to check all your issues.
Sorry, I assumed you would still have it from my previous thread about the update. It's off-guardian.org.
This restriction is made by Quill. It doesn't allow to insert the <p> tag inside the blockquote.
Can I ask why you're using a platform which doesn't support a such a basic function? I notice, for example, that this forum has the ability hard-return inside blockquotes.
The solution for this is clearly to disable rich text editing, but if you do that then users have no toolbar in the editor at all. Can you re-enable an html tool bar for basic html functions after turning off rich text editor?
- Conflict with "scroll to id" plugin breaks page
Not sure what do you mean. Could you please clarify a bit?
The "scroll to ID" plugin is a smooth scrolling plugin, when it is enabled it the pages load very slowly, and move incredibly jerkily.
Simply users add an additional "Enter" after they finished the main comment text.
No, it's not. It randomly appears, most especially it seems everytime someone edits their comment it adds a hard return. This means some comments end up with 4 or 5 lines of blank space at the bottom.
We also have an issue with vote data regeneration. We had over 150,000 comments on our site, with thousands of likes. We need to be able to regenerate a lot of data, but the option for doing so has been greyed out. Is there a workaround?
We get around 50,000 views and between 500-1000 comments every day, and are facing many complications/complaints since you released this update. If we had known the sheer scale of the changes, or that we stood to perhaps lose data, we likely would not have done the update.
There are some new aspects which are great - the "reply to" function, with the clickable name, makes conversations much easier to follow. And the "edit comment" works much better than previous versions. But if we can't get basic functionality back we will have to roll back.
If we roll back, will our vote-data need to be regenerated again?