Jon Brown

Any hope of this getting resolved soon? I’m still stuck on v2.17 until this is fixed and stops running looping non-performant queries.

The change log doesn’t seem to mention this issue at all. Was this addressed in 2.18.1 or not?


Changelog
2.18.1 – Wednesday, 8th January 2025

• Improvement: Global – Added responsive support for gradient background settings.
• Fix: Image Gallery – Removed the automatic maximum limit for galleries with less than 8 images.
• Fix: Tabs – Resolved an issue wherein the tabs in vertical layouts were only clickable on the title.
• Fix: Global – Resolved an issue wherein the translated setting panels in some Spectra blocks would cause some Spectra Pro features in those blocks to not work as expected.
• Fix: Global – Resolved an issue causing a php error for str_replace() for font loading.
• Fix: Global – Resolved an issue wherein the self-hosted Google Fonts would not work as intended on the multisite’s first sub-site setup.
• Fix: Global – Resolved an issue in which some static and dynamic javascript strings were not translatable.
• Fix: Global – Resolved an issue where migration buttons were not clickable, preventing the migration process from running as expected.

• This reply was modified 2 months, 2 weeks ago by Jon Brown.

@thebengalboy even on the Spectra dashboard that query looking for blocks being used doesn’t scale and is going to crash large sites with few blocks used. Remove the code.

FWIW, I rolled back to 2.17.0 which doesn’t seem to include this show_nps_notice code. If this was an attempt to improve your Net Promoter Score… yikes that’s a big backfire.

You shouldn’t be just running massively huge queries recursively on people’s sites.

This is Spect(r)acularly misguided:
https://share.cleanshot.com/1N51RKrB
We only use blocks on a couple pages, so you’re querying our posts for your own marketing purposes and you end up looping through 10s of thousands of posts to see if we’ve used 5 blocks. This doesn’t scale and you’re nearly taking down the site (we have 100s of editors in the backend and this is happening endlessly on every admin page load).

https://share.cleanshot.com/k7c3dHfM

Seems like your running a query to try to count the number of blocks being used, but you’re querying pages and posts (180,000). You’re limiting it to 100, but then looping through is dozens and dozens of times 100 at a go. Why the heck are you even doing this, regardless it’s bringing the admin to a crawl. Is there an older version without this code? I can’t tell from the changelog.

https://share.cleanshot.com/gKZj7klH

wp theme mod remove --all would remove ALL theme mods, and might remove more than just your templates. https://developer.www.ads-software.com/cli/commands/theme/mod/remove/

Another way more specific way to do it would be:
wp post delete $(wp post list --post_type=wp_template --format=ids) --force
wp post delete $(wp post list --post_type=wp_template_part --format=ids) --force

Also a fatal on the browse plugins page. There is a chance this is related to another script.
https://share.cleanshot.com/CwBfxPxh

see https://www.wpallimport.com/documentation/import-variable-products-woocommerce/ specifically the section titled “Linking Multiple Variations Together to Form a Variable Product”

This isn’t an issue with the transients. It’s a PHP error from running an ancient version of PHP. Update to the current version of PHP, 8.2.

WP’s built in password protection is very basic. Once the password is entered a cookie is set and a user will be ale to access that page until the cookie expires. While you could write custom code to make that cookie expire immediately, it’d be easier to use on of the plugins that faciliate all this for you like https://www.ads-software.com/plugins/password-protect-page/ (yes it has an option to expire the password cookie immediately).

You seem to have setup password protection for that path, /wp-admin.

While there are plugins that could do this, my guess is that you may have set this up from your hosting control panel.

If your unfamiliar with those settings you might want to reach out to your web host support to investigate.

If it is a plugin, typically a security plugin, you can disable that pluign by renaming it’s plugin folder via FTP (or your web hosts file manager).

Usualy I rename the plugin folder form /wp-content/plugins/plugin_name/ to /wp-content/plugins/disabled_plugin_name/ but you literally can change the name however you like. The try logging in. If it doesn’t work, change the name back.

You really should repost this in the support forum for Elementor itself https://www.ads-software.com/support/plugin/elementor/

I’m guessing you used a script installer in Cpanel to install WordPress and when you did it asked if you wanted to install it into a /blog / directory.

The best/easiest path here is probably to ask your hosting support to assist in rectifying this as they’re most likely to be familar with the details of the installer script you used.

WordPress can’t, or at least shouldn’t be installed into a directory that already has files in it. That said, it certianly can be moved up to /public_html/. Moving it will require changes in several places: wp-config,php, database, and often in cPanel as well.

In your WordPress admin dashboard sidebar go to WooCommerce > Settings. Then click on the Emails tab. Scroll down below the long list of emails and you’ll see a section called “Email sender options”. That sets the email name and address that woocommerce emails are sent from.

Note however that setting the from email there doesn’t mean that WordPress is authorized be the mail server handling your business address to send emails as that address. Those emails therefore may be marked as spam if you do nothing else.

The best thing to do is use an SMTP plugin to setup email sending through SMTP. A plugin such as https://www.ads-software.com/plugins/fluent-smtp/ This will let you setup WordPress to use a remote email server like Google, AWS, Microsoft, etc. that is hosting your business email address.

I have no affiliation with Fluent, it’s just the free option availabe in the .org plugin directory that I personally prefer.

Furhter, you may need to setup DNS records for SPF, DKIM and DMARC to authorize sending emails. This can seem overwheleming, but there are a number of online guides to help. https://fluentsmtp.com/dmarc-spf-dkim/

There are several plugins that will import from a CSV to WooCommerce site.

I’ve successfully used both
https://www.ads-software.com/plugins/product-import-export-for-woo/
and
https://www.ads-software.com/plugins/woocommerce-xml-csv-product-import/ (note: this is a simplified version of WP All Import which can also import data from CSVs, and is more flexible).