Skip to content

Migrating configurations from INI files

Jump to bottom
msorenson edited this page Jun 9, 2015 · 4 revisions

Should I be worried about this?

If you are a theme developer that is migrating an Infinity theme fork, or an Infinity child theme to be compatible with version 1.2 or higher, then yes.

How do I know if I need to take action on this?

If you edited the bundled INI configuration files, or added your own overriding INI files, you will need to convert only the specific options you changed or overrode to the new syntax. Don't worry, it's super easy.

What happened to using INI files, anyways?

Originally, INI files were chosen to make it easy for developers to add additional configurations and modify existing ones. Two things occurred that made INI files no longer a good choice for this:

  1. Quite a few people complained that it wasn't possible to translate the strings in the INI files. We didn't think this would ever be an issue... but when developers started putting default string values for options which would appear on the front end, it became a real problem.

  2. The WordPress theme-check plugin added the PHP functions which load and parse INI files to their black list of disallowed functions due to the fact that they open files directly from disk. This prevents any Infinity based themes from being accepted into the WordPress.org free theme directory.

Clone this wiki locally