achanne

I found the answer!!! In the table wp_options (wp_dxvd_options in our case), for wp_dxvd_user_roles (wp_user_roles in most other cases) was set to ‘a:0{}’. Since the correct value is pretty generic, the simple fix was to go to a working single site and just copy the value from there and paste into the value field in our database.

Just to provide an update: I installed the plugin Wordfence, and it was able to block https://www.example.com/wp-json/wp/v2/users without preventing REST API from working.

Most likely, the hacker ran a program that grabs admin usernames and other data from /wp-json/wp/v2/users and then the program uses that info to log in without a password. So after blocking access (such as by installing Wordfence), it may be a good idea to change the username used for login rather than your password (although it doesn’t hurt to change that as well).

The file “object-cache.php” was actually placed there by “APCu Object Cache Drop-in”. This is not a type of plugin that is managed through or listed in the WP admin dashboard, and was most likely installed by the hosting provider. So, I logged in to the hosting account, and turned off caching from there, then went back to the WP admin dashboard and installed the plugin “WP Super Cache”. So far the site hasn’t crashed and I hope it stays that way.

Thanks again. Is there a way I can turn this off myself…perhaps through the configuration file? Would this prevent caching plugins (such as WP Super Cache) from working?

We are using FVM and a3 Lazyload, but I’m not sure if those are caching plugins. I think we might have used W3 Total Cache and/or WP Super Cache in the past before. As I have mentioned, plugins have been ruled out when they were all deactivated, unless they leave files behind that we are not aware of.

Additional note: This is the error message:

Error Details
=============
An error of type E_ERROR was caused in line 136 of the file /home3/clubfood/public_html/community/wp-content/themes/theme_name/inc/wp-less.php. Error message: Uncaught TypeError: array_search(): Argument #2 ($haystack) must be of type array, null given in /home3/clubfood/public_html/community/wp-content/themes/theme_name/inc/wp-less.php:136
Stack trace:
#0 /home3/clubfood/public_html/community/wp-content/themes/theme_name/inc/wp-less.php(136): array_search('home3/clubfood/...', NULL)
#1 /home3/clubfood/public_html/community/wp-includes/class-wp-hook.php(307): wp_less->http_request_args(Array, 'https://api.word...')
#2 /home3/clubfood/public_html/community/wp-includes/plugin.php(189): WP_Hook->apply_filters(Array, Array)
#3 /home3/clubfood/public_html/community/wp-includes/class-wp-http.php(232): apply_filters('http_request_ar...', Array, 'https://api.word...')
#4 /home3/clubfood/public_html/community/wp-includes/class-wp-http.php(614): WP_Http->request('https://api.word...', Array)
#5 /home3/clubfood/public_html/community/wp-includes/http.php(179): WP_Http->post('https://api.word...', Array)
#6 /home3/clubfood/public_html/community/wp-includes/update.php(415): wp_remote_post('https://api.word...', Array)
#7 /home3/clubfood/public_html/community/wp-includes/class-wp-hook.php(305): wp_update_plugins()
#8 /home3/clubfood/public_html/community/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
#9 /home3/clubfood/public_html/community/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
#10 /home3/clubfood/public_html/community/wp-admin/includes/class-plugin-upgrader.php(371): do_action('upgrader_proces...', Object(Plugin_Upgrader), Array)
#11 /home3/clubfood/public_html/community/wp-admin/update.php(51): Plugin_Upgrader->bulk_upgrade(Array)
#12 {main}
  thrown

Thanks, but internal URLs are all working properly. It’s just image src code that’s not linking to correct URL. Will changing 301 redirects in .htaccess solve this issue? If so, what should I add/change in the .htaccess file?

@brainfestation Is this a file that you simply add to the plugin folder? If so, does it only work if you’re signed up with Imperva (and thus have an Imperva settings dashboard) or does it work with third parties using Imperva (such as Sitelock)? If it works with all, would you be able to share the file? Thanks.

@brainfestation We are using SiteLock for security, and it looks like SiteLock has outsourced to Imperva. I cleared the Trueshield cache in our Sitelock dashboard and was able to restore functionality of the Yoast SEO but only temporarily as the plugin was broken again on refresh. I called SiteLock and they said the only thing they can do is whitelist the application’s IP address. Hopefully, I sent them the correct IP address and this will solve the issue.

@brainfestation @mikes41720 I have posted my bug report at GitHub. I have also found three interesting things (which I have just added to my bug report post): you can actually predict if Yoast will work in editor without even having to go to your site – in other words, bypassing all plugins, themes, and other site components completely. By going to view-source directly (i.e. view-source…/wp-content/plugins/wordpress-seo/js/dist/post-edit-1740.js), do a ctrl+f search for /^*-+ (no spaces)and if you find it exists twice, Yoast SEO will not work in editor in that browser.

The second interesting thing is if I add a single line comment at the top of the js file post-edit-1740.js (for example //THIS IS A COMMENT), then do a view-source, comment disappears if it has been reformatted by the browser. If the comment is there, Yoast should work properly (you will also find that the regex will be valid – i.e. with the spaces before the *)

And finally, even if the code appears the way it should be and/or if Yoast is working properly, Ctrl-F5 may cause the “bad” version to reload, breaking Yoast.

Just following my last reply with more info: The site owner has updated Edge when the computer restarted, and now Yoast SEO doesn’t even work in Edge anymore. So I’m pretty sure browser updates are causing the plugin to break. Could you please look into this and let me know. Thanks.

Hello,

As suggested, I have used the troubleshooting plugin to run Yoast SEO with all other plugins disabled, with a different theme (Twenty Twenty One), and even tried in private browsing mode, and with cache cleared but none of those or any combination fixed the problem. I even tried with Jquery Migrate Helper installed and activated but that did not solve the issue. Meanwhile, the error console continues to show the same error in which there is “nothing to repeat” with invalid regular expression: /^*-+:*$/ in post-edit-1740.js:1.

BUT…here is something interesting: The site owner/writer started having the issue on Sunday after updating Chrome browser (it was fine before browser was updated). However, in Edge on the owner’s computer, Yoast SEO continues to work without any problems…at least for now. On the other hand, on my own computer, Yoast appears broken in editor on all browsers (Firefox, Chrome, and Edge).

Please let me know. Thanks.

Hello,

We are using the latest version of WP and I have temporarily disabled ACF Content Analysis for Yoast SEO plugin but the problem is still the same. I have also tried different browsers – Firefox, Chrome, and Edge – and also with cache cleared but it still does not work in any browser. With ACF Content Analysis for Yoast SEO disabled, here is a screenshot of the console in Edge: https://alvenh.com/screenshots/yoast_seo_error.png

Please let me know. Thanks.

Thanks for the reply. Because we are unable to update the theme, I will try to contact the theme publisher as you have suggested.

Hello, I have found the problem with the first issue: there were no classes or ID’s to distinguish “previous” from “next” page links, so for the NEXT selector, I added “a:last-of-type”. But I still have the problem with non-stop scrolling after reaching the last page. Is there a way to stop it after getting to the last post?

An example of a page with YITH infinite scrolling:
https://clubfoody.com/category/beef/

I don’t know how to attach an image to this reply but here are my configurations:
Navigation Selector: .pagination-w.hide-for-isotope
Next Selector: .pagination-w.hide-for-isotope a:last-of-type
Item Selector: .item-isotope
Content Selector: .index-isotope
Loading Image: https://clubfoody.com/wp-content/themes/pluto-osetin-theme-child/assets/images/ajax-loaders/loader-light-blue-more-recipes.gif

Thanks.