room34

I am also observing this issue. If I try to upload an SVG logo or favicon in the Customizer > Site Identity, it’s giving the file type error message.

I can upload the same files directly in the Media Library no problem, and then select them from the Media Library in the Customizer and it works, but the direct upload in Customizer does not.

This issue is now resolved in 11.5.3.2.

Thanks for bringing this to my attention. An update will be released within the next couple of hours.

Well of course, as soon as I posted this, I found the answer. Here it is for anyone else in my situation!

https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/#plugins-on-wordpress-org

Thanks for the quick response! This is a great plugin.

@recetteitalienne I’m sure the moderators will be on this soon enough, but you can’t ask about paid plugins in these forums. Try ACF support.

@electropatata Are you able to send me the link to your site? I’ve tested the plugin with my sandbox site set to Spanish and everything is working properly. There’s nothing about translations that should have any effect on the order of the events in the calendar.

Can you share a link to your page? If you prefer not to post those details here, please use the support request form and be sure to include the full shortcode and your System Report. Thanks.

Version 3.5.1 is on its way to the repository. I’ve completely revamped the process of defining the Settings array. The basic properties of the settings need to be available on plugins_loaded but the translated text strings are only needed on the No Nonsense admin page, and can be merged into the array later, so that’s what I’ve done.

I also added complete machine-translated files for German and Dutch, because I noticed the community-provided translation files are incomplete. Unfortunately in the process I also discovered that WordPress prioritizes community translations over the ones contained directly in the plugin, so I’m looking into how to work around that.

Unfortunately, I believed this had resolved the issue, but it turns out to be a bit more complicated.

This is a chicken-and-egg scenario. No Nonsense needs to load its array of settings information — which includes translated text strings — on the plugins_loaded hook in order to actually work, but doing so triggers the error message. Loading it late enough to get rid of the error message causes a lot of No Nonsense’s features not to work, because they’re acting on parts of WordPress that have already been loaded. (A really simple example is the “Remove Howdy” setting.)

I’m investigating whether or not I might be able to rework the settings array so its functional aspects continue to get loaded on plugins_loaded but its translated text strings (which are only needed for displaying the admin page) get assigned later.

• This reply was modified 3 months, 2 weeks ago by room34.

This issue is fixed now in version 3.5.0.2.

OK… kind of a weird situation. This issue actually was fixed in version 3.5.0, but it was a hotfix that was added about an hour after 3.5.0 was originally released. You must have updated before the hotfix.

I’ve bumped the version to 3.5.0.1 so you can get the update. (Re-downloading 3.5.0 from the repository also would have fixed the issue.)

Thanks for bringing this to my attention. Version 3.5.0 included a change that resolved this in an earlier beta of WordPress 6.7 but something else must have changed. I’ll get a fix released shortly.

Thanks… I’ll look into the feasibility of making the sub-settings dependent on the status of the “parent” setting.

@ned4spd8874 If you have root access for the Ubuntu server, you can go in and change the permissions. By default on Ubuntu all of the files in the Apache document root should have www-data as both the owner and the group.

I make a habit on my Ubuntu servers to add my own user to the www-data group, and make sure the group has full read/write permission on everything. That makes it easier for me to manually edit files over SFTP without causing these kinds of permission issues when updates run. But keep in mind that if you add any new files this way, you may still get permission errors when updates run.