Dion Hulse
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: api.ww.wp.xz.cn/statsDaily.
Forum: Plugins
In reply to: [Add From Server] Happy to help with ongoing maintenanceHi Matt,
I’ve responded in the GitHub issue you’ve opened: https://github.com/dd32/add-from-server/issues/9
Forum: Fixing WordPress
In reply to: .user.ini publicly accessibleHi @sounds,
You’ve created this topic in the WordPress Importer forum, but the file specified is not created by the importer, nor is the Importer the security scanner.
I’ve moved this thread to the
Fixing WordPressforum.Most security scanning plugins (If within WordPress) can only scan the files on disk, it doesn’t verify if the file is actually accessible. This is a failure of those plugins.
If you can access the file still by going to https://example.org/.user.ini then the .htaccess isn’t applying, and you may want to contact your web host to determine why. You may alsio find that the contents of the ini file does not matter to you, and having it public is fine. Security scanners can have false positives.
Forum: Plugins
In reply to: [Gutenberg] Gutenberg and Blocks Everywhere plugin@hebhansen Apologies, I was on holidays.
ww.wp.xz.cn uses a Multisite architecture, as such, ww.wp.xz.cn vs ww.wp.xz.cn/support are two different “Sites” each with their own set of plugins.
It is possible to use a mu-plugin to load a different plugin based on the URL being viewed though, but I would suggest NOT doing this on different paths of a single site. See [1] [2]
Forum: Plugins
In reply to: [Gutenberg] Gutenberg and Blocks Everywhere pluginSo this conclusion means that this site ww.wp.xz.cn uses an antiquated Gutenberg?
Unfortunately yes, the ww.wp.xz.cn Support Forums specifically use Gutenberg 17.9 at present due to this compatibility constraint. We’d like to replace the Blocks Everywhere integration on the forums with another solution, preferably natively supported by bbPress, but we don’t have a timeline on this at present.
We use the latest releases of Gutenberg everywhere else on ww.wp.xz.cn.
Forum: Plugins
In reply to: [WordPress Importer] Installation failedHello @molliem,
That error generally means that you’ve already got the plugin installed, or another plugin that is installed using the
wordpress-importerpath.Can you check what files you have in your
wp-content/plugins/wordpress-importerpath in your hosting environment? You’ll need to do this through the hosting control panel rather than through WordPress.Forum: Plugins
In reply to: [WordPress Importer] Version 0.9.1 trips anti-malwareFYI @zieladam
@headwall thanks for letting us know, in future if you wish, you can also report via GitHub: https://github.com/WordPress/wordpress-importer
Forum: Plugins
In reply to: [ww.wp.xz.cn Glossary] Use unitless value for line-heightThanks! This has been updated in trunk: https://plugins.trac.ww.wp.xz.cn/changeset/3359490
Forum: Plugins
In reply to: [WordPress Importer] 0.9.0 update WP 6.8.2 compatibility?Hi @willemb2,
0.9.0 was incorrectly released with
Tested up to: 6.7(ie. it wasn’t increased to 6.8 prior to release).After I noticed this, I updated the tested-up-to value: https://github.com/WordPress/wordpress-importer/pull/203 and updated ww.wp.xz.cn to show
6.8.2even though that’s not what is specified in the plugins readme.txt.The plugin installed on sites however would still have that old tested-up-to version. It’s unfortunate, but will be resolved with the next version of the plugin.
Thanks for raising it, sorry for any confusion it caused.
Forum: Plugins
In reply to: [Add From Server] Thumbs createdYes, WordPress now supports creating thumbnails of PDF files. I believe this feature was added in WordPress 4.7 but was dependent upon server support.
This plugin only replaces the “Upload from browser” segment of the upload process, all standard WordPress upload functionalities are still intended to run, which includes making thumbnails of uploaded content.
I hope this helps.
Forum: Plugins
In reply to: [WordPress Importer] 500 Error on plugin deactivateWere you able to resolve this?
Without further information, it’s not possible for me to provide you with any direct solution.I would advise looking at your PHP Error logs and see what is causing the 500 error – It’s likely that another plugin, or your theme, is reliant upon the plugin being installed. Although I’m not aware of any plugins which would.
This plugin itself has no code, nor does WordPress, which would cause your website to 500 error after it’s removal.
Forum: Everything else WordPress
In reply to: Unable to update ww.wp.xz.cn profile@konamiman You should be able to update it now.
Forum: Everything else WordPress
In reply to: svn.wordpress http status 429There’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.ww.wp.xz.cn/plugins/info/1.0/ml-slider.jsonwhich will have aversionfield.Forum: Plugins
In reply to: [Hello Dolly] Plugin installed by hackerHi @pat1701,
There’s two potentials here:
- Whatever you use for WordPress updates is re-installing the plugin.
- 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.