searching

Hi @mikrofree

Could you please right click on the page, select “Inspect page”, then look for the “Console” tab. If there’s any messages or text there, copy and I paste it here.

Normally, it should instantly show the results once it’s at 100%. Hopefully there’s something the console that will tell me what’s going on.

JQMIGRATE: Migrate is installed, version 3.4.1
tools.php:686 [Intervention]Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113
chrome-extension://d…efaobl/tooltip.js:1 Uncaught SyntaxError: Malformed arrow function parameter list
link-detector.js:42 link-detect ON !
link-detector.js:54 got env Object
link-detector.js:64 Finding links
link-detector.js:75 Res Array(0)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
useLocalStorage.js:61 Uncaught (in promise) DOMException: Failed to execute ‘setItem’ on ‘Storage’: Setting the value of ‘fmb_found_blocks’ exceeded the quota.
at https://logsinfos.fr/wp-content/plugins/find-my-blocks//assets/js/find-my-blocks.js?ver=1714376489:1:24099
at setCachedFoundBlocks (https://logsinfos.fr/wp-content/plugins/find-my-blocks//assets/js/find-my-blocks.js?ver=1714376489:1:24601)
at startSearch (https://logsinfos.fr/wp-content/plugins/find-my-blocks//assets/js/find-my-blocks.js?ver=1714376489:1:23087)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
tools.php:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)

    [NEW] Explain Console errors by using Copilot in Edge: click 
     to explain an error. 
    Learn more
    Don't show again

VM3355:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
_storageChangeDispatcher @ content.js:2
_storageChangeDispatcherCallback @ content.js:2
Afficher 2 plus de cadres
Afficher moins
VM3356:1 Uncaught (in promise) SyntaxError: “[object Object]” is not valid JSON
at JSON.parse ()
at l._storageChangeDispatcher (content.js:2:855976)
at _storageChangeDispatcherCallback (content.js:2:855424)
_storageChangeDispatcher @ content.js:2
_storageChangeDispatcherCallback @ content.js:2
Afficher 2 plus de cadres
Afficher moins

Thank you for this! I see it’s likely due to the browser storage being maxed out. The browser storage is meant to store the results so you don’t have to re-scan if you refresh the page.

How many posts do you roughly have?

I’ll look at creating scalable solution for the browser storage in the next update.

Console with Firefox :

TSS: excluded result: false content-scripts.js:1:63008
TSS: hosted page injected tools.php:4:17
InstallTrigger est obsolète et sera supprimé prochainement. tools.php:96:13
JQMIGRATE: Migrate is installed, version 3.4.1 load-scripts.php:5:981
Uncaught (in promise) DOMException: The quota has been exceeded.
z useLocalStorage.js:61
setCachedFoundBlocks usePreferences.js:42
startSearch useFinder.js:182

Searching for your blocks…

Progress: 100%

Scanning batch 573 out of 573

Total block instances detected: 33302 in 5704 locations.

I’m having the same problem, with Safari: scanning batch 369 of 369 / Total block instances detected 8509 in 3682 locations.

It worked, however, with Chrome.

Same issue here. I normally use Safari, but used Chrome for the search based on the previous reply. My scan frequency was set to Medium.

Uncaught (in promise) DOMException: Failed to execute 'setItem' on 'Storage': Setting the value of 'fmb_found_blocks' exceeded the quota.
    at https://example.com/wp-content/plugins/find-my-blocks//assets/js/find-my-blocks.js?ver=1714411101:1:24268
    at setCachedFoundBlocks (https://example.com/wp-content/plugins/find-my-blocks//assets/js/find-my-blocks.js?ver=1714411101:1:24770)
    at startSearch (https://example.com/wp-content/plugins/find-my-blocks//assets/js/find-my-blocks.js?ver=1714411101:1:23158)

Searching for your blocks...
Progress: 100%

Scanning batch 637 out of 637

Total block instances detected: 77187 in 63481 locations.

• This reply was modified 6 months, 3 weeks ago by JeanPaulH.

Hi everyone! Thank you for sending the information.

I believe switching to IndexedDB from LocalStorage will be solution.

LocalStorage is limited by browsers to 5-10MB, which would fail on large sites.
IndexedDB can use more available disk space. Otherwise it will fail gracefully, allowing you to still view the found blocks.

The cache is stored on your device/browser, so your WordPress database remains fast.

I’ve added the beta version with IndexedDB here: https://findmyblocks.com/download/

Please let me know if you run into issues (or none) ??

I can confirm 4.2.0-beta1 solves the issue. Output is now shown correctly after the scan. Tested with latest Safari/macOS.

Thank you for reporting back @djr ! Does the UI slow down at your scale?

Leaning into IndexedDB seems to be the way forward.

@mikrofree @billher please let me know your experience with beta when you’ve had time ??

Does the UI slow down at your scale?

Yes. As in; completely unable to work with. But ONLY when I open a block with a lot of occurrences, like the core/classic-editor block (over 60K occurrences). The UI then freezes to the point I can’t open it anymore. After some digging I found clearing the FMB LocalStorage (which holds the pointers) releases the UI, but then I have to do the scan all over again. So right now I just avoid opening the core/classic-editor block. But it’s less than ideal.

Have you tried something like FakerPress or another tool to just generate a lot of bogus content to test sites like ours?

Thanks. Works well with Safari Version 17.4.1 (19618.1.15.11.14). Response seems near instantaneous on blocks found in 3100 locations.

I have added React Virtualization into the latest beta. This method of rendering will kick in when results for a block is over 2000+. You should see the result list, almost instantly without performance loss.

@djr For references I used DemoPress to generate block content since FakerPress didn’t seem to.

Here’s the latest beta: https://findmyblocks.com/download/

In my testing it works really well, please let me know if it’s the same case you ??

Marvellous! My issue with the UI sluginess has been resolved completely. The core/classic-editor block now shows ”?Performance virtualization applied to large list.” and is as instant as the other block overviews.

All my other blocks are under 2.000 occurrences, so I can only check with the core/classic block, but really happy how this beta has turned out. I can now say farewell to 10up’s Block Catalog, which was also fine, but didn’t show a complete overview of block occurrences over all custom post types.

@djr for what it’s worth, Block Catalog already works on all public custom post types. If you have a private CPT that isn’t being included, there is a filter in place to override this called block_catalog_post_types: https://github.com/10up/block-catalog/blob/develop/includes/utility.php#L134.