What I’ve done, instead of not using GroceryCrud, is I’ve fixed it, improved it, and rewrote parts to extend it. If the code was exclusively GPL licensed, I would be obliged to publish my fixes, improvements, and extensions – pushing my commits to github, as you would be obliged with your improvemen…

The problems with the way you have it licensed are the following. No community development of the community edition is possible. The first thing a community would want to do with the community edition would be to fix the bugs in it and add the obvious extension that exist in the commercial edition …

I certainly appreciate the work you put into GC. I understand how you can feel “alone” in the work. That said, have you considered using the GNU GPL3 or Alfero license instead of the MIT license? It’s one thing to publish the code, quite another to make it a true copyleft open source project th…

Typical controller logic to jail into edit $state = $crud->getState(); $state_info = $crud->getStateInfo(); switch ($state) { case 'edit': case 'update_validation': case 'update': case 'success': $primary_key = …

To answer my own question, I guess there are two workaround I’ve thought of. One is to simply use a where clause to restrict the list to just one record. Sort-of a preview read-only view. The user then needs to click edit to change anything. Not quite as good as going directly to the edit page, but…

It appears that the README documentation on github for the community edition is relatively accurate, such as it is. I see correct docs for the where() function given there. Perhaps you should redirect your 2.x documentation on the main website to point to the correct docs for the community 2.x editi…

That’s so unfortunate. A typical use case is with a database of users. Each user should be able to edit their own profile record, but no-one else’s. I can’t believe your v2.x doesn’t support this very simple and common use case, as it did just fine in v1.x I understand that your removed the functi…