• Blog
• Grocery CRUD 2026 Plans

Grocery CRUD 2026 Plans

Hey there! 👋 Welcome back to one of my favorite blog posts of the year! I am glad to write those lines for you for the following reasons:

• A communication with you 🥰, the amazing Grocery CRUD community. It is great to share that Grocery CRUD is still actively developed and supported.
• A chance to check the past year and see what was delivered.
• To set the stage for this year and see what was my goals retrospectively at the end of the year. Did I have realistic goals? Or did I pressure myself too much (again 😅)?

This time I will make it short. I prefer having a few bullet points rather than having a long text that nobody will read 😀. So here we go:

• New method setCustomQuery which you can use your own custom queries for Grocery CRUD.
• Updating translations for all 35 languages.
• PHP 8.4 compatibility.
• A long waiting function unsetBackToList, unsetList and setDefaultState. Which you can have standalone forms.
• Several bug fixes and improvements. Usually users are reporting a bug or an improvement and I am fixing it for the next release.
• New method inlineEditFields which allows you to have inline editing for specific fields.
• New method setRelation1to1 which allows you to have 1-1 relations between tables.
• New field type virtual which you can finally have fields that don't exist in the database (to use it with callbacks)
• Create a new function fieldOptions which you can add a hint text for your field (for example when the field input is empty).
• Getting latest React version to version 18 (version 19 coming soon).
• Better support for Postgres databases.

So far 12 releases, almost 1 release per month. Let's have a quick look at the change log for 2025:

3.2.7 (Release date: 04 January 2026)

• GC-585: callbackColumn to be available to work with inlineEditFields.
• GC-587: displayAs to allow new line characters for better readability of long field names.
• GC-588: unsetPagination to remove pagination display and data limit, allowing all records to be shown.

3.2.6 (Release date: 20 November 2025)

• GC-583: Adding ability for ordering with setCustomQuery
• GC-584: Add Latvian language.
• Updating translations for all 35 languages.

3.2.5 (Release date: 29 October 2025)

• GC-581: New function setCustomQuery which allows you to set a custom SQL query for the datagrid.
• GC-582: Add new function unsetPagination to remove pagination from the datagrid.

3.2.4 (Release date: 14 September 2025)

• GC-579: Field type boolean doesn't work as expected with a Postgres database.
• GC-580: setRelation1to1 doesn't work with Postgres.

3.2.3 (Release date: 31 August 2025)

• GC-577: Multigrid with CSRF protection is throwing 403 Forbidden error.
• GC-578: inlineEditFields fails with upload field and callbackBeforeUpload.

3.2.2 (Release date: 17 August 2025)

• GC-576: New functionality for Inline Edit Fields with new method inlineEditFields.

3.2.1 (Release date: 19 July 2025)

• GC-573: Fixing styling issues when open_in_modal is false.
• GC-574: Error handling - Show a non-empty error response when the error is in JSON format.
• GC-575: Postgres Database to use ILIKE instead of LIKE on search operations.

3.2.0 (Release date: 14 June 2025)

• Removing support for PHP 7.4 and requiring PHP 8.1 and above.
• PHP 8.4 compatibility.
• GC-568: New function unsetBackToList, which removes buttons to back To list.
• GC-570: New function unsetList, which is completely removing the datagrid listing. Useful for standalone form pages.
• GC-569: New method setDefaultState, which is defining the default initial state instead of datagrid (current default).
• GC-571: Custom error message to be able to be displayed also as HTML instead of a simple text.
• GC-572: Fixing issue with extended filtering modal and fieldTypeSearchColumn which wouldn't pick up the correct dataType.

3.1.16 (Release date: 12 April 2025)

• GC-566: Add scrolling to the "Visibility" tab of the datagrid, when there are many fields and columns doesn't fit in the screen.
• GC-567: Field type "virtual" shows blank space by default when it is used with callbackEditField and callbackReadField.

3.1.15 (Release date: 05 April 2025)

• GC-563: New feature: 1-1 relation with a new method setRelation1to1.
• GC-565: New JavaScript function groceryCrudEmitReduxAction which will trigger specific redux actions to dispatch within CRUD.

3.1.14 (Release date: 01 March 2025)

• GC-562: New field type virtual which it can be used for fields that doesn't exist within the database.
• GC-564: Create a new function fieldOptions which you can add a hint text for your field (for example when the field input is empty).

3.1.13 (Release date: 30 January 2025)

• GC-560: Remove JavaScript error when we use date field in Italian Language.
• GC-561: Refactoring some code in order to showcase the real fieldType output at the website documentation

And finally... our plans for 2026!

I will do it like the previous time. I will promise just a few things and try to do even more. Here is the list of planned features for 2026:

• Push notifications (e.g. Bootstrap Toasts) for CRUD operations (success, info)
• Info icon with tooltip for fields and columns
• Default visible columns configuration per CRUD
• Relation n-n but with new entries (I will do my best for this one, although quite complicated)

Apart from that, I will need to change a few things in this website:

• Improve the landing pages to be sure that you are on version 3 page
• Improve or even change our forums. There are issues with the registration and spam bots still which I have to address manually myself.
• Focus on Laravel framework as well. Not only CodeIgniter.

And finally: This year is a bit to check my own health. I understand that this is not catchy for a roadmap but 2025 I was burned out. Not because of Grocery CRUD but from my main job and plus trying to juggle everything alone.

Fair Warning: The current list is a plan of what I have as a plan to deliver for 2026 as a mini-roadmap of 2026. The achievement of these goals has complicated factors and planning for 2026 is kind of odd anyway! Remember there is still an ongoing war with Ukraine and Russia, and the world is changing rapidly with all the climate changes and the artificial intelligence and this is still a one-man project. So please treat the list of features and improvement as a to-do list rather than a contract!

Jan 28, 2026 by John Skoubourdis