Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

NextGEN Custom Fields · Version history

NextGEN Custom Fields changelog and version history

Latest version
1.2.5
Jan 19, 2024 (2 years ago)
Releases
20
since 2009
In the last year
0
Tested up to
WordPress 6.4.14

Releases each year

  • 20097 releases
  • 20105 releases
  • 20114 releases
  • 20143 releases
  • 20241 release

20241 release

  1. NextGEN Custom Fields 1.2.5Latest

20143 releases

  1. NextGEN Custom Fields 1.2.4

    • Fix for gallery custom field values not showing saved values in admin manage gallery
  2. NextGEN Custom Fields 1.2.3

    • Restored custom fields in “Manage Gallery” screens in NGG >= 2.0.57
  3. NextGEN Custom Fields 1.2.2

    • Updated call to add_menu_page() and add_submenu_page() changing capability to ‘manage_options’ from deprecated user level 8 (thanks to ksemel for the report)

20114 releases

  1. NextGEN Custom Fields 1.2.1

    • Changed field_value column back to TEXT from VARCHAR(255), to allow more than 255 characters saved (thanks to ksemel for the find and bug report)
  2. NextGEN Custom Fields 1.2

    • Converted table to UTF8. This is much more compatible with internet safe languages.
    • Fixed quotes in field names and values
  3. NextGEN Custom Fields 1.1.3

    • Made gallery fields not rely on having an image custom field and JavaScript
    • Refactored some code to just clean it up a little
  4. NextGEN Custom Fields 1.1.2

    • I screwed up the backwards compatibility, sorry. Use 1.0.2 for < NGG 1.7

20105 releases

  1. NextGEN Custom Fields 1.1.1

    • Made it backwards compatible with NGG 1.6.x and lower. Should have been done with the last update, but I was spaced on pain meds
  2. NextGEN Custom Fields 1.1

    • Made this plugin compatibile with NextGEN Galley 1.7.x and greater, which breaks compatibility with lower versions of NGG
  3. NextGEN Custom Fields 1.0.2

    • Fixed a bug that would break gallery custom fields (textareas) if you had new lines in them. (thanks mygraphicfriend again for pointing it out)
  4. NextGEN Custom Fields 1.0.1

    • Fixed a bug that would delete all data for a custom field (all galleries or images in ngg), when it was unlinked from only a specific gallery (thanks to mygraphicfriend for pointing that out)
  5. NextGEN Custom Fields 1.0

    • Added the ability to link custom images when creating a new gallery. (Needs NextGEN 1.4.0 or later, thanks to maxx10 for the request)

20097 releases

  1. NextGEN Custom Fields 0.7

  2. NextGEN Custom Fields 0.6

    • Added the ability to select which galleries to link fields to (thanks to vividlilac and goto10 for pushing me into doing that)
  3. NextGEN Custom Fields 0.5

    • Added a little sanitation to field names and values, to allow apostrophes and some other none alphanumeric characters
    • Added the ability to edit a field’s name
  4. NextGEN Custom Fields 0.4

    • Added gallery custom fields
    • Fixed a bug that stopped the deletion of a custom field unless there was data saved for that field
  5. NextGEN Custom Fields 0.3

    • Added the ability to edit drop down options on existing fields
    • Added the “Change Log” section to this file 🙂
  6. NextGEN Custom Fields 0.2

    • Minor code reformat
  7. NextGEN Custom Fields 0.1

    • Initial release!

Questions about NextGEN Custom Fields’s releases

What is the latest version of NextGEN Custom Fields?

1.2.5, released on Jan 19, 2024 (2 years ago). It’s tested up to WordPress 6.4.14.

How often is NextGEN Custom Fields updated?

It had no release in the last year; the latest came out 2 years ago. Its first release on WordPress.org dates from March 2009.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in NextGEN Custom Fields’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.