msnewton

It really makes no sense to me that a user on a site (that happens to be hosted on a multisite installation) with admin privileges (but not super-admin) would be prevented from checking the “Keep paragraph tags” option. This, in fact, is causing me/us real headaches because a plugin that I’ve written relies upon all HTML be well-structured (contained within *some* tags) and the default setting — which admin users cannot change *on their own sites* — is for non-well-structured HTML.

Please allow all users with admin status to set the “Keep paragraph tags” option!

Well, I am keeping notes of this nature on GitHub:
https://github.com/Digital-Innovation-Lab/prospect/releases

I hope this is sufficient for your purposes. The manual will note any user-level requirements.

I can’t find a description for the format of the file — can you point me towards one?

Yes, updating from 2.5 to 2.6 and/or 2.7 requires updating map settings. This is explained thoroughly in the online manual:
https://docs.google.com/document/d/1NQO0ObqDIp576QpC5LvQ97d9vGB1YkrgSVhJZ22oIZg/edit#heading=h.5m4v72o2yjrk

FYI, I chanced upon the solution in an online search, tried it, and it works. I hope to prevent others from wasting precious time on such trivial details.

In a case such as this (creating download files that require _POST variables), the function that creates the file needs to be hooked in with the add_action(‘admin_init’) call.

Ridiculous, isn’t it?

PS. On one platform, the result is that the HTML for the webpage proceeds the data written out for the file. On another platform, the result is that the file contents are written out onto the screen. Clearly the issue is that the code doesn’t realize that two different outputs are intended: HTML for the screen and data for the file.