Skip to content
This repository has been archived by the owner on Mar 29, 2021. It is now read-only.

Starting to slow down the responses when typing in >1500 words #601

Open
4faster opened this issue Jan 24, 2020 · 2 comments
Open

Starting to slow down the responses when typing in >1500 words #601

4faster opened this issue Jan 24, 2020 · 2 comments

Comments

@4faster
Copy link

4faster commented Jan 24, 2020

ABT Version: 5.2.2

PHP Version: 7.2

Theme: https://www.wpexplorer.com/gopress-wordpress-theme/

Plugin List:

  • Academic Blogger's Toolkit
  • Akismet Anti-Spam
  • Booter - Bots & Crawlers Manager
  • Code Snippets
  • Code Syntax Block
  • Health Check & Troubleshooting
  • jQuery Updater
  • LiteSpeed Cache
  • Loginizer
  • LuckyWP Table of Contents
  • Polylang
  • Really Simple SSL
  • TablePress
  • Theme and plugin translation for Polylang (TTfP)
  • WP-KaTeX
  • WPS Hide Login
  • Yoast SEO
    Note: I already disable all of them except ABT, and the issue still occurred

Browser:
Google Chrome 79.0.3945.130
Firefox 72.0.2

issue location: admin edit post

Expected behavior:
Instant writing response in longer articles (>1000 words). in my case, is around 1500-3000 words

Actual behavior:
When editing a post with less than 1000 words, I didn't feel slow at all. But for longer articles, it needs around 1-3 seconds to display the typed words after I typed maybe 3-4 words. There are around 4-5 images (100-200kb/image) in a single post

Console messages:
I think there is no js error,

This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0. post.php

JQMIGRATE: Migrate is installed, version 1.4.1 load-scripts.php:8:552

Loading mixed (insecure) display content “http://indowhiz.com/articles/wp-content/uploads/2019/03/favicon-image.g.png” on a secure page
2 FaviconLoader.jsm:174:19

MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. wp-tinymce.js:3:9108

Computer spec:
Processor: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 8068MB RAM
using SSD
WIn 10

@4faster
Copy link
Author

4faster commented Jan 25, 2020

ABT v5.2.2 facts, in my experience:
ABT leaves the references and citation position inside each post as HTML tags. When the ABT plugin is deactivated, that tag is unharmed. It almost can be displayed on the front page even the plugin is deactivated, which is BEST.

Then right now, my solution to this problem is:

  1. deactivate the ABT plugin when editing or creating a post
  2. manually record some new citations/footnotes at the bottom along with the place of the citation (using something like ###citation 2 here### or ###[2]###).
  3. when finish editing post, reactivate the ABT plugin
  4. convert the manual citation into ABT data.

@adriandomenico
Copy link

adriandomenico commented Apr 15, 2020

Hi Derek,

I've been using the plugin very happily on a live site but, as said above, when I hit about 1200 words there is noticeable slow down in typing input.

On test pages, with up to 2000 words in paragraph blocks only, there is typing slow down but it is usable with the plugin activated. However, with a few quote blocks added to the page, typing input delay becomes excessive even with 1500-1700 words and over 2000 words ABT has to be deactivated.

Admittedly, these are large articles but deactivating the plugin always resolves the issue, no matter how large the article. I've tested up to 5000 words. On projects that size, it's best, as suggested above, to leave the plugin deactivated. However, activating it to then add references can be hit or miss. There can be a delay when adding a citation and if one fails no more can be added.

I've had a look but it's beyond my competence what the problem could be. This is a huge piece of work. I had to do a lot of work in re-writing my theme for the updated block editor in WP 5.4. That was a real pain! But perhaps that is what is at the bottom of this. The block editor has changed significantly, and this time around it has not been pleasant for developers!

I'm guess that over there, like here in the UK, you've got other things on your mind right now, so this will not be a priority - and not least because you do this voluntarily. I totally get it. But it's worth saying that this is a great plugin; very well thought out and supremely useful. I hope you can find the time to resolve these issues because I'd certainly incorporate it in my workflow - and have to admit a certain sadness that I cannot!

Regards,

Adrian

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants