F2 WP theme and Flexi Pages Widget updated

F2 WordPress theme updated to v1.0.7.

  • Added localization in Russian and Chinese languages. Thanks to Mihail Pomaskin and Awu for the Russian and Chinese translations respectively.
  • Minor improvements in styling.

Flexi Pages Widget plugin for WordPress updated to v1.5.10. Just a minor fix (closing quote for ‘exinclude-values’ in line 408). Thanks to SoFi and Kevin for notifying me about this bug.

Updates for F2 theme and Flexi Pages Widget

F2 WordPress theme update to version 1.0.6 with localization in Italian and Norwegian (Bokmål) languages. Thanks to Gianni Diurno for translating the theme in Italian and Eilif Nordseth for the Bokmål translation.

Flexi Pages Widget plugin updated to version 1.5.9 with localization in Brazilian Portugese, Swedish and Turkish languages. Thanks to Tzor More, Ove Kaufeldt and Hakan Demiray for the respective translations.

Plugin and theme updates on 2009-09-22

Flexi Pages Widget version 1.5.7

  • Ukrainian localization added. Thanks to the team at wpp.pp.ua for the translation.
  • Support for user defined widget arguments before_pagelist and after_pagelist

before_pagelist and after_pagelist are widget arguments that can be defined in the functions.php of your theme. These arguments can be used, for example, if you want to enclose the pagelist within a <div> (thanks to SoFi for the tip).

Quotes Collection version 1.3.5

  • Brazilian Portugese localization by Tzor More.
  • Modifications in quotes-collection.js (for better debugging in case of error)

F2 WordPress theme version 1.0.5

  • Dutch language localization by R. Helmes.
  • Minor improvements (styling for <pre>)

F2 WordPress theme 1.0.4

F2 WordPress theme updated to version 1.0.4.

  • Localization in Tamil language by Ravi. ஆம், தமிழ் வலைப்பதிவுகளிலும் பயன்படுத்த ஏதுவாகியுள்ளது F2. அழகிய தமிழில் மொழிபெயர்த்தவர் ரவி.
  • Support for custom.css.

The second point needs some explanation. When you customize the theme by directly editing the style.css file, you will lose your customizations when the theme is upgraded to a newer version. For this reason, it is advised that you create a file named ‘custom.css’ and put in all CSS customizations into that file, leaving style.css unchanged. The filename ‘custom.css’ is important as this file will be automatically included when WP loads.

Update on 2009-09-18: It seems that even the custom.css file gets deleted on upgrades. Therefore, custom.css should be backed up before upgrades. Also refer to this post for a better method to customize your theme: Using theme inheritance to customize your theme