- last update
over 1 year ago Composer require-dev failure - π©πͺGermany Anybody Porta Westfalica
It's unbelievable. This critical issue exists since > 2 years and the maintainers just don't care? I think they must have missed this issue. Going to contact them via PM.
@Nixou could you please provide the patch as MR to make it easier to review and merge for the maintainers?
Thanks! :)
Related issue : π Page freeze caused by Symfony 6 non-scalar error when tokensNotFound is triggered Needs review . There is a patch which solved this problem.
- π©πͺGermany Anybody Porta Westfalica
Thanks @omar_emailat - still this are separate issues. The frontend should never wait for the response, but run async, was written above.
- Status changed to Needs work
5 months ago 6:39am 19 September 2024 - π©πͺGermany Anybody Porta Westfalica
Next step should be to prepare a MR from the latest patch. This is still horrible to use, waiting for the UI.
For that reason, I'd suggest adding a note to the description of the new setting:
+ $form['auto_refresh']['auto_refresh_seo_result'] = [ + '#type' => 'checkbox', + '#title' => $this->t('Enable auto refresh of the Real Time SEO widget result'), + '#description' => $this->t('You can use this setting to allow or deny auto refreshing of the Real Time SEO widget results after a value of a form field is changed and a field focus is lost.'), + '#default_value' => $config->get('auto_refresh_seo_result'), + ];
like
Please note that this may cause UI delays, waiting for e.g. the Metatag values to become available to calculate the score
(A native speaker should improve the sentence).
- π©πͺGermany Grevil
LGTM! Tested it and everything seems to be working as expected!
Added 2 more comments otherwise RTBC.
- π©πͺGermany Anybody Porta Westfalica
Perfectly fine now @lrwebks! RTBC from my side, thank you!!
- Status changed to RTBC
about 2 months ago 8:02pm 9 January 2025 -
kingdutch β
committed 6dccb166 on 8.x-2.x
Issue #3008802 by anybody, knyshuk.vova, lrwebks, the_turk, flefle,...
-
kingdutch β
committed 6dccb166 on 8.x-2.x
-
kingdutch β
committed 48553703 on 8.x-2.x
Issue #3008802 by anybody, knyshuk.vova, lrwebks, the_turk, flefle,...
-
kingdutch β
committed 48553703 on 8.x-2.x
- π³π±Netherlands kingdutch
I've been hoping for the past time that I'd find the time to fully update the Real-Time SEO module to the now released version of the Yoast SEO library so that we could move to webworkers and fix this issue. However, unfortunately that has required more time (and a better development set-up then I currently have available).
Given that the first release of Drupal CMS is around the corner and the Real-Time SEO module will be part of it, I'm adding the button and tagging a stable release. However, I do hope that in a future release we can once again remove the button and go back to "Real-Time" while preserving a smooth experience :)
While merging I've split this issue in two. One to refactor the controller into a SettingsForm and the other to introduce the actual change with the new setting. I also fixed some comments to use more inclusive language.
Thanks for your contributions everyone!
- π©πͺGermany Anybody Porta Westfalica
Hi and thank you so much @kingdutch for taking the time for this project! We've been waiting years for this to be fixed and never used the project because of the broken state of this issue.
Reading the comments and the MR, I think we should open a follow-up to also fix the JS-side of this issue.
The root cause here is blocking JavaScript and I think we might also want to remove jQuery?The new option gives us the opportunity to disable the auto-refresh and makes the module usable again, but to have the functionality fixed, the JS needs to be corrected.
Do you agree? Should we open a follow-up for replacing jQuery by Vanilla JS and remove this blocking implementation combined?
- π³π±Netherlands kingdutch
Hey Anybody,
Yes I think that follow-up would be π Update YoastSEO JS to recent version Needs work . The newest release for the Yoast SEO library which finally came somewhere last year moves most of the processing to a webworker and keeps only the UI updates on the main thread. So that ensures that even if the server needs a bit more time we're not blocking.
My 5 year ago developer idea was to do that update with an overhaul of the widget itself and move that to React so that there's fewer event listeners and a more linear "Updated data comes in" -> "Render UI element top down" approach. One of the features that that should enable in the future is multiple keywords at the same time. However, I think that's a much larger undertaking so it makes sense to refocus the update issue to moving to the newest version as-is and seeing if we can only make smaller improvements to the existing widget, like replacing jQuery with vanilla JS.
- π©πͺGermany stefan.korn Jossgrund
I suppose this addresses β¨ Allow configuring of manual checking per field Postponed: needs info as well (using a site wide setting instead of form widget setting though). Maybe maintainers should decide whether to close β¨ Allow configuring of manual checking per field Postponed: needs info now as a duplicate or not.
- π©πͺGermany Anybody Porta Westfalica
I added the point from #36 / #37 to π Update YoastSEO JS to recent version Needs work FYI
Automatically closed - issue fixed for 2 weeks with no activity.