Last Active
Preferred Name
  • Little bug when accepting a 'Personal Data Update' with a 'Custom Field'

    Hi Roman,

    Thanks for catching this bug. In this case, it looks like submitting the form multiple times had the potential to erase the custom field data for a user that was not included in the update, so well caught! I've applied a fix in the v18 branch, which you can see here, feel free to apply it back to your codebase:

  • Cutoff date in data update settings

    Yep, this sounds like normal behaviour, the goal for the redirect is to encourage all users to update their data. If they've never submitted an update then they'll be redirected along with any users who haven't submitted one after the cutoff.
  • Gibbon 17 Not Loading (Complete Non-functionality)

    Hi ErnestP,

    Yes, Gibbon version 17 requires a minimum of PHP version 7.0, be sure to check the PHP version that your new server is running.

    If you have FTP access to your server, you can install older versions without using Softaculous, by following the standard install instructions. It's recommended to run the latest version though, if possible. All Gibbon releases are available through GitHub.

    Hope this helps!
  • Naming of ”Canned Response”

    The world is a big place, I think any chosen terminology is bound to have various meanings to different people. Luckily there's string replacement, so you can fine-tune the terminology in your system to what works for your needs :smiley:
  • Polish Language Issue

    Hi dgago,

    It looks like some terms in the Polish translation may have incorrect string tokens (like %1$s and %2$s) so they're not inserting the links and urls into the text where they're meant to be. Would you be interested in helping fix these translations through our online POEditor tool? Then we could generate new translation files which should fix your issue. If so, send an email to and we'll set you up with access.

    The second issue seems to be that the Date Picker uses a different date format than what is recorded in Gibbon for the pl_PL locale. What is the standard form of writing a date in Poland? If it's, you could possibly correct this issue by running the following SQL on your database:

    UPDATE `gibboni18n` SET `dateFormat` = '', `dateFormatRegex` = "/^(0[1-9]|[12][0-9]|3[01])[- /.](0[1-9]|1[012])[- /.](19|20)\d\d$/i", `dateFormatPHP` = 'd.m.Y' WHERE `code` = 'pl_PL';

    Let me know if that works and we can make the same change in the core.