import vs DISALLOW_FILE_MODS

[Denis-de-Bernardy]

When DISALLOW_FILE_MODS is set to true, you cannot install an importer from the plugin repo.

Visiting Tools / Import yields the following screen:

If you have posts or comments in another system, WordPress can import those into this site. To get started, choose a system to import from below:

No importers are available.

That first line should be changed to explain that file mods are disabled and that the plugins must be installed manually. Better yet, the list should point to the relevant plugins in the repo and highlight that they need to be installed accordingly.

[Ipstenu]

Moved 'to get started...' so it only shows if you CAN import.

[Ipstenu]

The list is empty because get_importers() is empty.

Attached is a first pass that just moves the 'If you have posts or comments in another system...' down to the check if importers are empty, and only shows if they're not (this way we don't have to update strings yet).

The if empty check is where we'll want to put the robust checking in for the various options. Do we know what those would be other than DISALLOW_FILE_MODS?

[Denis-de-Bernardy]

@ipstenu: off the top of my head, try checking if the user can install plugins. The relevant cap is probably 'install_plugins' or something along those lines.

[Ipstenu]

That looks like it. I'm not sure if it'd be better to change "No importers are available." to something that says 'because none are installed and you don't have access to do so via WordPress. Plugins must be installed manually.' or change that whole check to something crazy robust and check all the permutations.

[swissspidy]

See also #38673.