Dion Hulse

There’s been some changes to this since most of you posted; Please try again and let us know if there’s ongoing problems.

Please note: Using SVN to check for plugin updates is not exactly ideal. Please consider using something like https://api.www.ads-software.com/plugins/info/1.0/ml-slider.json which will have a version field.

Hi @pat1701,

There’s two potentials here:

1. Whatever you use for WordPress updates is re-installing the plugin.
2. A malicious plugin is being installed and pretending to be Hello Dolly.

Because WordPress includes Hello Dolly by default, some WP management tools do automatically re-install it, however, WordPress itself does not re-install it if you remove it.

Because it’s included by default in WordPress, many malicious actors may install a malicious plugin and set it’s name to Hello Dolly to disguise it on your site. In other words, the plugin you see installed may not actually be Hello Dolly.

If you’re finding the plugin constantly re-installed, and there’s a chance that it may not be the Hello Dolly plugin, you should treat your site as infected by malware / hacked and run through the appropriate steps. Simply removing the plugin is unlikely to remove the infection, nor would it remove the way that they’ve got control over the website.

The below article may help with direction on scanning and cleaning up any infection.

FAQ My site was hacked

Hi @solocreativos,

Thanks for the report.

I’ve filed a bug for this at https://github.com/WordPress/wordpress-importer/issues/164 and I expect it’ll get resolved in a future version of the importer.

The issue is that the import file you’re uploading references a taxonomy that doesn’t exist on the new site, this likely means you’re not running the same plugins/themes on the new site as your existing site.

If you install those missing plugins, that may allow the import to proceed.

Hi,

This indeed a “problem” but not a cause for concern.

WordPress 6.6 did not properly remove these old WP 6.5 files during upgrade, and WordFence has decided to throw an alert about this.

It’s not a problem for your site, and when 6.6.1 is released, these files will automatically be cleaned up.

I’ve filed a core issue to ensure this is resolved as part of 6.6.1.

Hi @realact,

Those files are no longer present and are safe to remove.

I’ve opened a core ticket to make sure that happens automatically, it should’ve been in 6.6, but it’ll be in 6.6.1.

Hi @techbrett,

This is likely caused by a plugin or theme you’ve got installed, and not specifically WordPress or a WordPress update.

It’s highly likely that this is being triggered because of using PHP 8.1, with something that isn’t supporting it 100%. You may be able to switch to PHP 7.4 in your hosting control panel – or by asking their support team.

Additionally, PHP Deprecated notices shouldn’t be visible normally, but it’s likely that your WP_DEBUG settings are incorrectly set. You can set that to false (See https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/)

Your website is currently not showing anything, other than the deprecated errors, I expect this is because it’s also running into a Fatal error which isn’t being shown. You’d be able to get those details from your hosting panel as well.

Hi @asker1,

The “A in a square” toolbar item sounds like the new Block Editor toolbar to me.

The WordPress classic editor didn’t support such things as text-over-images as far as I recall and can find, it’s likely that there may have been plugins to add that functionality however, but the majority of these are no longer actively supported and as a result can be harder to find.

I would personally suggest that you try to use the Block Editor again, I don’t know the last time you tried it, but it’s come a long way in the last 15 major releases of WordPress, and would likely allow you to create the image you wish to have.
I understand it may not be perfect for your needs in other ways, but you may be able to use it purely to create the image block and then switch back to the classic editor for the rest of the editing – I’m unsure if that’ll work properly though, please try testing it on a new post/page rather than the current page you’re working on!

Hi @poancia, apologies for this, this has now been resolved!

You should be able to follow the link in your email, or attempt to change it again.

Let me know if you have any problems!

I moved my site to a new subfolder and made (what I thought were) the appropriate config changes.

Are you able to share the steps you’ve taken for that?

Do you have any URL options visible under Settings -> Media? (Not everyone does)

Does the new URL show correctly under Settings -> General?

Hi @fickwp,

There hasn’t been any widespread reports of such issues.

It’s hard for us to know if there’s anything causing this, as there’s a lot of variables in play outside of our control.
For example, your upstream provider may be limiting bandwidth to www.ads-software.com, or a network link they use that connects to a network link we use might be at capacity.

Some things that might help:

• Can you check if the speed via https://downloads.www.ads-software.com/release/latest.zip is the same poor performance?
• Can you provide the output of mtr -T -P 443 www.ads-software.com to see if there’s any packet loss happening on an intermediate network?
• Can you provide a test IP of your servers, so we can perform the above in reverse?

There’s a also chance that your servers are hosted on a network which has been the source of recent traffic that has tripped up DDOS protections in our upstream providers network.

Hi @atakanau,

Using %1s is not recommended (or supported by wpdb::prepare()) for this, as it’s actually bypassing the entire purpose of using prepared queries.
Furthermore %1s is actually saying “Print %s with at least 1 character”, not the same as %1$s which is “The first argument presented as a string”. wpdb::prepare() accepts %1s for backwards compatibility with old code, but it should not be used intentionally.

This code is the same syntactically as what you’re currently using: (which has no SQLi prevention in place)

$ids = implode(',',$id_arr);
$wpdb->query( $wpdb->prepare( "SELECT ... WHERE ID IN( $ids ) " ) );

The proper way to achieve what you want, would be to apply some sanitization to the input before interpolating:

$ids = implode( ',', array_map( 'intval', $id_arr ) );
$wpdb->get_results( "SELECT ... WHERE ID IN( $ids ) " );

You’ll find many examples of this in WordPress files, such as WP_Query:

https://github.com/WordPress/wordpress-develop/blob/e5935547d2faeaedb857f77f878c4d08d2b3389b/src/wp-includes/class-wp-query.php#L2197-L2206

NOTE: If you’re looking to use strings rathe than IDs, you’d have to do something like this to properly escape each piece:

$slugs = '"' . implode( '" , "', array_map( 'esc_sql', $slugs ) ) ) ) . '"';
$wpdb->get_results( "SELECT ... WHERE post_name IN( $slugs ) " );

for example: https://github.com/WordPress/wordpress-develop/blob/e5935547d2faeaedb857f77f878c4d08d2b3389b/src/wp-includes/class-wp-query.php#L2550

There’s other approaches to this, like using array_fill() to generate the placeholders: https://stackoverflow.com/a/38735186

There’s work to support list notation with WordPress’s prepared statements in this trac ticket: https://core.trac.www.ads-software.com/ticket/54042

Hi @ofmarconi, there’s some discussion on this in this forum thread:

https://www.ads-software.com/support/topic/what-happened-to-the-plugin-search-system/

Hi!

I’ve made some tweaks to the search weighting of english titles in localised searches, which should help the examples shown here.

The www.ads-software.com plugin search, when done from a localised WordPress install, boosts plugins translated into your locale more than it would for an english-only plugin. The reasoning here is that it’s likely that either the phrases you’re searching are going to be in your own language, or that you’d prefer a plugin in your own language.

This is also visible when searching on https://br.www.ads-software.com/plugins/ vs https://www.ads-software.com/plugins/ – both should give a slightly different result, but hopefully not too different.

In the examples provided here, the plugin name isn’t translated, and so the localised title index was unavailable, but the weight of the english title was not enough to result in it ranking highly.
It’s likely that this wasn’t previously visible, as for some plugins it would’ve been matching on other fields instead of the title, but over time as additional translations are added for other plugins (or even the plugin you’re looking for) the one you expected to see became less and less relevant to the search engine.

Can you please do some additional searches to see if the results appear to be more what you expect? It’s likely not 100% perfect, but no search engine is.

Hi @thesheryar

Thanks for sharing the issue with Underline, I’m using this response to test the other various formatting options too. Strike _Sub ^Super Keyboard Input Inline Code <bdo lang=”ar” dir=”rtl”>Language</bdo> Bold Italic Link

This is justified.

Edit: Again, Underlined, and Language

• This reply was modified 7 months, 1 week ago by Dion Hulse. Reason: testing

Hi @bayejid00,

I’m unable to duplicate this using the latest Query Monitor and Debug bar.

The error you’ve shared suggests that there might be something else in your environment loading Debug Bar, possibly another version of it.

I’ve also tried using the WordPress playground to run a fresh WordPress site with both plugins active, and it doesn’t have the error either: https://playground.wordpress.net/?plugin=query-monitor&plugin=debug-bar

Are you able to duplicate this on a different WordPress site at all?